Mentions that warranted engagement but went unanswered — late or never. Some are recoverable; some aren't; all reveal workflow gaps worth fixing. This guide covers the historical audit, the recovery framework for late engagement, the diagnosis of WHY mentions were missed (detection failure vs triage failure vs capacity gap), and the prevention systems. The companion fix to response time — the work that happens after you realise some opportunities slipped past while you were optimising for speed.
Pull last 6-12 months of mentions across all tracked platforms. For each, flag whether it warranted response and whether response happened:
For each mention, tag:
- Warrant level: did this need engagement? (Yes / Maybe / No)
- Engagement happened: (Yes / Late / No)
- If late: how late? (hours / days / weeks / months)
- Outcome: what happened to the relationship/issue/sentiment?
Compute miss rate = mentions where warrant=Yes AND engagement=No
Typical findings:
- 20-40% miss rate is common at companies with no formal workflow
- 5-15% miss rate at companies with monitoring + workflow
- <5% miss rate at companies with dedicated reputation function
- Misses concentrate in: positive mentions (62% miss rate avg),
weekend/holiday windows, low-reach platforms, niche communities
| Miss type | Why missed | Recoverable? |
|---|---|---|
| Detection miss | Monitoring tool didn't surface it | Sometimes — depends on age |
| Triage miss | Detected but classified as no-response when it warranted one | Often — late engagement possible |
| Capacity miss | Detected, classified, but team didn't get to it | Often — late engagement possible |
| Authority miss | Detected but no one had authority to respond | Often — late engagement possible |
| Knowledge miss | Responder didn't know what to say | Often — late engagement possible |
| Active avoidance | Deliberately skipped (often defensive) | Sometimes — depends on whether avoidance still makes sense |
| Window-closed miss | Time-sensitive mention, window passed | Rarely — usually permanent |
Hi [name], I came across your [post / review / article] from [date] mentioning us — somehow we missed it at the time. Just wanted to say thank you properly. The bit about [specific thing they said] genuinely meant a lot. If you ever want to chat or there's anything we can do to support your [work / project / etc], let me know. [Real name] [Real role] --- Reads as: genuine, attentive, slightly self-deprecating about the miss. Works even months later. Often opens a productive relationship.
Hi [name], I was reviewing our community engagement and saw your [post / comment] from [date] about [specific issue]. We didn't reply at the time, which we should have. I'd like to make it right if it's still an issue: [specific action or offer]. If you've moved on, I understand — but if you're still dealing with this, please DM me at [contact]. [Real name] [Real role] --- Don't over-apologise. Don't make excuses. Just acknowledge, offer resolution, leave the door open. Most people appreciate this even if the original issue is no longer relevant to them.
Hi [name], I was catching up on [publication]'s coverage and saw your piece from [date] that included our [product / opinion / data]. Wanted to reach out belatedly — really appreciated the thoughtful framing. If you're working on related stories or want background on [relevant topic] anytime, I'd be glad to chat. [Real name] [Real role] --- Works well for journalist/analyst relationships. Builds the relationship that should have started at original mention time. Don't pretend the delay didn't happen; just move past it gracefully.
For the historical audit, group misses by root cause:
Expand monitoring coverage:
- Add more keyword variations (brand misspellings, product names,
internal codenames, exec names, related topics)
- Cover more platforms — review monthly which are surfacing missed
mentions, add them
- Set up secondary alerts for high-value mentions (e.g. anytime
a named journalist or competitor mentions you)
- Tune for false-positive vs false-negative balance — too noisy
and people ignore alerts; too quiet and misses accumulate
Triage decision tree documented:
- Severity criteria with examples
- Reach criteria with examples
- Specific test cases responders have practiced classifying
- Calibration: monthly review where team triages the same mentions
independently, compare classifications, identify drift
Capacity allocated by tier: - Crisis: dedicated on-call, no other duties when on-call - High: dedicated business-hours coverage, clear primary/backup - Standard: distributed across team with daily quota - Background: explicit "may not be responded to" expectation If a tier consistently misses, options: - Add capacity to that tier - Reclassify some mentions downward (less goes into that tier) - Reduce SLA expectation for that tier - Automate some responses (template + light human review)
Decision rights matrix:
- Standard responses: any trained responder approves
- Customer service / refunds within £X: support lead approves
- Public correction of factual error: responder approves with
peer review
- Legal language: legal lead approves regardless of tier
- Crisis statements: comms lead approves; exec briefed
- Anything responder is unsure about: escalate without shame
The principle: push authority DOWN to where speed matters.
Reserve exec/legal involvement for genuinely needs-them situations.
Monthly metric:
Miss rate = mentions where warrant=Yes AND engagement=No
divided by total warranted mentions
Targets:
Crisis tier: 0% miss rate (anything else is failure)
High tier: under 5% miss rate
Standard tier: under 15% miss rate
Background tier: rate irrelevant; this tier explicitly optional
Track:
- Trend over time (improving / declining)
- By tier (where are misses concentrated)
- By platform (which surfaces produce most misses)
- By responder (any individual struggling)
- By time-of-day (overnight gap?)
Quarterly improvement focus: pick the highest-miss tier or pattern,
make one systemic change, measure for 8 weeks, evaluate.
Missed opportunities affect more than just immediate engagement:
Miss-rate metric, root-cause analysis, recovery workflow.
Run Brand Mention Monitor →