How do you turn a missed call into a booked appointment?

By the PeachDesk team · Last updated July 31, 2026

Clay diorama of Peach, the PeachDesk mascot, on a wooden deck between two miniature towns linked by bridges

Missed-call to booking automation has four steps: your phone system reports the missed call to PeachDesk through an inbound webhook, a voice agent calls the customer back within moments, the agent qualifies the caller and answers questions, and the call ends in a booked slot or a transfer to your team. An after-hours variant skips the miss entirely by routing the inbound line to the agent in the first place.

This guide covers the detection, the recovery call, the qualification step, and the after-hours variant, plus what the whole loop costs. For the booking side of the flow, see the AI appointment scheduling use case.

How does missed-call detection work?

PeachDesk does not need to own your main business line to recover its misses. When your phone system, PBX, or telephony provider gives up on an unanswered call, it sends an inbound webhook to a public trigger endpoint on your recovery flow. That trigger starts an agent run with the caller's number and any context your system attaches, and the callback goes out moments later on your registered outbound numbers.

The flow runs on the same telephony layer as the rest of PeachDesk: bring your own carrier, manage multiple telephony configurations, and route each number to its assigned agent. See PeachDesk telephony for the supported providers and routing model.

What happens in the recovery call?

The agent opens by naming your business and referencing the missed call, then asks how it can help. That opening does the qualification work: the caller states the reason for calling, and the agent captures intent, urgency, and booking readiness before anything else happens. If the caller cannot talk, the agent can send an SMS during the call with a booking link or an offer to try again later.

For a ready caller, the agent checks live availability in your scheduling system through a custom HTTP tool and offers open slots. When the caller needs a human instead, the agent transfers the live call to your team or an external number, with the answer outcome reported back into the conversation. Either way, the result is written back to your system through a templated HTTP request from inside the workflow or an HMAC-signed webhook to your endpoint.

Webhook delivery is best effort with up to three attempts. Test delivery from the dashboard before going live, and make your receiver idempotent so a retry never double-books a slot.

How does the after-hours variant work?

After hours there is nobody to miss the call, so the recovery pattern inverts: route the inbound number straight to the agent. Each inbound number in PeachDesk routes to its assigned agent, so your main line can ring your team during business hours and the AI agent outside them. The agent answers, qualifies the caller, books a slot through the same HTTP tool, or captures the request and posts it to your system by webhook for morning follow-up.

Callers who ask for a person get an honest answer: the agent offers a booking, takes the details, and sets the expectation of a callback during business hours. Nothing about the call pretends to be human.

What does missed-call recovery cost?

Recovery calls are short, which keeps the per-recovery cost small. Take a two-minute recovery call as a worked example. On the Bibha Plan at $0.06 per minute, that call costs $0.12; at volume, where the rate goes as low as $0.03 per minute, it costs $0.06. The $59 per month Pay As You Go plan meters the same calls against your balance. Full details are on PeachDesk pricing.

Two sourcing modes cut the per-minute charge further. With BYOK you pay your speech and model providers directly at your negotiated rates, and calls on your own keys never consume PeachDesk credits. With Local mode a full open-model stack on your own GPUs serves the call, so there is no per-minute provider charge for locally served inference; you pay for GPU capacity instead. Telephony stays metered by the carrier in every configuration.

Stop losing bookings to missed calls

Connect one webhook from your phone system, record the recovery script, and every miss becomes a callback, a qualified lead, and a booked slot or a warm transfer.

Book a demo Talk to an expert

How fast should the recovery call go out?

As soon as your system reports the miss. The caller still has the phone in hand and the reason for calling is fresh, which is what makes a recovered call convert better than a returned voicemail. In practice your phone system or PBX fires the webhook the moment it gives up on the call, and the PeachDesk trigger endpoint starts the recovery agent run immediately after.

What if the caller cannot talk when the agent calls back?

The agent offers alternatives instead of pushing. It can send an SMS during the call with a booking link or a promise to try again later, and campaign retry rules handle busy and no-answer outcomes with per-reason controls. Every attempt is logged with its disposition, recording, and transcript, so your team can see exactly where each recovered lead stands.

Does this replace my front desk?

No. The agent handles the calls your team already lost: the misses, the after-hours rings, and the overflow. When a caller needs a human, the agent transfers the live call to your team or an external number, with the answer outcome reported back into the conversation. Think of it as a safety net around your staff, not a substitute for them.