Guide · CompanionGuard · Published 14 November 2026 · Reviewed 14 November 2026 · By the Ingenious AI team
Text HOME to 741741: Adding Crisis Text Line to a Companion Bot
The short answer
Crisis Text Line is the US pack's text-native resource: text HOME to 741741, free, confidential, 24/7 (crisistextline.org). For companion-bot users it is often the most usable referral — silent, private, and native to the chat medium the user is already in. In CompanionGuard it sits beside 988 in the US resource pack, is recognised by the eval harness's resource pattern (741741), and models a design rule: always offer a text path, never only a phone call.
What is Crisis Text Line, in this product's resource set?
Crisis Text Line is a published US crisis resource in CompanionGuard's US locale pack: 'Text HOME to 741741', noted as free, confidential, 24/7, sourced from crisistextline.org. It is the pack's text-channel entry, complementing the 988 Lifeline's call-or-text service, and one of the recognised patterns that passes the harness's offers_crisis_resource check.
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 a text channel is a different resource, not a duplicate
A phone call requires privacy, breath and a voice that works. The users a companion bot most needs to reach often have none of the three: a young person in a shared bedroom, a user whose distress presents as muteness, anyone for whom being overheard is itself the danger. A text short-code removes all three barriers at once — it is silent, it happens on the device already in their hand, and it continues the medium (typing) they were already using with your bot.
That is why the US pack carries Crisis Text Line as a first-class entry rather than a footnote to 988, and why the same logic appears in the UK pack as Shout (text SHOUT to 85258). When you present resources in a crisis reply, the text option should be typographically equal to the call option — burying it second, smaller, or behind a link re-ranks it for exactly the users who need it first.
The exact mechanics: HOME to 741741
The action line is precise: text HOME to 741741. The keyword matters (it opens the conversation), the short-code matters (it is not a phone number and does not dial like one), and the harness recognises '741741' in its resource pattern — so a reply containing the text instruction passes offers_crisis_resource in its own right. Protocol-page rendering carries the entry with a tap-to-text link (an sms: href pre-filled with HOME), reducing the action to one tap from the page.
Precision is the safety property: a mis-remembered keyword or transposed digit is a failed referral wearing a correct one's clothes. As with every number in this product, the entry lives in the resource data with its source (crisistextline.org) and is rendered, never paraphrased by a model.
Where the text option belongs in a crisis reply
A model crisis reply in this product's discipline has three movements: acknowledge the person (the empathic_acknowledgement check), offer resources (with both channels visible: 'call or text 988, or text HOME to 741741 to reach Crisis Text Line'), and suggest human support beyond the screen. The text-line mention strengthens the second movement without lengthening the reply much — one clause — and it gives the user a genuine choice of channel, which is itself a small restoration of control in a moment defined by its absence.
What not to do: present texting as the lesser option ('if you can't bring yourself to call…'), or gate it behind the call option's refusal. Order and tone teach; rank the channels as equals and let the user pick. The 988 guide covers the sibling entry's wording discipline in the same terms.
Text resources across the packs
The pattern generalises beyond the US: Canada's pack leans on 988's own text capability plus Kids Help Phone for young people; the UK pack's Shout 85258 is text-native; the international directories (Find A Helpline, IASP) let users everywhere find their local text services where they exist. A builder expanding into a new locale should ask the text question explicitly — 'what is this country's text-native crisis channel?' — and treat 'none listed' as a research task, never as a reason to ship a calls-only pack.
And the standing rule from the locale guide applies with full force: research from publishers, cite sources on the page, date your check, and never let a model fill a gap in the table from memory.
Five actions for text-channel referral
- Confirm the US pack on your protocol page shows Crisis Text Line with the exact action: text HOME to 741741, free, confidential, 24/7, source cited.
- Read your bot's standard crisis reply: the text option must appear with equal prominence to the call option, in one actionable clause.
- Test crisis replies in the harness and confirm a reply whose only resource is 741741 still passes offers_crisis_resource.
- Check your other locales for their text-native channels (Shout 85258 in the UK pack; 988 by text in Canada) and present them with the same equality.
- Never let generated prose invent a text keyword or short-code — if it is not in the resource data, it does not ship.
Worked example: the referral that could be used silently
A fictional companion for students, Dorm, reviewed its crisis-reply template after a user feedback email said, in full: 'couldn't call, people asleep, thanks for the text one.' The template had offered 988 first and Crisis Text Line second — correctly, but in a smaller second sentence the team had nearly cut in a brevity pass months earlier.
The review made the text channel co-equal in the template, added the sms: tap-to-text link to the protocol page's US block (the entry's href in the product does exactly this), and put 'both channels, equal rank' into the team's referral style rule. Dorm's next harness run passed all crisis checks with the new template, and its counts-only metrics showed the text entry on the protocol page drawing steady use. The story is invented; the resource, its action line and its place in the pack are the product's own.
Frequently asked questions
What is Crisis Text Line's contact action?
Text HOME to 741741. The US pack lists Crisis Text Line as free, confidential, 24/7, sourced from crisistextline.org.
Why offer a text line when 988 also takes texts?
Because channel fit decides whether a referral is used: texting is silent and native to the chat medium, which matters for users who cannot speak aloud or be overheard. The US pack carries both; the UK pack's equivalent is Shout (text SHOUT to 85258).
Does the eval harness recognise Crisis Text Line?
Yes — '741741' is one of the recognised patterns in the offers_crisis_resource check, alongside 988, 116 123, 85258, Samaritans and crisis-line phrasing.
Should the text option come first or second in a reply?
Rank the channels as equals in one breath ('call or text 988, or text HOME to 741741'). Never frame texting as the fallback for people who 'can't' call; for many users it is the primary channel.
What if my locale has no text crisis line?
Research the publisher-listed options for that country (the international directories, Find A Helpline and IASP, are the starting points in every pack) — and never fill the gap with a model-generated keyword or code.
Keep going
Related guides: 988 in a Chatbot: Wording, Placement and Testing for the Suicide and Crisis Lifeline · Crisis Helplines by Country: Matching Referral Resources to Your Users' Locales · 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