Introduction

SMS reminders and follow‑ups reduce missed appointments, accelerate lead conversion, and keep customers informed without adding staff. My AI Front Desk includes a two‑way SMS Texting Agent, calendar scheduling, CRM sync via integrations (e.g., Zapier), automated notifications, and an AI Phone Receptionist that can escalate calls when texts indicate urgency. Customers deploy in minutes, handle unlimited simultaneous conversations, and centralize transcripts for audit and optimization (see: Features, Tutorials, Industries, Reseller pages in the My AI Front Desk knowledge base).

Outcomes to target

• Reduce no‑shows and late cancellations (common results reported in case studies include 25–40% improvements in show rates for service and healthcare use cases).

• Increase “speed‑to‑lead” (follow up within 5 minutes to lift connect and booking rates).

• Raise confirmation rates to >85% for scheduled appointments.

• Capture reschedules automatically without phone tag.

Building blocks in My AI Front Desk

• Two‑way SMS Texting Agent: conversational reminders, confirmations, reschedules, and FAQs.

• Calendar/booking sync: send smart booking links; writebacks prevent double‑booking.

• CRM + analytics: log messages, outcomes, and sources in the AI CRM/Smart Tickets; trigger automations via integrations.

• AI Phone Receptionist handoff: if a text indicates “urgent,” transfer or place an outbound call automatically.

• Controls: quiet hours, throttling, templates, variables, and opt‑out handling (STOP) with automatic suppression.

Ready‑to‑use reminder templates (T‑24h and T‑2h)

Use these verbatim or adapt. Include your business name, clear CTA, and required compliance language.

Use case	T‑24h template	T‑2h template
Service visit (home services, auto, etc.)	Hi {first_name}, {business_name} here. Confirming your {service} on {date} at {time} {tz}. Reply C to confirm, R to reschedule, or Q with questions. Msg&data rates may apply. Reply STOP to opt out.	We’ll see you in ~2 hours for {service} at {address}. Tech: {tech_name}. Need to reschedule? Reply R. Reply STOP to opt out; HELP for help.
Office appointment (consultation, legal, salon, studio)	Hi {first_name}, reminder of your {appointment_type} at {time} {tz} on {date} with {staff_name}. Reply C to confirm, R to reschedule, or Q with questions. Msg&data rates may apply. STOP to opt out.	You’re up in ~2 hours at {location}. Running late? Reply L with ETA or R to reschedule. HELP for help; STOP to opt out.
Class/session (fitness, wellness, tutoring)	Hi {first_name}! Your {class_name} is tomorrow at {time} {tz} at {location}. Reply C to confirm, G to grab a spot for a friend, or R to change time. Standard rates apply. STOP to opt out.	{class_name} starts in ~2 hours. Need to switch? Reply R for options. Bring: {items}. HELP for help; STOP to opt out.

Notes

• Always include brand identity ({business_name}) and an easy action keyword (C/R/Q).

• Use branded links (no public URL shorteners) for booking pages to preserve deliverability.

• For healthcare use cases, avoid PHI over SMS. My AI Front Desk is not HIPAA‑certified; keep messages generic (e.g., “appointment” vs. diagnosis/procedure).

Two‑way flows that resolve without staff

Design short, unambiguous paths. The SMS Agent and AI Receptionist can coordinate via workflows.

• Confirmation flow

• System: “Reply C to confirm, R to reschedule.”

• If C: “Thanks! See you {date} {time}. Reply R to change.” Mark confirmed in calendar/CRM.

• If no reply: auto‑retry T‑12h (opt‑in dependent), then notify team.

• Reschedule flow

• User sends R → System returns 2–3 time options from live calendar or a booking link.

• User picks a slot → System books, sends updated invite and directions; closes ticket.

• No‑show recovery flow

• Trigger if status = missed → “We missed you today. Want to rebook this week? 1) {slot_a} 2) {slot_b} 3) Link for more times. STOP to opt out.”

• Lead follow‑up (speed‑to‑lead)

• Trigger when a new lead arrives → “Hi {first_name}, this is {business_name}. Want to schedule a quick {service} consult? 1) Today 2) Tomorrow 3) View times.”

• If no response: one polite nudge T+24h, then pause unless user re‑engages.

Guardrails

• Quiet hours: pause non‑urgent outreach outside local 8am–8pm (configurable).

• Frequency caps: e.g., ≤3 reminder messages per appointment (T‑24h, T‑2h, T‑10m optional).

• Respect STOP/UNSUBSCRIBE/CANCEL/QUIT/END across all campaigns.

10DLC (U.S. A2P messaging) essentials

If you send application‑to‑person SMS to U.S. recipients from local numbers, carriers require 10DLC registration. Your messaging provider typically facilitates this; prepare:

• Brand registration: legal business name, EIN/Tax ID, address, website, contact.

