missed-call-textback
Skill0 starsChanged 5 months agoMITView on GitHub
Writes SMS text-back scripts and follow-up flows for missed customer calls so the business saves the job before the caller dials a competitor. Use when the user mentions missing calls, wants automatic text-back messages, or says things like "we keep missing calls", "write a text for when we can't pick up", or "missed call follow-up texts".
In this repository11 other files it gives its agents.
- cold-email-personalizerSkill
- google-business-profile-optimizerSkill
- invoice-chaserSkill
- landing-page-critiqueSkill
- local-seo-auditSkill
- midwest-modeSkill
- proposal-writerSkill
- review-responderSkill
- service-page-writerSkill
- viral-hooksSkill
- website-conversion-auditSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Ask the one question that starts the job: for trades, "What's going on and what town are you in?" For salons/dental, offer the booking link.
- Distinctive: line 24
Keep it under ~300 characters (two SMS segments).
- Distinctive: line 39
Voicemail left vs. no voicemail: if they left one, reference it ("Got your voicemail about the water heater — few quick questions") and …
- Distinctive: line 65
Don't send "Your call is important to us." It's the sound of a company that won't call back.
- Distinctive: line 66
Don't ask for details they already left in a voicemail.
- Distinctive: line 67
Don't send more than 3 messages total without a reply.
- Distinctive: line 68
Don't let an auto-text promise something no one will honor ("we'll call you right back" at 11 p.m.).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Missed-Call Text-Back
A caller who hits voicemail is usually calling the next business on the list within two minutes. A text that lands in those two minutes keeps you in the running; the goal of the first message is not to close the job — it's to stop the next dial.
Step 1 — Intake
- Business type and the #1 reason people call (book, quote, emergency, question)
- Business hours, and whether anyone monitors texts after hours
- Booking link or quote form URL, if one exists
- Phone system: does it support auto-text on missed calls (most VoIP and tools like a business-texting platform do), or will a human send these manually?
- Is the caller base mostly new leads, existing customers, or both?
Step 2 — First-message rules
- Send within 5 minutes. At 30+ minutes the caller has usually committed elsewhere; still send it — some haven't.
- Name the business and a real first name. "It's Dan at Ridgeline Plumbing" outperforms "Thank you for contacting Ridgeline."
- Acknowledge the miss without groveling: "Sorry we missed you" once, no double apology.
- Ask the one question that starts the job: for trades, "What's going on and what town are you in?" For salons/dental, offer the booking link. For restaurants, hours/reservation info.
- Keep it under ~300 characters (two SMS segments). One question, not three.
- A booking link belongs in the first message only when booking is obviously why they called; otherwise ask the question first — replies start conversations, links end them.
Step 3 — Build the flow, not just the message
During hours (someone can take over):
- T+2 min: text-back with the opener question.
- On reply: a human takes over within 5 minutes. The auto-text buys time; a bot-feeling thread loses the job.
- T+1 hour, no reply: one nudge — "Still happy to help if you need us — want me to call you back?"
- Next morning, no reply: final touch, then stop. "If you got sorted elsewhere, no worries at all. We're at [number] if anything comes up."
After hours:
- Immediate: set expectations honestly — "It's after hours at [business], but I still get these. What's going on?" For emergency trades, include the emergency option: "If it's urgent (burst pipe, no heat), reply URGENT and I'll call you."
- 8 a.m. next day: "Morning — following up on your call last night. Want me to get you on today's schedule?"
Voicemail left vs. no voicemail: if they left one, reference it ("Got your voicemail about the water heater — few quick questions") and skip the generic opener. No voicemail = assume high shopping intent, lead with the question.
Known customer: drop the business intro, keep the name. "Hey Sarah, it's Dan — saw we missed you. Everything okay with the furnace?"
Industry-specific script sets (trades, salon, dental, restaurant, auto) are in references/scripts.md.
Step 4 — Deliver
**Flow:** After-hours missed call — new lead, emergency-capable trade
T+0 (auto): [message]
On URGENT: [human calls; holding text if delayed]
8:00 AM: [message]
+1 day: [final message]
**Handoff rule:** [who takes over, within how many minutes]
**Setup note:** [how to wire this into their phone system, if asked]Compliance (one paragraph, not a law degree)
Texting back someone who just called you is a reply, not marketing — but always honor STOP immediately, identify the business in the first message, and if using a texting platform with a new number, complete its A2P 10DLC registration or messages will silently fail. Don't add missed callers to marketing lists without separate consent.
What not to do
- Don't send "Your call is important to us." It's the sound of a company that won't call back.
- Don't ask for details they already left in a voicemail.
- Don't send more than 3 messages total without a reply.
- Don't let an auto-text promise something no one will honor ("we'll call you right back" at 11 p.m.).
Built by Reef — AI systems for small business → https://buildwithreef.com
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

