# Crisis Management (Brand Crisis Management)

## Quick answer

Crisis management, in a brand-monitoring context, is the process of noticing a sudden spike in negative mentions or a fast-spreading complaint early enough to respond before it spreads further, then tracking whether the response actually reduced the negative volume. It is reactive by nature, built around speed rather than a fixed schedule.

## Why it matters

A single bad experience rarely sinks a brand, but a bad experience that spreads unanswered for a day or two, while competitors and onlookers pile on, can turn into the first thing a prospective buyer reads when they search the brand's name. Catching the spike within hours instead of days is usually the only real lever a team has, because the content itself is often already public and unremovable. A slow response also tends to invite more commentary, since an unanswered complaint reads as confirmation to anyone deciding whether to pile on themselves.

## How to measure it

Watch mention volume and sentiment for sudden, sharp changes rather than slow trends, since a crisis shows up as a spike, not a drift. A team that already tracks daily mention counts and sentiment can set a simple threshold, such as a mention count or negative-sentiment jump well outside what a normal day looks like, and treat crossing it as a signal to look immediately rather than wait for the weekly review. After the fact, checking whether the negative volume actually fell following a response, rather than just assuming it did, shows whether the response worked.

## Example

A checkout software vendor has an outage during a high-traffic shopping period, and complaints start appearing across a community forum and social platforms within the same hour. The team that is already watching mention volume sees the spike almost immediately, posts a status update in the same places the complaints are appearing, and the negative mention count tapers off well before the outage itself is even fully resolved. A team without that monitoring in place would likely have learned about the complaints only once a customer called support directly.

## FAQ

### How is crisis management different from ordinary brand monitoring?

Ordinary monitoring runs on a regular schedule, such as a daily or weekly review; crisis management is about catching a sudden spike fast enough to respond the same day, which requires watching for the spike itself rather than waiting for the next scheduled check.

### Can a small team realistically do crisis management?

Yes. The main requirement is already tracking mention volume and sentiment continuously, so a spike is visible quickly; a team checking manually once a week will simply catch it too late to matter.

### Does a crisis always require a public response?

Not always. Some spikes are about a single incident that resolves on its own once fixed; the judgment call is whether the volume and tone are still rising or already fading before deciding to respond publicly.

### How is a crisis spike told apart from ordinary noise?

By comparing it against the brand's own normal range for mention volume and sentiment, built from past data; a jump well outside that range is the signal, not any single mention on its own.

## Related terms

- /glossary/customer-sentiment
- /glossary/brand-health-tracking
- /glossary/media-monitoring

## Related

- Competitor monitoring use case: /use-cases/competitor-monitoring
- MarketHQ pricing: /pricing