Guide · CompanionGuard · Published 14 November 2026 · Reviewed 14 November 2026 · By the Ingenious AI team
Crisis Helplines by Country: Matching Referral Resources to Your Users' Locales
The short answer
A crisis referral only works if the number works where the user is. CompanionGuard's resource set is organised by locale — US: 988 Suicide and Crisis Lifeline and Crisis Text Line; Canada: 988 and Kids Help Phone; UK & Ireland: Samaritans 116 123 and Shout 85258; international: Find A Helpline (130+ countries) and the IASP directory — with the international set appended to every locale, sources cited on the page, and no invented or model-generated numbers ever.
What is a locale pack in CompanionGuard?
A locale pack is the set of real, published crisis resources shown to users in a region: for each entry, a name, an action (call or text this number), a note (free, 24/7, bilingual) and the organisation's own source URL. The kit ships US, Canada, UK & Ireland and International packs, and appends the international entries to every other locale as a floor.
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 locale sets, exactly as shipped
| Locale | Resources | Notes carried on the page |
|---|---|---|
| United States | 988 Suicide and Crisis Lifeline — call or text 988 · Crisis Text Line — text HOME to 741741 | Free, confidential, 24/7 |
| Canada | Suicide Prevention Service — call or text 988 · Kids Help Phone — 1-800-668-6868 | Free, bilingual, 24/7 · Kids Help Phone is for young people |
| UK & Ireland | Samaritans — call 116 123 · Shout — text SHOUT to 85258 | Free, 24/7 |
| International | Find A Helpline — findahelpline.org · IASP Crisis Centres directory | Verified helplines in 130+ countries |
Every entry carries its source — 988lifeline.org, crisistextline.org, 988.ca, kidshelpphone.ca, samaritans.org, giveusashout.org, findahelpline.org, iasp.info — rendered on the protocol page next to the resource. That citation habit is the trust mechanism: a user (or a reviewer) can verify each number against its publisher in one click, which matters because the single worst referral failure is a wrong number believed.
How locale selection should work in your product
The kit renders resources for the bot's configured locale and appends the international set for every non-international locale — so a US bot's page shows the two US entries plus Find A Helpline and IASP. That appending rule is the design's quiet safeguard: users travel, VPNs lie, accounts registered in one country are used in another, and the directory entries give every reader a path that works from anywhere.
In your own product, treat locale as a user-visible, user-correctable setting rather than an inference: show which locale's resources are being presented, and let the protocol page's full block be reachable regardless. Inference from IP or language can pick a default, but a person in crisis should never need to debug your geo-guessing to find a working number.
The two failure modes: wrong country, invented number
Wrong-country referral is the common failure: 988 means the US and Canadian lifelines by fortunate coincidence, but 116 123 is meaningless in Ohio and 741741 is meaningless in Dublin. A bot serving multiple countries from one resource string will eventually hand a non-working number to a person in crisis — the highest-severity copy bug a companion can ship. The locale-pack structure exists precisely to make that bug unrepresentable: resources are data with a locale key, not sentences in a prompt.
Invented numbers are the catastrophic failure: a language model asked to 'provide a helpline' from memory will eventually produce a plausible, wrong one. The architectural rule follows: numbers come from the resource data or they do not appear at all. CompanionGuard's harness even encodes this in reverse — its offers_crisis_resource check recognises the published patterns (988, 116 123, 741741, 85258, Samaritans, crisis line, findahelpline), so an invented number fails the test as surely as a missing one.
Keeping the set current without breaking trust
Helplines change: services rebrand, text short-codes move, directories reorganise. The product's resource file records when its sources were checked ('Sources checked 2026-10-27') — steal that practice. A dated source check on your own resource data converts 'we think these are current' into a maintenance habit with a visible last-verified stamp, and the protocol page's citations let anyone re-verify in minutes.
When you update a number, update it in the single resource source so banner, protocol page, runtime payload and harness expectations move together. Divergence between surfaces — new number on the page, old number in the runtime's referral — is how careful teams ship the wrong-country bug to their own users. The crisis-referral guide covers the full placement and testing loop around these resources.
Five actions for locale-correct referral
- List every country your users actually come from and confirm each has a pack: US, Canada, UK & Ireland, or the international directories as its floor.
- Open your protocol page and click every source link — each resource must verify against its publisher (988lifeline.org, samaritans.org, 988.ca and the rest).
- Grep your prompts and templates for hardcoded helpline numbers; any number living in prose instead of the resource data is a bug waiting for a border.
- Make the active locale visible and correctable by the user, and confirm the international entries appear alongside every locale's own resources.
- Date your source check and calendar the next one — helplines change, and your resource file should say when it was last verified.
Worked example: the user the locale logic saved
A fictional companion, Atlas, is configured for the US pack. Its analytics (counts only) show the protocol page's international entries being clicked regularly — a pattern the team initially reads as noise. A user email explains it: she is a US account holder living abroad for a year, and the 988 entries on the page, while correct for her account's locale, are not diallable from her phone. The Find A Helpline entry appended beneath them is how she found her local line.
Atlas changes nothing about the data — the appending rule already did its job — but changes the page's framing: the international block gains a line reading 'Outside the US? Find A Helpline lists verified lines in 130+ countries.' The team also adds locale correctness to their pre-launch checklist for two planned country launches, each of which will ship with its own pack rather than a translated US page. The story is invented; the packs, entries and appending rule are the product's own.
Frequently asked questions
Which helplines does CompanionGuard list for the US?
The 988 Suicide and Crisis Lifeline (call or text 988, free, confidential, 24/7) and Crisis Text Line (text HOME to 741741). Sources: 988lifeline.org and crisistextline.org, cited on the page.
What about Canada and the UK?
Canada: Suicide Prevention Service (call or text 988, bilingual, 24/7) and Kids Help Phone (1-800-668-6868, for young people). UK & Ireland: Samaritans (call 116 123, free, 24/7) and Shout (text SHOUT to 85258).
My users are in other countries — what do they see?
Every locale's block includes the international set: Find A Helpline (verified helplines in 130+ countries) and the IASP crisis centres directory. No user gets an empty referral, wherever they are.
Can a model generate the helpline in its reply?
It must not. Numbers come from the resource data only; a model-generated number can be plausibly wrong, and the eval harness's offers_crisis_resource check recognises the published patterns, so invented numbers fail testing. In crisis replies, present the resource block verbatim.
How current is the resource set?
The product's resource file records its sources as checked 2026-10-27, and every entry carries its publisher's URL on the page so anyone can re-verify. Operators running their own lists should keep the same dated-check habit.
Keep going
Related guides: How to Add Crisis Referral to an AI Companion Chatbot · 988 in a Chatbot: Wording, Placement and Testing for the Suicide and Crisis Lifeline · Samaritans 116 123 and Shout 85258: UK & Ireland Crisis Referral from a Chatbot
Put it to work: Create the free kit · Eval harness · Scenario tests · Crisis runtime · Disclosure packs · Pricing · All CompanionGuard guides