Sending SMS Follow-Ups from Voice Agents

SMS follow-ups are one of the highest-ROI additions to any voice agent deployment. The caller just had a conversation; they know the appointment time, the tracking link, the next step. But people forget. A quick SMS with the details right after the call makes the conversation stick. Confirmation rates go up. No-show rates drop. Customer satisfaction rises measurably. The integration is conceptually simple, but the compliance and deliverability landscape has real gotchas you need to plan for.

This piece walks through SMS follow-up integration for voice agents, the A2P 10DLC landscape, and the patterns that keep your deliverability healthy.

TL;DR

• SMS follow-ups dramatically improve call outcomes — confirmation, retention, task completion.
• A2P 10DLC (for standard 10-digit numbers) registration is required for reliable delivery at scale.
• Short codes, toll-free SMS, and international each have different compliance profiles.
• TCPA applies: consent is required for any non-transactional SMS.
• Design for deliverability: clear sender, concise content, opt-out mechanism.

The cases where SMS wins

Voice agents benefit from SMS follow-up in many scenarios:

• Appointment confirmations — "Your appointment is Thursday at 2 PM. Reply C to confirm, R to reschedule."
• Tracking information — "Your order tracking: ."
• Payment confirmations — "Your payment of $X is received. Confirmation: ."
• Callback confirmations — "A callback is scheduled for 10 AM tomorrow."
• Summary of complex conversations — "Summary of our call: ."
• Links to self-service — "Manage your account: ."
• Appointment reminders (proactive outbound) — "Reminder: appointment tomorrow at 2 PM."

Each of these closes a loop the voice call started.

A2P 10DLC — the compliance floor

For SMS from standard 10-digit phone numbers in the US, A2P 10DLC applies. Key concepts:

A2P — Application-to-Person. Messages sent by businesses (as opposed to P2P, person-to-person).

10DLC — Long code (10-digit phone number). As opposed to short codes or toll-free.

Registration process:

1. Brand registration. Your company registers with the Campaign Registry (via your provider — Twilio, Bandwidth, etc.).
2. Campaign registration. Specific use cases registered — notifications, 2FA, marketing, customer care.
3. Throughput tier determined by verification completeness.
4. Message content filtering. Carriers block messages that don't match registered campaigns.

Without A2P 10DLC registration, your SMS:

• Gets throttled heavily.
• Suffers from low deliverability.
• May trigger carrier blocks.

See A2P 10DLC explained for voice agent builders.

Alternatives to 10DLC

Toll-free SMS. 8xx numbers can send SMS. Requires toll-free verification (separate process from 10DLC). Usually faster approval but stricter content requirements.

Short codes. 5–6 digit numbers. Expensive ($500–$1500/month), slow approval (2–8 weeks), but high throughput and deliverability. Used for high-volume consumer-facing messaging.

International. Each country has its own rules. Registration processes, prefix requirements, content filtering.

TCPA compliance

SMS from voice agents needs TCPA-compliant consent:

• Prior express consent (PEC) for non-marketing SMS (transactional).
• Prior express written consent (PEWC) for marketing SMS.
• Consent typically captured at:
  • Signup (SMS opt-in checkbox).
  • During the voice call (explicit ask).
  • At point of purchase.

Document consent. Store it. Audit it.

Opt-out must work immediately. STOP keyword universal.

See TCPA compliance for AI-powered outbound calls.

The integration

Voice agents typically send SMS via:

• Twilio Messaging API. Most common.
• Bandwidth, Telnyx, Plivo. Alternatives.
• AWS SNS. For low-volume transactional.
• SendGrid, Mailgun. Have SMS features but primarily email-focused.

Outbound message:

POST https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/Messages.json
{
  "To": "+15551234567",
  "From": "+15551112222",
  "Body": "Your appointment with Dr. Lee is confirmed for Thursday, April 18th at 10 AM. Reply C to confirm, R to reschedule."
}

Timing

After a voice call ends:

• Immediate (0–30s). Send confirmation or summary.
• Delayed (hours to days). Reminders or follow-ups.
• Event-triggered. Status changes in downstream systems trigger new SMS.

Immediate is the most impactful. Within 30 seconds of call end, SMS arrives.

Message design

Good SMS:

