Guide · CompanionGuard · Published 14 November 2026 · Reviewed 14 November 2026 · By the Ingenious AI team
988 in a Chatbot: Wording, Placement and Testing for the Suicide and Crisis Lifeline
The short answer
988 is the Suicide and Crisis Lifeline number in the US (call or text, free, confidential, 24/7) and also reaches Canada's Suicide Prevention Service (bilingual, 24/7). In CompanionGuard it appears in four places that must never diverge: the disclosure banner's crisis line, the locale resource packs on the protocol page, the runtime's show_crisis_resources payload, and the eval harness's resource pattern — the check that passes a crisis reply only if a recognisable resource like 988 is actually in it.
What is 988, as this product uses it?
988 is the published number for the 988 Suicide and Crisis Lifeline in the United States — call or text 988, free, confidential, 24/7 (988lifeline.org) — and, in the Canada pack, for the Canada Suicide Prevention Service (988.ca), also call or text, free and bilingual. In CompanionGuard it is resource data, never a sentence a model improvises.
Create the free safety kit Next guide All guides
CompanionGuard is built by Ingenious AI. A compliance toolkit — not legal advice and not a clinical service. If you are in crisis right now: US — call or text 988; UK & Ireland — Samaritans 116 123.
The four places 988 lives
The banner: 'If you are in crisis, call or text 988 (Suicide and Crisis Lifeline) any time, free and confidential' — fused into the disclosure wording of both the California and Colorado packs, so the number is present from the first interaction. The resource packs: the US entry (988 Lifeline, call or text 988) and the Canada entry (Suicide Prevention Service, call or text 988), each with its source cited on the protocol page. The runtime payload: when a signal class matches, show_crisis_resources hands the bot the locale's resources — including 988 for US and Canadian sessions — to present immediately. The harness pattern: '988' is one of the recognised resources that passes offers_crisis_resource.
Four surfaces, one datum. The engineering rule that keeps them consistent is the resource file as single source: change the entry and the banner context, page, payload and test expectations all describe the same referral. Teams that keep helplines in prompt prose will, eventually, update three surfaces and miss the fourth — usually the one the user meets.
Wording: call or text, free, confidential, 24/7
The qualifiers around the number do behavioural work. 'Call or text' matters because the users least able to speak aloud — a teenager in a house with thin walls, a person whose crisis is precisely about being overheard — are the users for whom a voice-only referral fails. 'Free and confidential' answers the two hesitations (cost, exposure) most likely to stop a first contact. '24/7' answers the timing doubt at 3 a.m. CompanionGuard's notes carry exactly these qualifiers from the publishers: US — 'Free, confidential, 24/7'; Canada — 'Free, bilingual, 24/7', where bilingual is itself an access qualifier for French-speaking users.
Copy the qualifiers with the number, every time. A bare '988' in a reply is a pass in the harness and a weaker referral in the world; the tested floor and the humane ceiling are different targets, and the ceiling is the one your users live at. The Crisis Text Line guide covers the text-first sibling resource.
Testing that 988 actually appears
The harness's offers_crisis_resource check recognises '988' among its patterns — which creates a precise, mechanical release gate: paste your bot's crisis replies, and any reply whose referral got lost (paraphrased away, formatted as an unrecognised URL, replaced by 'a helpline') fails by name. Run the crisis_referral scenarios too: the disclosed-plan scenario is the one where a missing number is most dangerous.
Also test the negative space: everyday replies must not contain 988 (the does_not_over_refer check), because a bot that pastes the lifeline into birthday-planning chat teaches users the number is decoration. Both directions are the referral's credibility.
When 988 is the wrong number
988's dual US/Canada coverage is a fortunate overlap, not a universal one. A user in the UK reaching a US-configured bot needs Samaritans 116 123; a user anywhere else needs Find A Helpline. That is why the international entries ride along in every locale block, and why locale correctness — covered in the helplines-by-country guide — outranks any single number's prominence. 988 is the right answer for a large share of this product's users; the design treats it as one locale's answer, not the answer.
If you are in crisis right now and in the US or Canada: call or text 988. In the UK & Ireland: Samaritans 116 123. Elsewhere: findahelpline.org.
Five actions for a correct 988 referral
- Confirm 988 appears in all four surfaces for US/CA bots: banner, protocol-page pack, runtime payload and your test expectations — from the one resource source.
- Check the qualifiers travel with the number: call or text, free, confidential, 24/7 (bilingual for Canada).
- Paste real crisis replies into the eval harness and require offers_crisis_resource to pass on every one — investigate any reply where the number was paraphrased or URL-buried.
- Verify everyday replies do not contain 988, keeping the number's meaning intact.
- Confirm non-US/CA users see their own resources (Samaritans, Find A Helpline) with equal prominence — 988 is a locale answer, not a global one.
Worked example: the URL that failed the check
A fictional companion, Beacon, believed its crisis replies were exemplary: each ended 'support is available at 988lifeline.org'. Its first harness run disagreed — offers_crisis_resource failed on two of five crisis scenarios. The reason is instructive: the checker recognises the resource patterns (988 as a number, lifeline phrasing that matches its pattern set), and Beacon's most polished replies had drifted into link-only referrals where the actionable number never appeared as text.
The fix took minutes and generalised: crisis replies now state 'call or text 988' in plain text, with the website as a supplement rather than the referral itself. Re-run: all crisis checks pass. Beacon's team kept the lesson in their style guide — a referral is a number a person can act on from the message alone, at 3 a.m., on a cracked screen, without clicking anything. The story is invented; the check and its patterns are the product's own.
Frequently asked questions
Is 988 the same in the US and Canada?
The number is the same and both are in CompanionGuard's packs: in the US it reaches the 988 Suicide and Crisis Lifeline (free, confidential, 24/7); in Canada, the Suicide Prevention Service (free, bilingual, 24/7). The organisations and sources differ (988lifeline.org, 988.ca) and the page cites each.
Where does 988 appear in CompanionGuard?
In the disclosure banner's crisis line (both US state packs), in the US and Canada resource packs on the protocol page, in the runtime's show_crisis_resources payload, and as a recognised pattern in the eval harness's offers_crisis_resource check.
Should a crisis reply include more than the number?
Yes: the qualifiers that make contact possible — call or text, free, confidential, 24/7 — plus an empathic acknowledgement and a suggestion of human support, which are separate harness checks. The number is necessary, not sufficient.
What if my user is not in the US or Canada?
Then 988 is the wrong referral. UK & Ireland users get Samaritans 116 123 and Shout 85258; every locale's block includes Find A Helpline and the IASP directory for the rest of the world.
Does showing 988 in everyday chat help?
No — it fails the harness's does_not_over_refer check and erodes the number's meaning. Keep 988 in the chrome (banner, protocol page) always, and in replies when a crisis signal or a direct need makes it a referral.
Keep going
Related guides: Crisis Helplines by Country: Matching Referral Resources to Your Users' Locales · Text HOME to 741741: Adding Crisis Text Line to a Companion Bot · How to Add Crisis Referral to an AI Companion Chatbot
Put it to work: Create the free kit · Eval harness · Scenario tests · Crisis runtime · Disclosure packs · Pricing · All CompanionGuard guides