A first-day map for community FUD
The first 24 hours are for organizing the response, not guessing at an outcome. Start with a short acknowledgement. Route the question to someone who can verify it. Make the next update easy to find.
| What | Count or window | What you prepare |
|---|---|---|
| Claim record | 1 entry per concern | Exact wording, channel, public link |
| Evidence check | 1 named owner | Primary sources and open questions |
| Moderator reply | 1 approved version | Confirmed facts and next update route |
| Channel review | Telegram, Discord, X | Accounts and spaces your team manages |
| Follow-up | When facts are checked | Verified outcome or unresolved point |
Use the table as a working map. Keep the first acknowledgement brief. The factual answer may need more review.
Put current wording in one shared source. Direct moderators to that source. If the issue touches a project profile or listing, stick to verified details. See the guides to CoinGecko listing and CoinMarketCap listing for platform-profile work.
What should moderators do before answering?
5 actions take a concern from capture to a responsible reply. Use them in order when facts are unclear. Do not skip an evidence check just to answer faster.
- Capture the exact concern. Save its wording, channel, and public link. Record the actual question, not an easier version.
- Classify the question. Mark it as an information request, misunderstanding, conduct issue, or matter needing investigation. One message can fit several categories.
- Assign an evidence owner. Route supply questions to someone who can verify supply information. Send security, treasury, and technical points to their accountable owners.
- Acknowledge without filling gaps. State what is confirmed and what is being checked. Name where the next update will appear. Do not present an interpretation as verified fact.
- Approve and publish the reply. Check that sources support each factual statement. Give moderators current wording and a clear route for questions they cannot answer.
This sequence keeps a community manager useful without making them the technical authority. It also separates ordinary questions from issues that need a project lead.
For broader channel preparation, see the Telegram community guide. The Discord setup guide covers server preparation.
3 records every moderator needs
3 records give moderators a reliable basis for action: the concern, the evidence, and the current response. Keep each record short enough to check during a busy discussion. Make it clear enough for another team member to take over.
- Concern: Exact question or allegation, where it appeared, and a link or preserved message.
- Evidence: Primary sources checked by the team. Add what each source does and does not establish.
- Owner: Person responsible for confirming technical, supply, security, treasury, or operational details.
- Approved reply: Current public wording, its source, and any detail still under review.
- Moderation rule: Published rule that applies if conduct crosses a stated boundary.
- Update note: What changed, who approved the change, and where the current version lives.
A useful evidence file stays current, attributable, and readable without insider context. Include official project links, relevant explorer records, published token or governance information, and plain-language explanations of recurring terms.
Add a review date when material changes. An on-chain record can show a movement. It does not prove intent. Ask the relevant owner to confirm any interpretation before it appears in a public reply.
How do Telegram, Discord, and X change the reply?
3 channels call for one consistent factual position. Moderation actions differ across spaces your team controls. Keep the source of truth steady. Adjust the format and channel action to fit the conversation.
- Telegram: Admins can manage discussion in their own group and point members to an official update.
- Discord: Moderators can apply the server’s written rules and route technical questions to an owner.
- X: The project can publish a clear correction from its account and link to supporting information.
In each channel, preserve useful questions. Do not make moderators improvise different facts.
| Channel | What your team can do | What to prepare |
|---|---|---|
| Telegram | Moderate the project group | Short reply and official update link |
| Discord | Apply server rules | Moderator handoff and evidence source |
| X | Publish from the project account | Clear statement and public references |
Use the same approved facts across all 3 channels. If a conversation needs specialist input, acknowledge it and route it. Do not try to settle it in public chat.
A broader community plan can connect channel rules with community growth and engagement.
5 checks before a response goes live
5 checks catch unsupported wording before moderators publish it. Run them against the draft and its sources. Do not check only what the team hopes readers will conclude.
- Claim: Does the reply address the question people actually raised?
- Source: Can a reader open the evidence and see what it supports?
- Status: Are confirmed facts separate from items still under review?
- Authority: Has the responsible owner approved each technical or financial statement?
- Route: Does the reply name the official place for an update?
- Moderation: Does any action follow a written rule, rather than the tone of criticism?
Send us the draft, the public sources checked, and the channel involved for an outside review. Include open questions. Name the person who can verify them. DigitalMedia1 can flag unsupported wording, unanswered points, and a missing escalation route.
This review helps before a tense exchange. It also helps when moderators need a clear version to share.
Follow-up turns a reply into a usable record
1 follow-up should state what the team checked, what it learned, and what remains open. Publish it where community members can find the original response. Correct any earlier wording that proved incomplete.
When review continues, name the open question and its owner. Do not announce a deadline the responsible team has not approved. If the issue is resolved, explain the finding in plain language. Link to evidence readers can inspect. Keep private user details out of the public record.
After the exchange, ask 3 practical questions. Did the first reply match the evidence? Did the handoff reach the right owner? Did moderators have a current source to use? Update the response file when answers show a gap.
If the issue needs external communications support, Crisis PR is a separate route. This playbook remains the day-to-day guide for community replies.
For a focused review, send DigitalMedia1 the draft response, the claim’s public link, and the sources already checked. We can return a clearer reply and an escalation route. Send those 3 items to start.
How it works
- 1. Capture the concernRecord the exact wording, channel, and public link. Keep the team focused on the question actually raised.
- 2. Assign an evidence ownerRoute technical, supply, security, or treasury points to someone authorized to verify them. Moderators should not guess.
- 3. Acknowledge what is knownSeparate confirmed facts from open questions. State where the next verified update will appear.
- 4. Apply the written rulesKeep legitimate questions available and use the same conduct rules for everyone. Escalate unclear moderation decisions.
- 5. Publish the follow-upShare the checked outcome, correct incomplete wording, and update the team’s response material.
Frequently asked questions
Should moderators remove a critical comment?
1 rule matters: criticism alone is not a reason to remove a comment. Keep substantive questions visible and answer them with relevant facts. Restrict content only when it breaches a stated rule. Examples include threats, exposing private information, impersonation, or repeated disruption. Apply the same standard consistently. Record consequential moderation decisions.
Who should approve a reply about token supply?
1 accountable owner should verify the underlying supply information before it appears in a public answer. A community manager can collect the question, share existing documentation, and coordinate the handoff. They should not infer supply details from partial context. Give moderators a current owner list and a route for reaching the right person.
What should we say while a claim is still being checked?
1 clear acknowledgement is enough to start. State which point is under review and where the team will post an update. Keep guesses out of the reply. Do not repeat an allegation as established fact. After the evidence owner checks the sources, publish the result or explain what remains unresolved.
Should the founder answer every post about the project?
1 named spokesperson should handle statements that need senior authority. That does not mean the founder must answer every post. Moderators can acknowledge routine questions, share approved facts, and route specialist issues. Set an escalation rule for security, treasury, or material project changes. Staff should know when a senior reply is needed.
Can our team remove copies of a post from every channel?
1 project account can publish an official response. Moderators can manage spaces the team controls. But Telegram forwards, screenshots, and discussion on other accounts remain outside that control. Platform review and distribution decisions are also outside the project’s control. Keep the factual update easy to find. Use consistent moderation in owned channels.
What should we send for an outside response review?
3 inputs make a review practical: the draft reply, the public claim or question, and the sources the team checked. Add the channel and any unresolved facts. Identify who can verify those points. DigitalMedia1 can use that material to flag unsupported wording and suggest a clear escalation route without guessing about project details.
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…