• Short. Under 160 characters when possible (one SMS segment).
• Clear sender. "Westside Dental:" prefix, in case they don't recognize the number.
• Specific. "Appointment Thu 4/18 10 AM with Dr. Lee." Not "Your appointment is confirmed."
• Actionable. Include a next step (link, reply keyword).
• Opt-out. "Reply STOP to unsubscribe." Required for most campaigns.

Example:

"Westside Dental: Your cleaning is confirmed Thu 4/18 10 AM with hygienist Sarah. Reply C to confirm or R to reschedule. Reply STOP to opt out."

Templated vs dynamic

• Templated. Pre-approved message formats with variable insertion. Safer for 10DLC compliance.
• Dynamic. LLM-generated content. More natural but higher compliance risk (carriers may filter novel content).

Most production SMS follow-ups are templated for compliance and deliverability.

Reply handling

If your SMS asks for a reply (e.g., "Reply C to confirm"):

• Inbound webhook from your messaging provider on incoming SMS.
• Parse keyword (C, R, STOP, HELP, etc.).
• Take action (update appointment, trigger voice callback, etc.).
• Confirm back via SMS.

Model this as another webhook → workflow.

Deliverability monitoring

Track:

• Delivery rate. % of sent messages that delivered.
• Response rate. % of callable-response messages that got a reply.
• Opt-out rate. % of recipients who STOP.
• Carrier filtering. Messages filtered by specific carriers.
• Error codes. Undelivered reasons.

Low delivery rates (under 95%) signal a compliance or content issue.

MMS (multimedia)

For sending images, documents, or audio:

• Same compliance framework.
• Costs more per message.
• Useful for sending maps, receipts, or instruction images.

Use sparingly; SMS is usually sufficient.

International SMS

Complexity multiplies:

• Sender ID rules vary (US requires 10-digit or short code; other countries allow alpha-senders).
• Content rules vary (some countries require native-language content).
• Carrier relationships vary (deliverability by country).
• Registration — country-specific processes.

Start domestic. Add international deliberately.

Common pitfalls

Shipping SMS without 10DLC registration. Low deliverability, delays, blocks.

Unclear sender. "From 555-1234: confirm your appointment" — customer doesn't know who. Always identify in the body.

Long messages. Over 160 characters get split into multiple segments. Costs more, arrives out of order occasionally.

No opt-out path. TCPA violation. Always include STOP keyword instructions.

Unresponsive reply handling. Customer replies C to confirm; nothing happens. Broken flow.

Aggressive follow-up cadence. 3 SMS in 10 minutes feels like spam. Space out.

Example flow: appointment confirmation

# Voice call ends at 14:23
# Appointment booked for Thu 4/18 10 AM

# Within 30 seconds:
SMS to +15551234567:
"Westside Dental: Your cleaning is confirmed Thu 4/18 10 AM with hygienist Sarah. 
Reply C to confirm or R to reschedule. Reply STOP to opt out."

# 24 hours before appointment (Wed 10 AM):
SMS:
"Reminder: Your cleaning is tomorrow Thu 4/18 10 AM at Westside Dental. 
Reply R to reschedule. STOP to opt out."

# Morning of appointment (Thu 7 AM):
SMS:
"Reminder: Cleaning today at 10 AM. Address: 123 Main St. See you soon!"

# If caller replies R:
→ Trigger voice callback or direct them to online rescheduling

Voice + SMS orchestration

Best deployments use SMS as the written trace for voice conversations:

• Every appointment booking triggers SMS confirmation.
• Every callback commitment triggers SMS confirmation.
• Every complex conversation triggers SMS summary.
• Follow-up questions can be handled via SMS rather than voice.

This cross-channel pattern meaningfully improves outcomes.

Related reading

• How to Port a Phone Number to Your Voice Agent
• Twilio + Voice Agents: A Complete Guide
• Sending Voice Agent Transcripts to Slack
• Connecting Voice Agents to Snowflake or BigQuery
• Setting Up Toll-Free Verification for AI Calling

FAQ

How much does SMS cost? Per-message in US: $0.008–$0.015 for 10DLC, more for toll-free. Plus registration fees.

Can the AI read incoming SMS? Via webhook yes — incoming SMS fires a webhook to your integration.

What about rich messaging (RCS)? Emerging but limited carrier support. SMS and MMS still dominate.

How do we handle customers without phones? Fallback to email if available. Confirm preferred channel during signup.

Do we need explicit opt-in during the voice call? For marketing, yes. For transactional (appointment confirmations the caller just asked for), usually covered by broader consent but check your compliance counsel.