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.
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.
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.
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 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.
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.
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 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.
Nothing is sent to a customer until your team has approved the wording and the routes, and each path has been tested.
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.
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.
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.
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.
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.
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.
These are patterns for scoping, not client results.
The customer is sent to the booking page you already run, so the booking stays in your own system.
Writing a booking directly is a separate scope, considered only where your platform allows it.
A caller may ring twice, may already have an open enquiry, and a message may not send.
The workflow answers inside rules your team has approved. Anything it cannot settle reaches a named person.
A phone system or booking platform may already text back a missed call. Check that before adding anything.
These pages cover the calculator, the other enquiry-handling routes and a first conversation.
Supporting information: See this one working · Dental enquiry handling · Salon enquiry handling · Accountancy enquiry handling · Animal-service enquiry handling · Assessments: how the bounded first stage is chosen for your workflow · Pricing: how our work is priced and scoped · Security: the current status of each data-handling item
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.
With your permission, Google Analytics uses cookies to help us understand how this site is used. We remember your choice for six months; you can change it at any time using Cookie settings in the footer. How Google uses data.
Your choice could not be saved. Please check your browser storage settings.