Twilio toll-free verification for healthcare: what it asks for and how to prepare

What Twilio toll-free verification is

Toll-free verification is the review a toll-free number goes through before it can send text messages in the US and Canada. You tell Twilio who you are, what you will send, and how people agreed to receive it. The review checks that against your website.

It is separate from A2P 10DLC registration, which covers local 10-digit numbers. It is also separate from HIPAA. Verification is about carrier rules for business texting, not about how you protect patient information.

What the Twilio toll-free verification submission asks for

At the time of writing, Twilio's docs list these items. Check the current list before you submit.

• An approved Trust Hub customer profile for your business.
• Business name, website, type, and a notification email for status updates.
• A business registration number, such as an EIN in the US, for every business type except sole proprietors.
• Use case category and a summary of what you will send and why.
• A sample of a real production message.
• The opt-in type (web form, paper form, verbal, by text, QR code or import), with publicly hosted images that show it.
• Expected message volume.
• Optional but worth adding: privacy policy URL, terms URL, opt-in confirmation message, opt-in keywords and a help message sample.

1. Put the compliance pages on your website first

The reviewer opens your website. If the pages are missing, or the business name does not match, the request can be rejected.

Use the same business name on the website, the profile and the submission.

2. Show the opt-in, step by step

• Take screenshots of the form with the checkbox and the consent language in view.
• If staff collect consent by phone or in person, write the script or show the paper form.
• Host the images at public URLs. The reviewer cannot open files behind a login.
• Describe the opt-in in the use case summary in plain words: where, how, and what the person agrees to.

3. Write message samples for healthcare

Samples should match what you will send, name your organization, and include opt-out wording.

• Appointment and admissions follow-up: "Hi, this is [Organization]. We received your inquiry and will call you shortly. Reply STOP to opt out."
• Reminders: a time and a callback number, with no diagnosis or treatment details.
• Keep health information out of the text. Ask the person to call, or use a secure portal, for anything clinical.
• If you plan marketing messages, say so in the use case. Do not submit one use case and send another.

Why toll-free verification requests get rejected

A rejected request comes back with reasons. Twilio lets you edit and resubmit some requests; others need a new one. Before you submit, check for these gaps.

• The website does not load, does not match the business name, or has no privacy policy.
• The opt-in image does not show consent for texts, or the checkbox is pre-checked or bundled with other terms.
• Message samples do not match the use case, or have no organization name or opt-out.
• The business registration details do not match the business record.
• The use case summary is vague about who receives the messages and why.

After approval: keep the opt-in in your CRM

Verification looks at how you collect consent. Your CRM has to respect it every time someone sends a text.

• Save the form checkbox into an "Approved to SMS" field on the lead or contact, in Salesforce, Zoho CRM or your CRM of choice.
• Block sending when that field is not checked. Our Send SMS widget checks it before every message.
• Process STOP replies, so an opt-out turns the field off.
• Connect Twilio through its API, so inbound replies and outbound texts are logged on the record.

Want help getting the website, the opt-in and the CRM ready? Book a free call. For healthcare work, we sign BAAs.