What to reply when a customer says 'I missed your call'

A customer texts 'I missed your call.' Here is the reply that identifies them, asks one question, and sends a form link instead of back-and-forth.

When a customer texts "I missed your call," you have a warm lead and about a minute of their attention. The reply that works recognizes the caller from their number, asks one question, and sends a short form or booking link, instead of starting a back-and-forth that often ends with nobody booked. Here is the wording, the routing, and the setup.

Start from the contact form template

What the text actually means

Front-desk staff usually can't tell why someone is writing. It might be a reply to your automatic missed-call text. It might be someone returning a voicemail, or a person who saw an unknown number and is calling back without context. The message is the same four words every time, and the intent behind it differs.

The default human reply is "Hi, who is this?", followed by "What can we help with?", followed by "When are you free?" Each message gives the person a chance to get pulled back into their day. By the third question, a plumber with an open slot on Thursday is waiting on someone who has stopped looking at their phone.

You already know more than you think. You have the number they texted from, the number they called, and probably a customer list. That is enough to skip the first question entirely.

The four parts of the reply

A good reply has four parts, in this order.

Recognize them. Look the number up in your customer list or CRM. If it matches, use the first name and, if you have it, the type of the last job. If it doesn't match, say nothing about who they are.
Ask one question, the one that decides which link to send. It should be answerable in a word or two: "New job, or something we already worked on?"
Send one link. Not a menu of three. A short form with a handful of fields, or a booking link if the person only needs a time.
Leave an exit. "Or reply CALL and we'll ring you back." Some people hate forms, and a reply thta traps them loses them.

A known customer might see this:

Hi Maria, thanks for getting back to us. Is this about a new job or something from your last visit? Either way, this takes under a minute: forms.yourbusiness.com/callback. Or reply CALL and we'll ring you.

An unknown number gets the same shape without the name:

Hi, thanks for getting back to us. Are you looking for a quote or to book a visit? This takes under a minute: forms.yourbusiness.com/callback. Or reply CALL and we'll ring you.

Keep it under two short sentences plus the link. A long reply reads like a form letter, and people skim it.

Routing map

The AI should not decide which URL to send. It should classify the message, and your automation maps the class to a link. That keeps the model from inventing a URL or promising a slot you don't have.

What the customer says	Class	What goes out	Who is notified
"I missed your call" (known number)	returning_customer	One question, then the callback form	Front desk, by email
"I missed your call" (unknown number)	new_unknown	One question, then the quote or booking form	Front desk, by email
"Need a quote for the kitchen"	new_quote	Quote request form	Owner or estimator
"Can I come in Tuesday?"	booking	Booking link	Whoever owns the calendar
"Pipe burst" or "no heat" or "locked out"	urgent	No form first; a short text saying a person will call now	Everyone on the urgent rule, plus a Slack alert
"STOP"	opt_out	Nothing; suppress the number	Nobody

Urgent is the row teams forget. A form lnik sent to someone standing in an inch of water is a bad experience, and the urgent class should skip automation and page a human.

Step-by-step setup

Build the form first. Keep it to name, what they need (multiple choice), address or zip code, and a preferred time window. Fewer fields means more completions. Add a hidden field for the phone number and another for the source, set to something like missed-call-text, so every submission shows which text it came from. The help page on hidden fields covers how to pass values in through the link.
Point your SMS provider's inbound webhook at your automation (n8n, Make, Zapier or custom code). Twilio, for example, posts From, To, Body and MessageSid as form-encoded fields.
Look up From in your customer list. Return a first name and last service if found, otherwise caller_known: false.
Send the body and the lookup result to the model with a strict instruction: classify the message, pick one question from your approved list, and return JSON. Do not let it write free-form promises about pricing or availability.
Map the class to a link in code, build the reply from your template, and send it. Log the message and the class against the number.
Connect the form's webhook to your CRM or inbox so a submission closes the thread. Without this, the customer finishes the form and then gets your automated nudge anyway.
Add one follow-up for people who got the link and never submitted, sent the next morning. One, not a sequence.
Make "reply CALL" and "STOP" work. Your provider handles the STOP keyword at the carrier level, but your own system also has to stop sending to that number.

