To set up missed call text back, start with your existing phone system. Check whether it can tell that nobody answered the business call, send a text from a number that accepts replies, and give a member of staff a callback to track. The text acknowledges the call. The callback task tells your team who still needs help.
Some phone systems already cover much of this. For example, RunaCall’s missed-call follow-up guide describes sending a text only when nobody in the call flow answers, suppressing it if the caller gets through during a short delay, and routing replies to a conversations inbox. Ask your own provider to show what happens on your actual business line before buying a separate tool.
Set Up Missed Call Text Back: A Roll-out Plan
Check your current phone system first, then test missed-call texts and callback tracking before a cautious launch.
Check your phone
Ask what happens on your business line when calls go unanswered.
Set the call rules
Set which calls get texts, where replies go and who calls back.
Test call outcomes
Test two missed calls, voicemail and an answer before texts send.
Start with one line
Launch cautiously and check texts, replies and open callback tasks.
Follow one caller through two missed calls and a conversation
Suppose a customer rings a plumbing company while the office team is busy. Nobody answers the first call, and the customer hangs up. The system opens a callback task and queues a text. The customer rings a second time and leaves a voicemail. Staff can see the voicemail alongside the open task, but the second call does not queue another text.
The customer then tries once more and reaches a colleague, even though another extension rings out. If they get through before the queued text goes out, cancel it where the system can reliably recognise the answered call. If the text has already gone out, leave the conversation visible so staff can see any reply. The colleague records what the customer needed and closes the callback task if they handled it. If they only took a message for the engineer, the task stays open with a named owner.
1. Check what your current phone system can detect
Make a test call to your main business number and have a colleague answer it after another extension has rung out. Ask your provider which record shows the outcome of the whole call, including any queue, forwarding destination or answering service. Then repeat the test with voicemail. A call log may show that voicemail or a forwarded destination picked up without telling you whether a person spoke to the caller.
- Call outcome: Can you distinguish a call nobody answered from one a colleague took? Can you separately identify voicemail?
- Texting: Can your existing business number send and receive SMS? If not, ask which number customers would see, where replies would go and whether a number move or forwarding change is actually needed.
- Follow-up: Can staff see the call, voicemail and replies together, assign a callback and record its outcome? Can they find an open task when the same number calls again?
Use the built-in feature if it can do those jobs in one place. If the only trigger you can get is an individual extension ringing out, do not switch on automatic texts across the business line. Start with a staff-reviewed callback list, or enable texts only on a line where you have verified the final call outcome. If the phone system can identify genuinely missed calls but replies and tasks sit elsewhere, an integration between the phone system, inbox and task list can give staff one record to work from.
2. Decide which calls should send a text
Base the text trigger on whether the business answered the call, not whether an individual extension rang out. Wait until the full call route has finished. Treat a busy signal or a caller hanging up in the queue as eligible only if the final outcome confirms nobody answered and you have a usable caller number.
Decide whether voicemail callers should receive the same acknowledgement. Sending it can be useful if voicemail and text replies reach the same team. If a separate team already handles voicemail, you may prefer to exclude those calls from texting while still making sure they appear on that team’s callback list. Test that the phone system can enforce whichever rule you choose.
Keep one open follow-up per caller number for repeat attempts on the same business line, and keep each call visible on that record. Use a repeat-text limit so a flurry of calls or duplicate notifications cannot send multiple acknowledgements. If your system supports a short send delay, test whether it can cancel the queued text when the caller gets through or staff confirm they have already made contact. Use a delay that fits how quickly your team usually picks up or calls back.
Which missed calls get a text, a review or a callback
Clear rule, clear input and a safe next action.
The system can prepare the decision, but a person should check it.
Judgement, sensitivity or consequence makes human ownership the right choice.
3. Write the text and give replies an owner
Identify the business, acknowledge the missed call and give the customer one clear next step. Use hours and response expectations your team can meet. Before enabling automatic sends, check the current rules that apply to your location and type of message with the relevant regulator and your messaging provider, including any consent or opt-out requirements. Keep promotional offers out of this acknowledgement.
During opening hours: Hi, it’s Green Lane Plumbing. Sorry we missed your call. Reply with a brief note about what you need and our office team will follow up.
After hours: Hi, it’s Green Lane Plumbing. Our office is closed. Reply with a brief note about what you need and we’ll pick it up when we reopen.
Send replies to a shared inbox that someone is assigned to check, not to a personal handset. Link each reply to the open callback where possible and alert the person covering the inbox. Create the task when the call is missed, rather than waiting for an SMS reply. If the caller hides their number, don’t attempt to send a text; review any voicemail for contact details. If a text fails or the number cannot receive texts, show that to staff and keep the callback open if there is a number they can ring.
4. Close the callback when the enquiry has been handled
Give each callback an owner and a due time. Record whether staff spoke to the caller, handled the enquiry by text, left a voicemail or got no answer. An outbound dial or a call marked technically complete does not prove the customer was reached. If nobody answered or staff left a message, keep the task open with a next action, or record an explicit stop reason when your follow-up policy calls for it. If the phone system cannot verify contact, leave closure to the person who handled the enquiry.
5. Test the setup before sending texts to customers
Start with staff test numbers and the same main number, extensions and forwarding rules customers use. For each scenario below, check three places: the call log, the text inbox and the callback list.
- Nobody answers: One text is queued or sent, and one assigned callback appears even if the caller never replies.
- Another extension or forwarding destination answers: An unanswered ring on the first extension produces no text or new missed-call task.
- The caller rings twice and leaves voicemail: The second attempt and voicemail are visible, with no duplicate text or task. On a separate test, leave voicemail on the first call to check your chosen voicemail rule.
- The caller gets through on a later attempt: If contact happens within the send delay, verify that the queued text is cancelled where supported. Check that the colleague can find the open task and record whether the enquiry was handled or handed over.
- Staff call back: Test both a callback that reaches the customer and one that rings out or goes to voicemail. Check that an unsuccessful attempt does not close the task.
- The number cannot receive texts or is withheld: Check that an undeliverable text is visible where delivery status is available, that no text is attempted for a withheld number, and that staff can still review the missed call.
- The customer replies after hours: Check the after-hours wording, where the reply lands and who picks it up at reopening.
Before rollout, confirm the send rule, repeat-text limit, reply inbox, callback owner and closure rule with the staff who will use them. Enable missed call follow-up automation on one line first and review the first live cases against the call log. If answered callers are getting texts or open callbacks have no owner, fix that before expanding it.
Connect missed calls to your team’s callback list
Tell ZappFlow which phone system you use, where missed calls and text replies appear, and how staff record a completed callback. We can help you check whether your existing tools cover the process or need connecting.