Lead ResponseUpdated July 4, 2026
Missed Call Text Follow-Up
Create a useful SMS follow-up after a missed call or voicemail.
Use case: Use for local service businesses where missed calls cost revenue.
Prompt
Write a missed-call SMS follow-up for a local service business.
Customer name: {{customer_name}}
Business name: {{business_name}}
Reason for call if known: {{reason_for_call}}
Callback window: {{callback_window}}
Booking link: {{booking_link}}
Return 3 SMS options:
1. Friendly callback offer.
2. Booking-link option.
3. Urgent-service option.
Each message must be under 300 characters. Include opt-out wording only if required by our SMS policy. Do not imply we diagnosed the issue before speaking with the customer.
Quality bar:
- Classify buying intent and missing data separately.
- Recommend one next action, not a menu of vague options.
- Keep customer-facing copy short and easy to approve.
- When prioritizing, use a table with recommendation, why it matters, effort, impact, owner, and verification check.
- Separate evidence, assumptions, recommendations, and limits so the output cannot be misread as a guaranteed claim.
- Flag any wording an AI answer could overstate, misquote, or detach from its source.
Before finalizing, add:
- Missing inputs or assumptions
- Evidence-backed facts and source gaps
- Misread risks or unsupported guarantees
- First 3 actions
- What to verify before actingAdaptation notes
- Check SMS consent and local compliance before automating.
- Use conservative wording for urgent services.
- Track replies and bookings separately.
- Before publishing, verify the output separates evidence, assumptions, limits, and recommendations so AI answers cannot turn guidance into a guarantee.
Quality checks
Strong prompt output should survive these checks before it turns into copy, automation, or a sales action.
- Does it avoid adding friction to hot leads?
- Does it preserve consent and contact-channel boundaries?
- Does it give a route the CRM can actually store?