A telehealth platform can use an SMS API to send visit reminders, a link to join the waiting room and a nudge when a clinician is ready. Keep health details out of every text. Ready isn't HIPAA compliant and doesn't sign BAAs, so the message should say that something is waiting, not what it's about.

The shape of telehealth makes texting tempting: patients are on their phones, the visit starts at a set time, and a missed link means a lost slot. Used well, texts raise attendance. Used carelessly, they leak details to a lock screen. For the broader rules, read healthcare SMS compliance requirements.

Texts that work

MomentExampleWhy it's safe
Booking"Your visit with Example Clinic is Tue 3:00 PM. Details are in your account."No condition named
Reminder"Reminder: visit in 1 hour. Join: example.com/v/Xk2"A link, nothing clinical
Waiting room"Your clinician is ready. Tap to join."Pure status
Missed visit"We missed you today. Rebook any time in your account."No reason given

Write each text so a stranger reading it on a lock screen learns nothing about the person's health. Link to a page that requires login before it shows anything clinical.

Link hygiene

Use a short link on your own domain, with a single-use token that expires. Public URL shorteners attract carrier filtering. See carrier filtering of public URL shorteners. Don't include a link in the first text to a new contact if you can avoid it. Link in first message filtering explains why.

Platform architecture

  1. One sub-account per clinic or practice group, created with POST /v1/sub-accounts.
  2. Registration per business. Most approvals take 2 to 7 days.
  3. Template library. Offer fixed templates with merge fields like time and clinic name only. Block free text unless a human reviews it.
  4. Timing. Appointment reminders near the visit can fall in quiet hours. An API text is held only if the window opens within 6 hours, otherwise it returns a 409, so handle that case in code. A reply to a patient who texted within 24 hours can go out at any hour.
  5. Consent at signup. Record when and how the patient agreed to texts, in your own data.

What not to promise

Never promise clinics HIPAA compliance for their texts. Ready isn't HIPAA compliant, and the terms say so. Offer text as a convenience channel, never as a place for results, diagnoses, medications or notes. If a patient texts something clinical, your product should reply with a pointer to the secure portal. See HIPAA-compliant texting for appointment reminders.

Cost

Three one-segment texts per visit across 2,000 visits is 6,000 segments, so 6,000 × ($0.0075 + $0.0045). That's an assumption, and your no-show reduction decides whether it pays back.

Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.

Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.

Frequently asked questions

Can I text a visit link? Yes, if the link reveals nothing and needs authentication before anything clinical shows.

What about prescriptions? Don't text medication names or doses. Point the patient to your secure portal instead.

Do I need separate numbers per clinic? Separate numbers per clinic keep each clinic's identity and its opt-outs clean.

Next step

List every text your platform sends, and strike any that names a condition, a drug or a result.