Home/Pune practice/Corporate and crisis comms
Service · corporate communication
Operations improved faster than the reputation did
Two situations, one discipline. Customers who still describe you the way they did three years ago, and the week when something goes wrong and nobody knows who is allowed to say what.
Build the plan before you need it See the escalation path
- Recovery work
- 4 to 6 weeks
- Crisis system
- 3 to 4 weeks, built cold
- Includes
- Roles, paths, holding statements, internal FAQ
- Reviewed
- Annually, or after any use
Component supplier · reputation recovery
Rebuilding trust after repeated delivery problems
The company had resolved its production bottleneck. Customers still associated it with late deliveries and were routing new enquiries elsewhere.
Operations had improved considerably faster than the reputation. Nobody had told the market anything, partly because the sales team found the subject uncomfortable and avoided raising it.
We communicated the recovery with evidence: revised processes, added capacity, new tracking systems and transparent order updates. Sales teams were trained to acknowledge the earlier problem directly without becoming defensive.
Trust returned, and it returned because the communication matched what the factory could now actually deliver. A slogan would have made it worse.
You cannot communicate your way out of a delivery problem. Once it is genuinely fixed, failing to communicate is leaving the recovery on the table.
Manufacturing company · crisis system
The crisis response written before the crisis
A product quality incident. Technical teams investigated immediately and competently. Customer communication was slow and inconsistent.
Different customers received different explanations depending on who they reached. The silence in between created considerably more anxiety than the incident itself, and two customers heard about it from a third party.
After the situation was resolved, a crisis communication system: response roles, approval paths, holding statements, customer update templates, internal FAQs and escalation rules.
The next problem did not become a communication emergency, because the company already knew who had to say what, to whom, and by when.
Nobody writes well at eleven at night during a recall. That is precisely why the writing happens now.
Who says what, by when
Named owner and named deputy, decided long before today, because incidents do not wait for people to return from leave.
A holding statement within two hours buys you the day you need to investigate. An approval chain that cannot move at incident speed simply gets bypassed, so the path is designed with a clock on it.
The internal FAQ matters more than most companies expect. Your employees get asked by customers directly, and without a briefing they improvise. Improvised answers travel faster than official ones.
What the system contains
Named roles and deputies
Who decides, who writes, who speaks to customers, who briefs employees, and who covers each of them.
An approval path with a time limit
Two hours, not two days, with a defined escalation if someone is unreachable.
Pre-written holding statements
For the three or four scenarios your category actually faces, with blanks for specifics.
A customer update template
What is known, what is not, what you are doing, and when they will next hear from you. The last item is what stops the phone ringing.
An internal FAQ
Issued to all staff before customers start calling them.
Escalation triggers
What moves a routine complaint into crisis mode, decided in advance rather than argued during.
An annual rehearsal
Ninety minutes, one scenario, the actual people. It is the only way to find out that the approval path does not work.
Before you ask
We have never had an incident. Do we need this?
That is exactly when to build it. Writing a communication system during a live incident produces slow, defensive, inconsistent messaging, which is what turns a technical problem into a commercial one.
Who should speak to customers, sales or quality?
Both, coordinated. Sales owns the relationship, quality owns the facts. What fails is a technical explanation delivered without relationship context, or a reassuring commercial message the facts later contradict.
Should we ever say nothing?
Rarely, and never for long. Silence reads as concealment. Saying that you are investigating and will update by a specific hour is almost always better than waiting until you have the complete answer.
Is this the same as PR?
No. Media relations is a different discipline and I bring in specialists where a story is genuinely public. Most manufacturing incidents never reach media and are won or lost entirely in direct customer communication.
Who writes the first customer email?
If you cannot answer that in one name, the system does not exist yet. It takes three or four weeks to build properly and you only ever build it when nothing is wrong.
Build the plan before you need it See case studies
Kunal Waghmare · Padmavati Hills, Mokai Vasti, Bavdhan, Pune, Maharashtra 411021
office@quiamo.com · +91 90216 02686