Skip to content

Recover a missed call with a useful next step

This page follows one unanswered call, state by state, from the missed call to a booking link or a named person. It shows what we check, what your team approves and where a feature you already have may be enough.

Missed-call recovery is a bounded workflow that responds to a call a customer made to your number and that nobody answered. It checks the call is eligible, sends a reply your team has approved, offers a next step and passes anything unresolved to a named person. Durward maps your number and provider first, agrees the wording and the routes with you, and tests each path before go-live. It acts only on a call a customer made. Outbound calls and messages are set up separately, and only for people who have agreed to receive them.

What the workflow covers, and what it does not

Missed-call recovery is a bounded workflow that responds to a call a customer made to your number and that nobody answered. It checks the call is eligible, sends a reply your team has approved, offers a next step and passes anything unresolved to a named person. Durward maps your number and provider first, agrees the wording and the routes with you, and tests each path before go-live. It acts only on a call a customer made. Outbound calls and messages are set up separately, and only for people who have agreed to receive them.

What is included

  • A check of the number customers ring, the phone system or provider behind it and whether a missed call can be detected there.
  • Reply wording agreed with your team before anything is sent.
  • A stop rule: a customer who asks to stop gets no further messages from your business through this workflow, and the request is recorded.
  • A route for the customer's answer, to your existing booking link, a described request or a request for a person.
  • Rules for repeat callers, duplicate records and messages that fail to send, with a fallback to a person.
  • A named owner for each unresolved enquiry and a hand-off that carries the conversation with it.
  • A test of each path before go-live, including a failed send and a call outside the agreed rules.

What is not included

  • A message to someone who did not call. This workflow answers a call the customer made and does nothing else. Outbound calls and messages are a separate scope, agreed with you in writing first, and go only to people who have agreed to receive them.
  • Any promise about how quickly a reply is sent or read, or how quickly a person will respond.
  • Support for every kind of number. Withheld numbers, numbers that cannot receive the chosen channel and lines where a missed call cannot be detected are handled by a person.
  • Any assessment of whether a call is an emergency or urgent. A person makes that decision.
  • Writing into your booking platform, unless a separate scope has verified its permissions.
  • A legal view on messaging rules. You approve the wording and the contact route, and you should take qualified advice where the question matters.
  • Replacing a feature of your phone system or booking platform that already does the job.

Which missed calls the workflow replies to

A call qualifies when the call and the number it came from give a clear next step. A missed call alone is not enough.

The customer made the call

The trigger is a call to your number that no one answered. A number taken from a list, a past customer or an old enquiry is not a trigger, because the workflow acts only on a call that was made.

Your number and provider can show a missed call

Some phone systems and booking platforms already report a missed call. Others need call forwarding or another route. If a miss cannot be detected reliably, fixing that comes before any reply.

The caller's number can receive the chosen channel

A number that cannot receive the chosen channel, such as a withheld number, is not replied to, and the call goes to a person. Check each channel's own terms and your provider's conditions before relying on them, particularly for WhatsApp.

A named person owns the replies

A named person or role has agreed to take the replies that need a human. Without one, the first job is to name an owner before any reply is switched on.

How the workflow is set up and tested

Nothing is sent to a customer until your team has approved the wording and the routes, and each path has been tested.

  1. Map the number and the provider

    We check the number customers ring, the phone system or provider behind it, any booking platform and the channels you already use. We note whether a feature you already have covers the case.

    Buyer receives: A fit note naming the detection route, the channel and anything that blocks them.

  2. Agree the reply

    Your team approves the wording, the channel and what the message says about who or what is replying. The wording describes a next step and gives no timing.

    Buyer receives: Approved reply wording, held with your records.

  3. Choose the next step

    The reply offers your existing booking link, a way to describe the request or a way to ask for a person. A booking write is considered only under a separate, verified scope.

    Buyer receives: A route map from each customer answer to a destination.

  4. Set the rules for duplicates and failures

    We define what happens when the same caller rings twice, when an open enquiry already exists, when a message does not send and when a customer answers outside the expected options.

    Buyer receives: Written rules and a test log for each case.

  5. Name the owner and test the hand-off

    A named person receives anything unresolved, unclear or urgent, with the conversation attached. We test each path, including a failed send, before go-live.

    Buyer receives: A hand-off route, a named owner and a record of the test run.

  6. Confirm the scope and the cost sources

    The fixed implementation fee is published on the pricing page and is not repeated here. Charges from your phone, SMS or WhatsApp providers depend on your plan and volume, and they are itemised rather than blended into the fee.

    Buyer receives: A written scope and the provider charges that apply to your setup.

