Guide · CompanionGuard · Published 14 November 2026 · Reviewed 14 November 2026 · By the Ingenious AI team
International Crisis Referral: Find A Helpline, IASP and the Everywhere Floor
The short answer
Most of the world has no dedicated pack in CompanionGuard — it has something more scalable: the international set, Find A Helpline (verified helplines in 130+ countries) and the IASP crisis centres directory, appended to every locale's resource block. The design principle is a floor, not a gap: a user in any country can always reach a directory of verified local lines, even where the product ships no country-specific entry.
What is the international pack?
The INTL entry in CompanionGuard's resource set: two directory resources — Find A Helpline (findahelpline.org) and the IASP Crisis Centres list (iasp.info) — shown as the resource block for international users and appended to the US, Canada and UK & Ireland blocks, so the directories are present on every bot's protocol page.
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.
Why directories, not 190 country tables
A companion bot's users are wherever the internet is; its builder's knowledge is not. Maintaining verified, current helplines for every country is a research programme no small team sustains — and a half-maintained table is worse than none, because stale numbers fail silently. Directories invert the problem: Find A Helpline maintains verified helplines across 130+ countries as its mission, and the IASP (International Association for Suicide Prevention) curates its crisis centres list the same way. Referring to the directory outsources currency to the organisations whose job it is.
The product's phrasing on the page is exact about what these are: a directory action ('findahelpline.org', 'iasp.info crisis centres') rather than a phone number. That honesty matters — a directory referral asks one more step of the user than a number does, and pretending otherwise would overstate the referral. One more step to a verified local line beats zero steps to an invented one.
The appending rule: a floor under every locale
CompanionGuard appends the international entries to every locale block except the international one itself — so a US bot's resources are the two US entries plus Find A Helpline and IASP; likewise Canada and the UK. The rule looks redundant until you enumerate the users it serves: the traveller, the expatriate, the student abroad, the user whose account locale is simply wrong. For each of them, the 'wrong' pack contains a working path anyway.
It also disciplines expansion: launching in a new country does not require a perfect pack on day one, because the floor is already there. The country work — a dedicated entry, youth lines, text channels — becomes an upgrade to a functioning referral rather than the precondition for one. The locale guide shows the full structure.
Presenting a directory referral in conversation
In a crisis reply, the directory mention should be concrete: name it, say what it does, keep the everyday checks intact ('Find A Helpline lists verified helplines in more than 130 countries — findahelpline.org'). Note that the harness's resource pattern includes 'findahelpline', so a directory-based referral passes offers_crisis_resource in its own right — the scoring discipline does not privilege numbered countries over directory-served ones.
Where the bot knows the user's country, the ideal reply pairs both: the locale's own entries first, the directory as the traveller's net. Where it does not know, the directory leads. Either way, the reply must never fill silence with a remembered number for a country whose pack the product does not carry — the invented-number failure is the one unforgivable referral bug.
When to build a dedicated pack
Directory referral is the floor, not the ceiling. Signals that a country deserves a dedicated researched entry: sustained user share from that country, a partner or regulator asking country-specific questions, or a launch that markets into the country deliberately. The pack standard to meet is the existing ones: published services only, publisher sources cited on the page, call and text channels where they exist, a youth line where one exists, notes that answer the hesitations (free, language, hours), and a dated source check.
Until a country meets that standard, the honest configuration is the floor plus transparency: the protocol page shows the directories for what they are. Users forgive a directory; they do not forgive a wrong number delivered with confidence.
Five actions for international referral that never empties
- Open your protocol page in each locale configuration and confirm Find A Helpline and IASP appear in every block, appended beneath the locale entries.
- Read one crisis reply intended for an unlisted country: it must name the directory and its coverage, never an improvised local number.
- Score that reply in the harness and confirm the directory mention passes offers_crisis_resource (findahelpline is a recognised pattern).
- Track user countries in aggregate; when one country's share grows, schedule its dedicated pack research against the existing packs' standard.
- Date your directory link checks — directories reorganise like everything else, and a dead directory link is an empty referral by another name.
Worked example: forty-one countries, two directory entries
A fictional companion, Wayfare, reviews its signups and finds users in 41 countries — with dedicated packs for exactly 3 of them. The naive project (research 38 country tables) stalls for a quarter. The shipped project takes a day: confirm the international appending rule covers every configuration, rewrite the protocol page's international block heading to say plainly 'Outside these countries? Find A Helpline lists verified helplines in 130+ countries', and add directory-referral wording to the crisis-reply template for unlisted locales.
Over the next quarter the counts-only metrics show the directory entries are the second-most-used resources on the page. Wayfare later builds two dedicated packs for its largest unlisted countries — researched to the standard of the existing ones — and the floor stays underneath both. The story is invented; the directories, their coverage figure and the appending rule are the product's own.
Frequently asked questions
What is in the international pack?
Find A Helpline (findahelpline.org — verified helplines in 130+ countries) and the IASP Crisis Centres directory (iasp.info). Both are directory referrals rather than phone numbers, and the page presents them as such.
Why not list every country's helpline directly?
Currency and correctness: directories like Find A Helpline and IASP maintain verified, current listings as their mission. A small team's hand-built table goes stale silently, and a stale number is a failed referral. The directory referral outsources freshness to the organisations that own it.
Do directory referrals count in the eval harness?
Yes — 'findahelpline' is among the recognised patterns for offers_crisis_resource, so a crisis reply offering the directory passes the check. Directory-served countries are not second-class in the scoring.
Which locales get the international entries?
All of them: the set is appended to the US, Canada and UK & Ireland blocks, and constitutes the international block itself. Travellers and mis-localed users always have a working path.
When should a country get a dedicated pack?
When its user share, a partner's requirements, or a deliberate launch justifies the research — to the same standard as the existing packs: published services, cited sources, call and text channels, a youth line where one exists, and a dated source check.
Keep going
Related guides: Crisis Helplines by Country: Matching Referral Resources to Your Users' Locales · How to Add Crisis Referral to an AI Companion Chatbot · What Counts as a Crisis Referral? Defining the Event Your Reports Depend On
Put it to work: Create the free kit · Eval harness · Scenario tests · Crisis runtime · Disclosure packs · Pricing · All CompanionGuard guides