Do not paste private group-chat messages, participant names, workplace information or personal allegations into a general chatbot. Extract a non-sensitive public claim yourself or use a fictional example. Keep the original message privately if needed to understand what was actually said.
A claim lands in a family group chat, a neighborhood forum, or a work channel; several people react and someone forwards it. Correcting it feels risky in a way that correcting a stranger online does not: these are people you will still be talking to tomorrow, and a clumsy correction can read as an accusation, a lecture, or a fight about who is smarter - even when the evidence is on your side.
This is a practical script for interrupting a spreading claim in a live group conversation, plus the quick verification step to run before you post anything.
What the evidence does and does not establish
The 2018 Twitter diffusion study concerns how true and false news traveled on that platform. It does not test the correction scripts below or establish which tone works in your family or work group. The scripts are practical wording options for presenting inspectable evidence.
Tool and workflow choice: verify fast, before you type anything
Before responding, identify the exact checkable claim and a source responsible for the relevant fact. There is no fixed time limit for verification; if you cannot finish, say what remains unverified.
Here is a claim from a group chat: [public, non-sensitive claim or fictional example]. In one sentence, what
is the specific checkable claim being made? Then tell me what kind of
source would confirm or refute it directly (a named outlet, an
official account, an official statement) - do not tell me whether the
claim is true, I will check the source myself.
Open the relevant primary source before you post anything. If a prompt returns no source, a broken link, or only secondary commentary, do not repeat its conclusion. If you cannot verify the claim in the time available, label it unverified and ask people to pause further sharing.
Step-by-step: the interruption script
Step 1: Address the claim, not the person. State what you checked without guessing why someone shared it. “I looked into this claim” identifies your task; it does not accuse the poster of inventing it.
Step 2: Lead with what you found. Share what the primary source says before explaining the discrepancy. Give others an inspectable basis for assessing your conclusion; do not promise that a particular tone will change their minds.
I looked into this - the original source is [X], and here's what it
actually says: [summary]. Looks like the version going around adds
[the inaccurate part].
Step 3: Leave room to update. State the discrepancy without guessing why someone shared it. “The notice gives a different date” is enough; you do not need to call it an easy mistake or predict their reaction.
Step 4: Choose whether to continue. If someone contests the correction, you can restate the source and unresolved point, then pause or choose a more appropriate channel. Repeating the exchange is not required to establish what the source says.
Step 5: Follow up if the picture changes. If new information emerges - the original story was updated, a fuller version came out - post the update the same way you posted the correction: matter-of-fact, source-first, no victory lap.
Validation and fallback
If you cannot verify the claim either way in the time available, say so directly rather than guessing: “Couldn’t confirm this one way or the other - the original source I could find doesn’t say [the specific claim]. Would hold off sharing further until it’s clearer.” An honestly labelled “unverified” is a legitimate contribution. This article does not claim it is as effective as a confirmed correction; its purpose is to avoid adding another unsupported assertion.
Human review or escalation rule
For a claim affecting money, safety or another consequential decision, check that the relevant person or responsible channel has the correction where doing so is safe and appropriate. A private message is one option, not a universal rule. For immediate danger, use local emergency services; for abuse or safeguarding concerns, follow the appropriate support or reporting route rather than contacting a person who could create further risk.
A reusable script template
| Situation | What to say |
|---|---|
| Claim is confirmed false | ”Looked into this - original source is [X], and it actually says [Y]. The version going around added [inaccurate part].” |
| Claim is confirmed true but missing context | ”This part checks out, but worth adding: [missing context], from [source].” |
| Could not verify either way | ”Couldn’t confirm this one way or the other from [source]. Might be worth holding off sharing until it’s clearer.” |
| Someone pushes back | Restate the source once, calmly. Do not repeat the argument further. |
When the rumor is about a specific person in the group
Some group-chat claims are not abstract news - they are about a member of the group itself, or someone connected to it: a rumor about a colleague’s job status, a claim about a family member’s health or behavior, gossip framed as fact. These need extra care, because the interruption script above assumes the subject is not reading along. If the person the claim concerns is in the chat, or likely to see it, consider whether the correction belongs in the group at all versus a private message to the original poster - a private correction may avoid repeating identifying details to the whole group. Choose the channel for the actual circumstances, not a promised social effect.
A correction that shows its basis
Invented example: a group message says the library closes permanently on Friday. The library’s notice says only that its reading room closes that afternoon for maintenance. A response could be: “The library’s notice says the reading room is closed Friday afternoon for maintenance: [official link]. I could not find a permanent-closure announcement there.” This corrects the scope without claiming to have checked every possible announcement. If the notice changes later, update the message.