Three situations, and what the workflow does in each

These are patterns for scoping, not client results.

Booking link route

The customer is sent to the booking page you already run, so the booking stays in your own system.

Trigger
A reply from the customer shows they want to book.
Systems or sources
Your existing booking platform and its public booking page.
What the workflow does
Send the booking link and record that it was offered. The workflow does not read or change your diary.
Human checkpoint
Your team confirms or adjusts any booking that needs a person.
Exception route
A customer who cannot use the link, or who asks something else, is passed to a named person.
Success measure
Whether offered links lead to bookings in your own platform, compared with how those calls were handled before.

Verified booking write

Writing a booking directly is a separate scope, considered only where your platform allows it.

Trigger
Your team asks for bookings to be written and the platform offers the permissions needed.
Systems or sources
The platform's API, with permissions your team grants.
What the workflow does
Write only the booking types the verified scope names, and log each write.
Human checkpoint
Your team owns the diary rules, changes and cancellations.
Exception route
A request outside the verified scope, or a write that fails, passes to a person and no booking is assumed.
Success measure
Whether written bookings match the diary, checked on a sample your team reviews.

Repeat callers, duplicates and failed sends

A caller may ring twice, may already have an open enquiry, and a message may not send.

Trigger
The same number rings again, matches an open enquiry or the channel reports a failure.
Systems or sources
The call log, your enquiry records and the messaging provider's delivery status.
What the workflow does
Group repeat calls into one enquiry, avoid a second reply on an open one and pass a failed send to a person with the reason.
Human checkpoint
A named person decides what happens next when a message could not be sent.
Exception route
A number that cannot be messaged is not tried on another channel unless your team has approved that route.
Success measure
How many calls were grouped, how many sends failed and how each failure was resolved.

Human ownership, and who does what

The workflow answers inside rules your team has approved. Anything it cannot settle reaches a named person.

Durward prepares

  • The reply wording, the channel choice and the route map, for your approval.
  • Rules for eligibility, repeat callers, duplicates and failed sends, written down and tested.
  • A hand-off that names who receives each type of unresolved enquiry and what they see.

Your team keeps

  • Approval of the reply wording, the channel and the contact rules before anything is sent.
  • The booking diary, including every change and cancellation.
  • Every question about urgency, safety or treatment, and every enquiry that is unclear, sensitive or still open.
  • The decision on which messages are appropriate to send, with qualified advice where it matters.

When a feature you already have may be enough

A phone system or booking platform may already text back a missed call. Check that before adding anything.

A workflow adds value when

  • Calls, bookings and enquiry records sit in more than one system and nothing joins them.
  • The reply needs to reach a booking link, an assistant or a named person depending on what the customer says.
  • You need rules for repeat callers, duplicates and failed sends that a built-in text-back does not offer.

Use what you already have when

  • Your phone system or booking platform already sends a text-back you are happy with, and someone owns the replies.
  • A missed call cannot be detected reliably on your number. Fix that first.
  • The aim is to contact people who have not called. This workflow does not do that, and outbound is set up separately.

Bring one phone number and one booking route

Tell us which number customers ring, what sits behind it and who takes the replies. We will say plainly if your current system can already do the job.