Build your reply form free

What the payloads look like

The inbound text, after your platform parses it:

{
  "From": "+15555550142",
  "To": "+15555550100",
  "Body": "hi i missed your call",
  "MessageSid": "SMxxxxxxxxxxxxxxxx"
}

What you ask the model to return:

{
  "caller_known": true,
  "first_name": "Maria",
  "class": "returning_customer",
  "urgent": false,
  "question_id": "new_or_existing"
}

The reply text is assembled from a template keyed on question_id, with first_name dropped in only when caller_known is true. If the model returns anything outside your list of classes, send the default reply and flag the thread for a person. Failures here are quiet: a model that is 95 percent right stkll sends something odd to a few customers, so log every class and read a sample weekly.

Where the form sits in the system

This is the middle step of our Missed-Call Text-Back & Reactivation system. A missed call fires the first text, the customer's reply gets classified, and the form or booking link turns a vague "I missed your call" into structured details your team can act on. The same form works for the quarterly reactivation texts to your dormant list, with a different source value in the hidden field.

For the form itself, Qwenvo is a completely free form builder thqt our team builds, and its contact form template is a quick starting point. Several things that matter for this workflow are free there:

Webhooks to any URL, so Zapier, Make and n8n can pick up submissions.
Partial submissions, so you can see who opened the link and gave up.
A custom domain on a subdomain like forms.yourbusiness.com, which makes the link in an SMS look like it belongs to you.
No Qwenvo badge, and unlimited teammates so the whole front desk can see results.
AI triage that assigns each submission a category, a priority and a suggested reply, with routing rules that email up to 5 addresses or post to a Slack incoming webhook.

On Tally, custom domains, partial submissions and branding removal are on the Pro plan at $29 a month. Fillout puts custom domains and partial submissions on its $89 a month Business plan. Tally's free plan is generous otherwise, and if you only need a basic form with no custom domain, it works fine.

One limit matters if you run a clinic. Qwenvo has no HIPAA offering, so if the form collects health information, look at a tool that does, such as Jotform's paid plans. For a callback form tat asks "what do you need" and "when," this usually isn't an issue, but keep symptoms and diagnoses out of the form either way.

What to measure

Pick numbers you can read from your own logs:

Time from the customer's text to your first reply. Anything over a minute defeats the point.
Share of inbound "I missed your call" texts that end in a form submission or booking.
Partial submissions on the form. If many people open it and leave, a field is too long or too personal.
Threads that needed a human. Read these every week, because they show you which questions to add.
Opt-outs. A rise after a campaign tells you the message or timing was wrong.

Use the quote request template

Questions teams ask

Should the reply come from a person or the AI?

The first reply should come from the system, because speed is the whole advantage. Anything urgent, emotional or unclear should move to a person right away. Make it easy for the front desk to see the thread and take over, and stop the automation once a human replies.

What if the number doesn't match anyone in our list?

Don't pretend. Skip the name, ask the new-or-existing question, and let the form collect their details. After they submit, you have a new record, and the next call from that number will be recognized.

Is a form or a booking link better?

A booking link suits people who clearly want a time slot, like a salon or a gym tour. A form suits jobs that need details first: a roofing quote, an insurance question, a car problem. When you can't tell, ask the one question and let the answer choose.

Can customers fill the form on their phone?

They will, almost always, because they are already in a text thread. Test it yourself on a phone before launch, with one thumb, on a weak signal. If it takes more than a minute, cut fields.

Next step

Pull your last ten "I missed your call" texts and sort them into three piles: wants a quote, wants a time, wants an update on existing work. Those piles are your routing table, and the biggest one tells you which form to build first.