A customer raises a serious concern. Screenshots start circulating, journalists request a comment, and different teams begin drafting different answers. In that moment, the priority is to understand what is happening and help the people affected. A polished statement cannot substitute for a real response.
In the first 24 hours of a consumer brand crisis, establish verified facts, assign decision-makers, acknowledge the issue, explain the next action, and keep updates consistent. The timeline below is a working sequence, not a reason to wait. Urgent safety instructions and required notifications may need to happen immediately.
This guide focuses on communication for consumer brands. Product safety, security, legal, and emergency specialists should direct the underlying incident response when their expertise is needed. Communication supports that work; it does not replace it.
Not every critical comment is a crisis. A routine service complaint may be handled by customer support. A credible report of harm, a significant service failure, or a rapidly spreading allegation may require a coordinated response. Visibility alone is not a reliable measure of seriousness: a low-profile concern can still be urgent.
Ask what happened, who may be affected, whether the issue is continuing, and which team can verify the facts. Separate an allegation from a confirmed event without dismissing the person reporting it. Do not describe a situation as contained, isolated, or resolved until the responsible team has evidence for that conclusion.
The CDC’s Crisis and Emergency Risk Communication framework was developed for major emergencies. Its emphasis on timely, accurate, credible, empathetic, and actionable communication is also useful when planning a brand response. Applying those principles does not make a marketing team an emergency authority.
Create a shared incident record with a clear owner. Keep confirmed facts, unresolved questions, and the actions being taken in separate sections. For each material fact, record who verified it and when. A screenshot may show what someone posted; it does not establish every claim made in that post.
Preserve relevant records according to your organization’s policies and any instructions from counsel. Avoid copying personal information into widely shared chat channels. Give people a secure route to submit details, and restrict sensitive material to those who need it.
Identify the people who need to make decisions: the incident lead, communications lead, customer support lead, and relevant operational specialists. Name an approver and a backup. Keep the group small enough to act, while involving the expertise required for the actual issue.
Review scheduled social posts, promotional emails, creator content, and other public activity. Pause material that would be insensitive, misleading, or inconsistent with the response. Do not automatically erase the brand’s entire presence or delete records of what happened.
A first statement can explain what the brand knows and what it is doing before every question has an answer. It should not imply certainty that the team does not have. The useful test is whether someone affected can understand the current situation and their next step.
Build the statement around five elements: the issue being addressed, the people affected, the confirmed facts available, the action underway, and where the next update will appear. Use a specific update time when the team can reliably meet it, even if that update may report that work is continuing.
Lead with concern for people rather than the organization’s reputation. Avoid defensive openings about the brand’s long history or a request that the audience be patient before you have acknowledged their experience. If the organization made an error, communicate that accurately and explain the corrective action that is actually underway.
The PRSA Code of Ethics emphasizes accurate communication and correcting errors. That is a useful standard for the approval process: identify unsupported claims before release and correct material mistakes openly afterward.
Use one accessible page or other stable destination as the main public record when the situation warrants ongoing updates. Add a visible date and time to each update. Social posts, media responses, and support replies can point there, helping people find current information instead of an outdated screenshot.
The core facts should remain consistent across channels, but the delivery can differ. A customer may need a clear support route. An employee needs to know who can speak publicly and where to send questions. A journalist needs a named contact, a verified statement, and an honest answer about when more information may be available.
Make updates readable on a phone. Use short paragraphs, descriptive headings, and accessible text rather than placing essential instructions only inside an image. Where relevant, consider language needs and other barriers that could prevent affected people from understanding the message.
Coordinate directly with retailers, distributors, event operators, or creators who need verified information to avoid repeating an outdated claim. Do not ask them to speculate, defend the brand without facts, or present a scripted position as an independent personal opinion.
Monitor questions and reports across the channels relevant to the incident. Track recurring information needs, newly reported impacts, misleading claims, and questions your current statement does not answer. Treat that record as input for the incident team, not simply as a sentiment score.
Give customer-facing staff an approved answer set and a route for escalation. Explain which questions they can answer, which require investigation, and how to handle sensitive information. A consistent response should not become a copy-and-paste reply that ignores the person’s actual concern.
If misinformation is materially affecting people’s decisions, correct it with verified information and a clear source. Avoid amplifying every obscure rumor by repeating it to the entire audience. Decide whether an individual reply, a clarification on the update page, or a broader announcement is proportionate.
Moderation should follow a clear policy. Legitimate criticism is not the same as harassment, threats, spam, or disclosure of personal information. Document moderation decisions and apply the policy consistently rather than removing uncomfortable comments to make the page look positive.
Imagine a consumer brand learns that a scheduled public event cannot open as planned. This is a hypothetical planning example, not a Jive PR + Digital client case study. The immediate communication need is practical: should people still travel, where can they get verified information, and when will the next decision be announced?
Operations first confirms the affected session and what is known about access. Communications then updates the main event information, briefs customer support, and reaches people through the channels available for that event. Creators scheduled to promote the opening receive the same confirmed facts.
If the cause remains under investigation, the statement says so. It does not promise a reopening time that operations has not confirmed. As the situation changes, the team updates the central notice and the channels that carried the original message. That follow-through is more useful than issuing a reassuring statement while outdated promotional posts remain visible.
Publish updates when meaningful facts change and at the intervals you have committed to. If the investigation is ongoing, say what remains unresolved and what is being done next. Do not manufacture progress simply to make an update sound more positive.
Check whether the response is reaching affected people. Are support teams still receiving questions already answered elsewhere? Are important instructions buried? Are partners sharing an earlier version? These observations can reveal communication gaps that a broad engagement report would miss.
Prepare a handover for anyone taking over the response. Include the latest approved facts, outstanding questions, public commitments, contact responsibilities, next update time, and relevant links. Confirm who is monitoring overnight or across time zones where needed.
At the end of the first day, the issue may still be unresolved. The goal is a reliable response process: clear ownership, an accurate public record, and practical information for the people affected. A later review should examine both the underlying incident and how effectively the organization communicated.
For everyday reputation work outside an active incident, see Jive PR + Digital’s guide to managing online brand reputation. If you are reviewing your broader PR communication approach, contact Jive PR + Digital to discuss your brand’s needs.
It can acknowledge an issue and explain what is being verified without speculating. Share confirmed information, identify what remains unknown, and give people a useful next step. Urgent instructions should be coordinated with the responsible specialists rather than delayed until a complete narrative is available.
Use a named communications approver with input from the people responsible for the incident’s facts. Depending on the situation, that may include operations, legal, security, or safety specialists. Identify a backup so the process does not stop when one person is unavailable.
Apply your published moderation policy consistently. Criticism alone is not a reason to remove a comment. Threats, harassment, spam, and exposed personal information may require a different response. Preserve relevant records and escalate serious concerns through the appropriate internal process.
Update when meaningful verified information changes and meet any update times you have announced. The right cadence depends on the incident and audience needs. If there is no resolution yet, explain what is still being checked and when people can expect another update.
