What should a Web3 team do first when a crisis breaks?
Start by establishing what is confirmed, who can verify it and who has authority to speak. In an exploit or delisting situation, teams are often asked for an explanation before technical or commercial reviews are complete. A short, accurate holding statement can acknowledge the issue and explain when the next update will come without presenting an unverified cause as fact.
Bitcoin Insider begins with a source-of-truth review: we gather incident notes, public posts, relevant notices and the project’s current status from the people responsible for each area. We then mark each point as confirmed, under review or not for publication. This gives the team a usable basis for decisions rather than a draft built from scattered chat messages.
Before responding publicly, identify:
- The incident owner and the person authorized to approve statements.
- The facts that can be shared now, and what remains under investigation.
- The audiences who need an update first, such as users, partners or media.
- The next update time or condition the team can realistically meet.
For broader communications support, see our PR and media services.
How do holding statements work during a Web3 incident?
A holding statement gives people a reliable first account while the team checks the underlying facts. It should identify what is happening in plain language, say what the project is doing now and set expectations for the next update. It should not speculate about responsibility, imply that funds or services are safe without verification, or promise a resolution the team cannot yet support.
We prepare a core statement and adapt its emphasis for the audiences that need it. Users may need practical instructions; partners may need operational context; journalists may need a concise summary and a contact who can respond. The wording can differ, but every version should trace back to the same approved facts. We also prepare answers to likely follow-up questions, so the spokesperson is not improvising under pressure.
A useful approval sequence is simple: the incident owner checks the facts, the relevant technical or legal lead checks their area, and one named spokesperson approves the final copy. Keep a dated copy of what was published and note which information changed between updates. If a formal announcement is appropriate, our press release distribution service can support a separate publication plan after the message is ready.
How does crisis PR differ for FUD, exploits and delistings?
The response should match the incident, not force every situation into the same announcement. FUD calls for a careful distinction between a claim and verified evidence; an exploit calls for confirmed user guidance and a clear account of what is being investigated; a delisting requires precise language about the affected venue and what users should do next. The communication task is to make the known situation understandable, not to make every incident sound resolved.
| Situation | First communication priority | Useful supporting material |
|---|---|---|
| FUD or disputed claims | Address verifiable points and avoid amplifying unsubstantiated details | Evidence log, concise Q&A, spokesperson notes |
| Exploit or service incident | Share confirmed user guidance and investigation status | Incident timeline, approved update channel, user instructions |
| Delisting notice | State what the notice covers and direct users to confirmed information | Venue notice, token or service identifiers, user Q&A |
For each case, we map the facts to the audience’s immediate question: what has happened, what should I do, and where will the next verified update appear? When an ongoing community conversation needs a dedicated response approach, FUD handling for crypto communities offers related guidance. Keep the evidence and the message together so new drafts do not drift from what the team can substantiate.
What does a crisis PR engagement include?
A crisis PR engagement turns an urgent, fragmented situation into an approved communication sequence. The exact scope is agreed with the team, but the work can include an initial fact review, holding statement, stakeholder messages, spokesperson preparation, anticipated questions and follow-up updates. We focus on communications deliverables and decision support; the project team remains responsible for technical investigation and operational decisions.
The working file keeps the response practical: confirmed facts, open questions, approved language, owners and the next review point. This gives each participant a clear place to check before publishing or replying. For ongoing reporting, we record what was prepared, what was approved and which public messages were issued, rather than treating a burst of activity as evidence of resolution.
A typical sequence is:
- Brief: identify the incident, decision-makers, audiences and immediate deadline.
- Verify: organize source material and flag claims that require confirmation.
- Draft: prepare the holding statement and audience-specific messages.
- Approve: route language to the named factual and communications owners.
- Update: revise the message as verified information changes and log each version.
A named account lead coordinates drafts and approvals with your designated incident owner. If the situation also calls for earned coverage after the immediate response, sponsored articles in crypto media can be considered as a separate, clearly labeled communications option.
What can a crisis PR team control during an incident?
A crisis PR team can organize evidence, prepare accurate language and coordinate the agreed communications work. It cannot decide the outcome of an exchange review, reverse a venue’s delisting decision, determine the findings of a security investigation or require journalists and social platforms to handle a story in a particular way. Those decisions remain with the relevant platform, investigators, editors or project leadership.
That distinction shapes the plan. We will not describe a listing status as restored until the venue confirms it, or present an exploit explanation as final while the technical review remains open. We also avoid asking the team to publish a stronger claim than its evidence supports. The deliverable is the agreed communications work, with clear approval records and updates that reflect confirmed information.
For a project with a longer-term reputation concern beyond the immediate incident, online reputation management may be a separate follow-on service. Crisis response should not be used to obscure a material issue; it should help the team communicate what it knows and what it is doing next. This is especially important when users need practical information rather than reassurance alone.
What should you prepare before contacting a crisis PR team?
You do not need a polished incident report before asking for help. A concise account of what happened, the latest confirmed status and the next decision deadline is enough to start a focused review. Share source documents or notices where possible, and identify who can confirm technical, legal, operational and communications details.
Keep the initial handoff factual. Include the public statements already made, the channels where questions are arriving, any commitments the team has already announced and the audiences with immediate needs. If some material is confidential, flag it clearly and use the sharing method your team approves. We can then identify the gaps that matter for the first statement instead of delaying the work for a complete post-incident account.
Send Bitcoin Insider the incident summary, available source material, the name of your incident owner and the most urgent communication deadline. We will review the handoff, identify the first approval decisions and propose a scoped response sequence for your team to confirm.
Prices
| Service | Price | Quote |
|---|---|---|
| Community FUD Playbook | on request |
Starting prices in USD. Custom bundles and volume discounts on request. Payment in USDT, USDC, BTC, ETH, SOL, TON or your project token.
How it works
- Brief the response leadShare the incident summary, current status, key audiences and immediate decision deadline. Name one person who can coordinate approvals.
- Review the evidenceWe organize source material into confirmed facts, open questions and information that should not yet be stated publicly.
- Draft the first messagesWe prepare a holding statement and the audience-specific language required for the agreed response.
- Route approvalsThe designated project owners verify facts and approve the copy before publication or direct outreach.
- Update and documentAs new facts are confirmed, we revise the agreed messages and keep a clear record of versions and communication decisions.
Frequently asked questions
How quickly can you help us prepare a holding statement?
The first draft follows the initial fact review and depends on how quickly the right people can confirm the incident details and approve language. In the first briefing, we identify the decision-makers, the facts that can be stated and the earliest useful update. We agree a workable response schedule with your team rather than promise a fixed turnaround before seeing the material.
What information should we send for crisis PR?
Send a concise incident summary, the latest confirmed status, relevant notices or source documents, links to statements already published and the next deadline facing the team. Include the names or roles of people who can verify technical, legal and operational details. Mark confidential material and tell us which audiences need guidance first.
Can you respond to FUD if we cannot prove every claim is wrong?
Yes. The response can separate claims that are disproven, claims that are still being checked and facts the project can document now. A careful statement does not need to answer every allegation at once; it should correct verifiable inaccuracies, avoid repeating unsupported details unnecessarily and explain how the project will provide further information.
Can you manage communication after an exploit?
We can support the communication work: organize confirmed details, draft user-facing guidance, prepare stakeholder messages and update statements as the investigation develops. Your technical team remains responsible for investigating the exploit and confirming operational instructions. We work from information approved by the people who own those decisions.
Can crisis PR reverse a delisting or guarantee a publication?
No. A venue controls its own listing review and status, while editors decide whether and how to cover a story. We can prepare a factual response, organize supporting information and deliver the communications work agreed with your team, but we cannot compel either decision or describe an outcome before it is confirmed.
Should we publish a statement before the investigation is complete?
Not necessarily. If people need immediate guidance, a holding statement can acknowledge the issue, share only verified information and set expectations for a further update. If there is no confirmed information or useful action to communicate, agree internally on what is being checked and who will authorize the next message before posting.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…