Crisis PR gives your team a clear first voice
Crisis PR helps a Web3 team respond when an incident raises questions beyond routine community updates. We work with your people to turn confirmed information into plain, useful messages for members, partners and media.
The first choice is usually between a short holding statement and a fuller explanation. A holding statement can acknowledge the issue, say what is confirmed and point people to the next update. A fuller explanation makes sense when your incident lead has checked enough detail to describe impact or action. We help you avoid filling gaps with guesses.
Start by gathering the incident timeline, source material, current public posts and the name of the person who can approve wording. If the discussion is mainly community confusion, our guide to handling FUD in a crypto community can help. For wider work after the urgent response, online reputation management can address ongoing public questions. We focus on clear communication; your technical and legal leads remain responsible for their specialist findings.
Build the first response around three checks
A useful first response separates what is known, what is being checked and what readers should do next. We use that simple structure to help your team move from a pile of messages to wording people can follow.
- Check the source. Identify who reported the issue and what primary evidence is available. Keep screenshots, notices or technical notes with their source and time received.
- Mark the facts. Put confirmed details in one group and unresolved claims in another. Assign each open point to the person who can verify it.
- Set the next update. Agree where the official message will appear and who approves it. If you cannot give a time for the next update, say what event or confirmation will trigger it.
Say a delisting notice reaches your team while members are sharing competing explanations. We would first compare the notice with the project’s own records, then draft a brief response that names what is confirmed. If the reason remains unclear, the wording should say so plainly rather than offer a theory. When the situation needs formal media distribution, we can connect the approved message with press release distribution.
What changes when the incident is an exploit or delisting?
The communication plan changes with the facts your team can confirm and the questions people need answered. We keep each message tied to its source, audience and approval route.
For an exploit or suspected vulnerability
Let the technical incident lead set the boundaries for public detail. A statement can identify the affected product, describe the investigation status and share user steps only after the responsible team approves them. Do not include private user information or operational details that have not been cleared. If the cause or impact is still unknown, say what is under review without implying a conclusion.
For delisting news
Confirm the notice, the affected asset or service, and any user-facing instructions from the relevant platform. A project can explain what it has done, such as contacting the platform, only after that action has happened and is approved for disclosure. Keep speculation about the platform’s reasoning out of the official account.
For FUD and public criticism
Sort claims by whether they need correction, a direct answer or a support route. A concise reply with evidence may help; repeating every unsupported claim can distract from useful information. Our PR and media services can support a later explanation when your team has stable facts and a clear spokesperson.
Keep the people answering questions on the same page
Your community hears the response through people as well as statements. We help give admins, founders and support staff a shared source of approved wording. Each person knows what to answer and where to send harder questions.
Picture a Discord server with a part-time admin, between a testnet and a mainnet. A worrying post appears while the project team is checking an incident. We would help the admin use a short approved reply and point members to the official update channel. We would send technical questions to the named lead.
A practical handoff can include:
- A short reply for moderators and support staff.
- Talking points for the founder or approved spokesperson.
- A Q&A that marks unresolved questions clearly.
- A channel list showing where the official update belongs.
For example, suppose partners ask for an explanation while community members want immediate user guidance. We can prepare separate versions from the same confirmed facts. Both should name the same official source, while each answers the audience’s real question. Your team approves the wording before it goes out.
Keep the public record useful as facts change
A strong response stays connected to the evidence as the incident develops. We can prepare statements, talking points, Q&A and agreed outreach, then keep a record of approvals, publication links and follow-up questions. When new facts change an earlier message, make the correction visible and direct readers to the current account.
An exchange or other platform makes its own decision about a delisting review. Newsrooms decide whether to cover an incident and how to frame it. Social platforms control post visibility and moderation; we can deliver the communications work you approve, but cannot direct those decisions.
After the urgent exchange has settled, keep the original statement, later updates and their sources together. Note which questions remain open and name the person responsible for each next answer. If the incident calls for a deeper explanation, founder interviews and features may suit that next stage. Your team should be ready to speak on the record.
To start, send Brand Community a short incident timeline, relevant notices or posts, confirmed facts and the name of your approver. We’ll review those materials with your contact, identify the first gaps to resolve and agree on the messages your team needs.
How it works
- Share the current pictureSend the timeline, source material, public messages and contact details for the people checking facts. Flag what is sensitive or not cleared to share.
- Separate facts from open pointsWe work with your designated lead to sort confirmed details from questions still under review. Each open point gets a clear owner on your side.
- Draft for the people who need answersWe prepare the agreed statement, talking points or Q&A in plain language. Each message reflects its audience and channel.
- Get the right approvalYour authorized spokesperson and relevant advisers review the copy. Nothing is released without the approval your team requires.
- Coordinate and keep a recordWe help align approved updates across agreed channels and log publication links, outreach and follow-up questions.
Frequently asked questions
What should we send before you draft a first update?
Send a short timeline, the notice or post that raised concern, what your team has confirmed and what remains unknown. Include any response already shared and name the people who can check technical details and approve wording. For example, a delisting notice and its source help us distinguish an official notice from community discussion.
Can you help when exploit reports are still unclear?
Yes. A holding statement can acknowledge the report, share only what the incident lead has confirmed and point readers to the official update channel. It should not guess at cause or impact. We can mark open questions clearly, then revise the message when your technical lead approves new facts.
How do you keep a delisting response from sounding final?
We describe the confirmed status without suggesting the platform has made a different decision. If your team has contacted the platform or is reviewing next steps, the statement can say so once that action is confirmed. A clear line between known status and future action helps members understand what has happened.
Should we answer every critical post in Discord or X?
No. We help sort posts into those that need a factual correction, those that need a support answer and those that are better left unamplified. For example, repeated questions about a user action may belong in one pinned official update rather than many separate replies. Moderators can then point members to that source.
How soon can your team begin reviewing the incident?
We can begin when a project contact shares the available evidence. They should also connect us with the people who can verify facts and approve messages. The pace then follows those checks and approvals. If details are still missing, we can identify the open questions before drafting language that depends on them.
Can you make an exchange or newsroom change its decision?
No. The relevant platform controls its own delisting decision, and each newsroom decides whether to publish. We can prepare accurate materials, coordinate approved outreach and record follow-up, but cannot promise a reversal, coverage or removal of someone else’s post. Our commitment is to the communications work agreed with your team.
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…