A text after a missed call can reduce uncertainty, but it also creates a new communication channel with consent, identity, privacy, timing, and ownership requirements. The message should help the caller choose a next step without turning a service response into an unapproved campaign.
Decision snapshot
| Decision | Practical approach | Watch for |
|---|---|---|
| Trigger | Which missed calls should receive a message? | Documented eligibility and suppression rules |
| Message | What minimum next step is offered? | Approved identity, purpose, and response text |
| Handoff | Who sees and resolves replies? | Monitored queue and service standard |
h
Separate service response from marketing
h
Control eligibility and timing
h
Write a recognizable minimum message
h
Create a real staff task
h
Test wrong-number and failure cases
Action checklist
- Counsel-reviewed purpose and rules
- Eligibility and suppression logic
- Approved message and opt-out behavior
- Monitored reply queue
- Sensitive-data and emergency handling
- Delivery and loop-failure tests
Working worksheet
Record these fields in the same working document so the decision can be reviewed and handed off:
- Trigger
- Message version
- Queue owner
- Response target
- Suppression or exception
Common failure patterns
- Treating a missed call as broad marketing consent
- Sending replies to an inbox nobody monitors
- Asking for account or health details by ordinary text