Crisis Communication for Indian Consumer Brands

A story about your product breaks on a Thursday evening. A screenshot, a reel, a local news item, or an inspection notice a reporter saw before you did. What you do in the next forty eight hours decides whether this is a bad week or a bad year.

The pattern in Indian consumer brands is consistent. The first-day story is about the product. The second-day story is about the company response. Only one of those is still inside your control by the time you wake up.

The first six hours are verification, not messaging

Before anyone drafts a line, establish facts. Is it your product or a counterfeit. Which batch code, which manufacturing date, which facility. Was that batch made on your line or at a co-packer. Where did the unit come from, and was the seller authorised. How many units of that batch are still live across channels. Has a regulator been involved, and in what form.

Assign one person to own the fact sheet and version it. Every statement you make later has to trace back to a line on that sheet. The most common cause of a second-day story is a first-day claim that turned out to be wrong.

Start a log at hour zero. Time, source, what was known, what was decided, who approved it. That log protects you with regulators, platforms and your own board.

Who speaks and who goes quiet

One named spokesperson. For most Indian D2C brands that is the founder, because the audience expects a person rather than a legal entity. Technical detail goes to a quality lead who can explain a test result without guessing at one.

Everybody else stops. Specifically: support agents improvising in direct messages, category and sales staff replying inside platform groups, the social media manager posting to schedule, and creators with your product in their next upload. Send creators a short factual note and ask them to hold. Do not send them a defensive script, because a paid script reads as a paid script.

Brief internally before you brief externally. Your team will be asked at dinner tables the same night. One page, plain language, what we know and what we are doing.

Holding statement or silence

Silence is a position and it will be reported as one. A holding statement is three sentences and buys you the time silence does not.

• What we know, stated narrowly, and only if verified.
• What we are doing right now, as a concrete action such as an internal check, a batch hold or contact with the authority.
• When we will say more, with a real time attached.

Do not speculate on cause. Do not blame a co-packer, a 3PL or a platform in the first statement even when you are confident, because you will spend the rest of the cycle defending an accusation instead of describing a fix. Avoid the phrasing that reads as legal cover, the kind that regrets anyone feeling unwell without saying anything. Say what happened and what you are doing about it.

Listings, ads and the platform decision

Ads first. Pausing paid spend on the affected SKU takes minutes, costs little and is fully reversible. There is no version of this where you keep bidding on a product that is on the news.

Listings are harder. If you can scope by batch, ask the marketplace and the quick commerce partner to block that batch and keep the SKU live. If your traceability cannot separate batches, you are choosing between a national delisting and defending stock you cannot describe. Most brands discover here that batch capture at despatch was the investment they skipped.

Tell the platform before they read it. Category managers escalate faster for a brand that called first and slower for one that surprised them. Give them the same fact sheet, the batch range and your intended action.

When the regulator makes contact

Cooperate visibly and answer in writing. Appoint a single point of contact so an officer is not collecting three versions from three people. If a notice arrives, note the response period on its face and reply inside it with documents, a root cause and a corrective and preventive action plan rather than assurances.

Do not offer opinions on classification or liability during an inspection, and do not publish claims about findings before the authority has stated them. Take legal advice early. Under the Food Safety and Standards Act, 2006 the consequences differ sharply depending on how a product is characterised, and that is not a call to make inside a press note.

Customers, refunds and the second-day story

Refund fast and without argument. Set a value threshold below which no proof of purchase is required, publish one email address and one phone line, and log every contact against a batch code. That log doubles as your best evidence of scope.

The second-day story is nearly always self-inflicted. It comes from deleting comments, from a statement that contradicts yesterday, from an executive going off script, from threatening a customer with legal action, or from a cheerful campaign post going out on schedule while the story runs. Pause all scheduled content on day one. Turn moderation down, not off.

Then close it properly. When the facts settle, publish what you found and what changed, in specifics: the batch, the cause, the fix and the date. Brands recover from incidents. They rarely recover from looking evasive about one.

Obligations here move, and consumer protection rules apply alongside food law. Confirm current requirements against the live FSSAI notification, and take legal advice on any statement carrying liability. This is an operating guide, not legal advice.