What to do in the first six hours

Most reputational damage is done by the response, not by the event. The response is decided by whether anyone prepared for it, which is work nobody wants to do on a good day.

Something goes wrong. A product fails publicly, a customer posts a video, an employee says something, a payment breaks, a journalist calls. The event is usually survivable. What is often not survivable is six hours of silence followed by a defensive statement written by a committee.

Prepare on a quiet Tuesday

• A named decision maker, reachable, authorised to approve a statement without a board meeting.
• A holding statement template that can be filled in within fifteen minutes.
• A list of what could plausibly go wrong, written by the operations team rather than by marketing, with a position drafted for the top five.
• Monitoring that would actually tell you, including the platforms where your customers complain rather than the ones you post on.
• Agreement on who speaks, and an instruction to everybody else that they do not.

This takes a day and it is the entire difference between a controlled response and an improvised one.

The first six hours

Acknowledge quickly, even without full facts. The holding statement says three things: we know, we are looking into it, we will come back by a stated time. Then meet that time, even if the update is that you do not yet know more.

Say what you do know and nothing you do not. Do not speculate about cause. Do not blame a vendor, an employee or a customer in public, ever, because it reads as evasion even when it is true. Correct factual errors in coverage, politely and privately first.

Fix the thing before talking about having fixed it. A statement that outruns the remedy produces a second cycle worse than the first.

When silence is correct

When the matter is in a legal process, when responding would amplify something almost nobody has seen, or when a single angry individual is seeking engagement rather than resolution. Silence is a decision that should be made deliberately and reviewed every few hours, not a default produced by nobody feeling able to act.

Tone

Plain language, no corporate abstraction. People can tell the difference between an apology and a sentence constructed to avoid one. If you got it wrong, say so in short words. Regret for an outcome without ownership of the cause is the most common tonal failure in Indian corporate statements, and the audience reads it accurately every time.

Afterwards

The incident becomes a search result, and the search result lasts far longer than the news cycle. Publishing your own clear account of what happened and what changed gives both people and answer engines something accurate and first party to find. Then do the slow corroboration work: coverage that is not about the incident, content that is genuinely useful, reviews answered properly. That is reputation repair, and it runs in months rather than weeks: see reputation is a search result.