Which crisis PR response fits your Web3 incident?
1 incident record gives us the starting point. It shows what happened, what is confirmed and who can approve the response. Crisis PR turns those inputs into clear messages for the people who need them. The first choice is the message format, not a broad public explanation.
| Format | Use it for | Window | What you send |
|---|---|---|---|
| Holding statement | An active review with facts still open | First public response | Confirmed facts and next update channel |
| Audience talking points | Repeated questions from users or partners | While facts develop | Affected groups and known concerns |
| Follow-up announcement | A resolved issue or confirmed update | After approval | Verified findings and official sources |
Choose a holding statement if people need an immediate acknowledgement. Use it while the investigation remains unfinished. Choose talking points if support and community teams already receive different questions. A follow-up announcement fits once the technical or operational lead confirms what changed.
For community-specific FUD handling, pair this work with the crypto community FUD guide. For a broader media plan, see PR and media. We keep the first message narrow. We expand it only when your evidence supports more detail.
Holding statement: 3 checks before approval
1 holding statement should acknowledge the issue, state what is known and point readers to the next update. It buys time for verification without filling gaps with assumptions. Keep each claim tied to a source your team can name.
- Confirm the event: Use the exact exploit report, listing notice or other source available to your team.
- Mark what is known: Separate confirmed impact from details still under review.
- Name the next update: Give readers a real channel or contact point for further confirmed information.
- Route technical claims: Ask the responsible technical or operational lead to check every incident-specific detail.
- Approve one version: Name the person authorized to publish. Then share the approved copy with channel owners.
For a reported exploit, the statement can acknowledge the report. Leave cause and impact open for review. For a delisting, quote the confirmed status. Avoid guessing at the platform’s reasoning. For a burst of FUD, answer specific, verifiable claims. Don't repeat every allegation.
Our review marks claims that need confirmation before publication. Your technical lead supplies that confirmation. Your approval lead owns the final wording. If a fuller announcement fits after facts settle, press release distribution can support the next communication.
5 inputs that keep crisis PR moving
5 inputs help us draft without turning unknowns into public claims. Send what you have and label gaps clearly. Identify who can close them. A complete evidence pack is useful, but a short, accurate record beats an unverified explanation.
Incident summary: What happened, when the team learned of it and what remains unclear.
Source material: Technical notes, official notices, public posts or correspondence relevant to the event.
Affected audiences: Users, token holders, partners, employees or journalists who need an update.
Approval owner: The person who can approve wording and authorize publication.
Subject-matter contact: A technical or operational lead who can check incident claims.
Add the urgent communication deadline.
Name the channels where an update may appear.
For a listing issue, send the exact notice, not a paraphrase.
For an exploit, include the material your technical lead considers authoritative.
For FUD, point us to the specific claims you want reviewed.
Don't forward unrelated discussion as if it were evidence.
This intake makes the first draft easier to review. It keeps the approval route visible. If you also need ongoing public-record work after the incident, see online reputation management.
What are the crisis PR windows and reporting points?
4 checkpoints show you what happens next: quote, work start, live updates and final record. The incident, evidence and approval route shape the message set. These are working defaults. We adjust them when the incident needs a different review path.
| Checkpoint | Window | What you receive |
|---|---|---|
| Written quote | Before payment | Confirmed message formats and work plan |
| Work start | Within 24 hours of confirmed payment | Intake review and assigned next actions |
| Active response | Every 24 hours while work is live | A status note with open checks and approved updates |
| Final record | Within 2 working days after the response window ends | Links and screenshots for published materials |
- A named account lead keeps requests, versions and approvals in one place.
- We flag missing evidence before it becomes a draft claim.
- Then we route copy to your authorized reviewer.
- Your team retains publishing access and final approval.
- The report records what was approved and published.
- It also lists open questions.
For a follow-on founder explanation, consider founder interviews and features. Need a different media format? The PR and media service list shows adjacent options.
Platform decisions stay with the platform
2 checks reduce avoidable messaging risk: verify the source, then verify who can approve the claim. A platform controls its own listing review and decision. Media outlets control whether they publish. We cannot set those outcomes. We can deliver the agreed statements, coordinated copy and report.
Open technical question: Mark it as unconfirmed until the responsible lead verifies it.
Delisting explanation: Use the exact notice. Don't present a suspected reason as established fact.
Conflicting public versions: Pause new wording until the approval owner selects the source of truth.
These checks matter most when a public post could outpace the team's evidence.
Give the technical reviewer a direct route to the person drafting the message.
Keep one approved version available to people handling media, community and partner questions.
That creates a usable record without claiming the response can control an external decision.
If the incident is active, send the exact notice or incident summary. Include the target channels and your approval lead's name. We’ll review those 3 inputs, identify missing checks and return a written quote within 2 working days.
How it works
- 1. Send the incident recordShare the current account of events, source material, affected audiences and urgent deadlines.
- 2. Name the reviewersIdentify the approval owner and the technical or operational lead who can verify claims.
- 3. Review facts and draftWe separate confirmed details from open questions. Then we prepare the agreed message formats.
- 4. Approve and coordinateYour authorized lead checks the copy before channel owners use it.
- 5. Record updatesWe log approved messages, published links, unresolved questions and the next communication decision.
Frequently asked questions
What should we send first for crisis PR?
1 incident summary is enough to start the review. Add the exact notice or source material. Include affected audiences and urgent deadlines. Name your approval lead. If a detail is unknown, label it as open. A technical contact helps us check incident-specific claims before they appear in public copy.
Can you write a holding statement during an exploit investigation?
1 holding statement can acknowledge the report. It can identify what the team has confirmed and direct readers to the next update channel. It should not claim a cause or impact still under review. Your technical lead checks incident details. Your approval owner signs off before publication.
How should we answer a delisting notice?
1 exact notice is the source for the first response. We distinguish confirmed listing status from any explanation not yet established. Then we adapt approved wording for users, partners or media. Your authorized representative reviews the final message before it goes out.
Should we reply publicly to every FUD claim?
1 specific, verifiable claim beats a stream of unrelated posts. We help identify what the project can substantiate. Then we draft a measured response for the right audience. The FUD response guide covers community-facing decisions beyond the incident message.
Can crisis PR coordinate Telegram, X and media updates?
3 channel types can use the same approved core message. We adapt it for each audience. We prepare channel-ready wording and record its approval and publication status. Your team keeps publishing access and final approval. We can include Telegram, X and media when they are part of the agreed plan.
Can crisis PR reverse a platform delisting?
1 platform controls its own listing review and decision. Communications work cannot reverse that decision. We can use the exact notice to prepare accurate messages, organize approvals and document updates. The agreed work covers those communications and the report, not a platform outcome.
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…