Pre-Visit Instruction Texts: Clinic Templates
A patient who arrives unprepared costs the clinic twice: once in the delay while forms are completed or insurance is chased, and again in the downstream appointments that start late because of it. Most of that friction is preventable with one well-timed text sent before the visit.
This is a working template library for pre-visit instruction texts, organized by scenario, with the timing rules and compliance wording that keep the messages useful and HIPAA-safe.
The Rules Before the Templates
Three constraints shape every template below:
Keep clinical detail out of SMS. Standard text messages cross the carrier network unencrypted. HIPAA's Security Rule requires covered entities to assess transmission risk for electronic PHI (45 CFR 164.312(e)), and the defensible pattern is logistics-only bodies: times, locations, documents to bring. Procedure names, prep protocols tied to procedures, and anything implying a diagnosis belong in your patient portal; the text links to the portal rather than carrying the content.
Send from a consented, registered line. Automated texts require prior express consent under the TCPA (47 U.S.C. 227), and organizational SMS at volume should run through registered A2P channels so carriers deliver rather than filter it.
One message, one job. A pre-visit text that tries to cover arrival time, forms, parking, insurance, and prep in a single wall of text gets skimmed. Split by priority; lead with what changes patient behavior.
Timing: When Instruction Texts Should Fire
| Instruction type | Send window | Why |
|---|---|---|
| Forms and portal registration | 3-5 days before | Patients need time to complete them |
| Fasting or prep logistics | 48-72 hours before | Behavior starts the day before |
| Arrival, parking, documents | 24 hours before | Close enough to remember |
| Telehealth link and tech check | 24 hours + 15 minutes before | Two touches; the second is the working link |
The instruction text is a separate message from the appointment reminder. Reminders confirm attendance; instructions change how the patient shows up. Combining them buries the instruction under the confirm/cancel decision.
Template Library
Replace bracketed fields; keep messages under about 320 characters where possible so they arrive as one or two segments.
Arrival and check-in
- "[Clinic]: You're set for [day] at [time]. Please arrive 15 minutes early to complete check-in. Bring a photo ID and your insurance card. Reply HELP for questions."
- "[Clinic]: Reminder for [day] at [time]. Our entrance is on [street]; free patient parking is behind the building. Check in at the second-floor desk."
New patient paperwork
- "[Clinic]: Welcome! Before your visit on [day], please complete your new patient forms here: [portal link]. Finishing them ahead saves time at check-in."
- "[Clinic]: We still show your intake forms incomplete. Finishing them tonight keeps your [day] appointment on time: [portal link]."
Insurance and payment
- "[Clinic]: For your visit [day], please bring your current insurance card and a payment method for any copay. Questions about coverage? Call [number]."
- "[Clinic]: Your insurance on file may have changed. Please bring your newest card [day] so we can update it at check-in."
Fasting and preparation logistics
Keep the procedure unnamed; the portal carries the specifics.
- "[Clinic]: Your appointment on [day] at [time] requires preparation beginning the day before. Full instructions are in your patient portal: [link]. Reply if you cannot access them."
- "[Clinic]: Reminder: no food or drink other than water after midnight before your [day] appointment. Details in your portal: [link]."
Medications and documents
- "[Clinic]: For [day], please bring a list of all current medications and dosages, or the bottles themselves. It helps us keep your record accurate."
- "[Clinic]: If you have recent test results or records from another provider, bring copies [day] or upload them here: [portal link]."
Telehealth visits
- "[Clinic]: Your video visit is [day] at [time]. Join from a quiet spot with good signal: [link]. A quick test of your camera and sound tonight prevents delays."
- "[Clinic]: Your video visit starts in 15 minutes. Join here: [link]. If the link fails, call [number] and we'll connect you."
Children and accompanied patients
- "[Clinic]: For [child first name]'s visit [day], a parent or legal guardian must be present and should bring photo ID and the insurance card."
- "[Clinic]: If someone else will bring your child [day], please call [number] beforehand so we can note authorization in the chart."
Weather, delays, and same-day changes
- "[Clinic]: We're open and your [time] appointment is on as scheduled today. Please allow extra travel time for road conditions."
- "[Clinic]: Our office is closing early today due to weather. Your appointment will be rescheduled; we'll text options shortly. Nothing is needed from you now."
Building the Sequence, Not Just the Message
Templates work best as a chain triggered by appointment type. A new-patient physical might fire forms at day 5, insurance at day 2, and arrival at day 1; a telehealth follow-up needs only the two link messages. Map each appointment type in your scheduling system to its instruction chain once, and the workflow runs itself. This is one layer of the larger lifecycle described in our patient text messaging workflow guide.
Two-way handling completes it. Every instruction text generates replies, "where do I park," "the portal link won't open," "can my daughter drive me." Route structured questions to automated answers and the rest to a staffed queue. An unanswered reply teaches patients to ignore the channel.
Measuring Whether Instructions Work
Pick operational measures, not vanity ones: percentage of new patients arriving with forms complete, average check-in duration, late-start rate for first appointments of the day, and portal-link click-through on prep messages. Run the comparison against the weeks before launch. Practices typically find the forms-completion message earns its keep first, because every completed form is minutes recovered at the front desk.
Seasonal campaigns follow the same template discipline; the vaccination reminder playbook shows the same structure applied to outreach rather than preparation.
Frequently Asked Questions
Can I name the procedure in a prep text?
Avoid it. A procedure name in an unencrypted SMS ties an identifiable patient to specific care, which is the kind of disclosure the HIPAA Security Rule's transmission-risk analysis exists to prevent. Send the logistics by text and put procedure-specific prep in the portal behind a login.
How far ahead should pre-visit texts go out?
Match the window to the action: forms need 3 to 5 days, prep behavior 48 to 72 hours, arrival logistics 24 hours. Anything sent more than a week out is forgotten; anything sent only hours before cannot change behavior that had to start earlier.
Do instruction texts need patient consent?
Yes. Automated texts require prior express consent under the TCPA. Capture texting consent at intake or booking, document it, and honor opt-outs immediately. Instructions tied to a scheduled visit sit comfortably within healthcare-related messaging once that consent exists.
Should instructions and reminders be one message?
No. The reminder's job is a confirm/cancel decision; the instruction's job is preparation. Combined messages bury one job under the other. Send the reminder in its own slot and the instruction in its own window.
What if a patient replies with a clinical question?
Staff should never answer clinical questions over SMS. The reply directs the patient to a phone call or secure portal message, and your routing rules should flag those replies for prompt human follow-up.
Instructions That Send Themselves
FRANSiS triggers instruction chains from your schedule automatically, appointment type in, right message at the right hour out, with a signed BAA included and an AI Powered Helper answering the routine replies. Contact us to set up your template library.