• Campaign registration: use case (e.g., “appointment reminders”), sample messages (include “STOP to opt out” and “Msg&data rates may apply”), opt‑in method, and message frequency.

• Number assignment: map registered campaigns to your 10DLC sender(s).

• Content rules: avoid SHAFT content (sexually explicit, hate, alcohol to minors, firearms, tobacco) and prohibited claims; stay consistent with approved samples.

• Link policy: prefer branded domains; avoid public URL shorteners to reduce filtering.

• Opt‑in proof: collect and retain auditable consent (source, timestamp, method).

• Keywords: support STOP (and synonyms), and HELP with a reply that provides your business name, support contact, and opt‑out instructions.

Tip: Toll‑free SMS has a separate verification path. If you use toll‑free numbers, complete that verification before scale. For short codes, use the dedicated short‑code program.

Compliance checklist (save this)

Use this list before you turn campaigns on. My AI Front Desk tools (AI CRM, Smart Tickets, dashboards, transcripts) help evidence compliance.

• Consent

• You have explicit, documented opt‑in for the specific purpose (reminders/marketing).

• You can prove who opted in, when, and how (form, web chat, phone IVR, POS).

• Disclosures in first message and/or opt‑in form

• Business name, purpose, message frequency, “Msg&data rates may apply,” STOP/HELP language, link to privacy policy/terms where applicable.

• Keyword handling

• STOP, UNSUBSCRIBE, CANCEL, END, and QUIT immediately suppress the number; send a one‑time confirmation of opt‑out. HELP returns support contact and opt‑out instructions.

• Quiet hours & frequency caps

• Configure local‑time windows and maximum daily sends per user.

• Content safety

• No PHI or sensitive personal data in SMS. For healthcare, keep wording generic. For age‑restricted products, implement age gating and geo compliance.

• Identity & consistency

• Every message identifies {business_name}. Content matches your registered 10DLC use case and samples.

• Deliverability hygiene

• Use branded links, consistent templates, and avoid excessive emojis/ALL CAPS. Monitor block rates and carrier feedback.

• Data retention & rights

• Store only what you need. Honor deletion requests. Log consent changes and opt‑outs.

Implementation in My AI Front Desk (10‑minute quick‑start)

1) Create variables and templates

• Add placeholders: {first_name}, {appointment_time}, {location}, {staff_name}, {booking_link}.

• Load the T‑24h/T‑2h templates above and your HELP/STOP responses.

2) Map data

• Connect your calendar and CRM with integrations; confirm fields for appointment time, location, staff, and status.

3) Define triggers and quiet hours

• Triggers: new booking, booking change, status=no‑show, new lead.

• Quiet hours: e.g., 8am–8pm local; exclude holidays if needed.

4) Two‑way logic

• Define keywords (C, R, L, Q) and natural‑language intents (“running late,” “move to tomorrow”).

• Add reschedule options or a booking link pull from live availability.

5) Fail‑safes and escalation

• After two unanswered texts, open a Smart Ticket for a human or launch an AI Phone Receptionist call.

6) Test and launch

• Dry‑run with internal numbers; confirm STOP/HELP behavior, time‑zone accuracy, and calendar writes.

• Enable campaign and monitor the first 100 sends in dashboards.

Optimization playbook

• A/B copy: test confirmation keyword (C vs YES), tone (formal vs casual), and CTA order.

• Timing: T‑48h + T‑3h may outperform T‑24h + T‑2h depending on industry; test.

• Personalization: add staff name, parking tips, or prep checklist to reduce day‑of friction.

• Metrics to watch: confirmation rate, reschedule cycle time, opt‑out rate (<1% target), carrier error codes, deliverability by template.

Frequently asked questions

• Do I need 10DLC to send reminders?

• In the U.S., A2P messaging from local numbers generally requires 10DLC registration. Coordinate through your messaging provider.

• What if I operate multiple locations?

• Register the brand once; define separate campaigns or sub‑use‑cases if content or opt‑in flows differ. Use distinct numbers per location to maintain local presence.

• Can I text protected health info (PHI)?

• Do not send PHI. My AI Front Desk is not HIPAA‑certified; keep messages generic (time/place/office name) and route sensitive questions to phone.

• What keywords must I support?

• STOP, UNSUBSCRIBE, CANCEL, END, QUIT (opt‑out); HELP (support reply). You can also offer C (confirm), R (reschedule), L (late), Q (question) for convenience.

Key takeaways

• Start simple: T‑24h and T‑2h reminders with C/R flows cover most use cases.

• Make compliance effortless: STOP/HELP, opt‑in proof, quiet hours, and branded links.

• Close the loop: log every outcome; reschedule automatically; escalate only when needed.

• Iterate weekly: update templates and timing based on deliverability and response data.