Booking funnel, mapped before it ships
For 2-person service shops

The booking-form visitor who walks is the conversion you can't afford— a 24/7 AI agent is what qualifies + escalates the thread on the visitor's clock.

On a typical 2-person service shop, a meaningful share of booking-funnel visitors open the quote or booking form and walk before any human reply — the form is open across the abandoned-tab count by the time the team sees it. Layer the after-hours booking-intent (calendar-fit, scoping, price-floor) on top, and the worked-loss arithmetic rolls up to ~€4,500/month on a 2-person service shop — the same envelope the /slow-reply, /missed-questions, /after-hours, and /cart-recovery pillars each describe from a different angle. Skip the qualifying + escalation pass and the thread waits hours / until morning; ship the 24/7 agent and the qualified thread reaches the owner with the full transcript by 9 am.

Source note · Oldroyd / Lead Response Management (the 5-minute response-window study) insidesales.com.

Abandonment share
~25-pp conversion gap
Built around
A custom map
Mode
24/7 AI, qualified handoff
~€4,500/month booking-funnel worked loss
300 enquiries · €60 lead value

Leak on the line

~€4,500/month

of service-avoidable loss sitting inside the booking funnel on a 2-person service shop — a meaningful share of booking-form visitors walk before any human reply, and a meaningful share of those after-hours threads carry purchase intent (calendar-fit, scoping, price-floor). The qualifying + escalation pass lands the full transcript + qualifying summary in the owner's inbox by 9 am; the thread the visitor expected a reply on at 11 pm the night before is the conversion that walked without it. Recoverable, once the mapped journey + 24/7 AI agent is running against your operation instead of a generic template. The assumptions are spelled out below; a critic can rerun the math against your own enquiry volume and lead value.

Abandonment share
~25-pp gap
Qualifying → escalated
by 9 am
If unaddressed
€4.5K/mo

Worked example, not a guarantee. The arithmetic and the underlying assumptions live one section below.

The four findings the brief surfaces

Four dials on the booking funnel — each one buys back a slice the form was losing.

Booking-funnel loss on a 2-person service shop is not a single problem. It is four leaks at once — the abandonment share itself, the after-hours booking intent that compounds on top of it, the qualifying + escalation pass the 24/7 agent runs, and the worked dollar-loss the same pattern rolls up to. The map finds them; the build closes them, with the same 24/7 AI agent the /slow-reply, /missed-questions, /after-hours, and /cart-recovery pillars each describe from a different angle.

01
Booking-funnel abandonment share — the visitor who opens the quote / booking form and walks before any human reply
A meaningful share of booking-funnel visitors land on a 2-person service shop's quote or booking form and walk before any human reply — the form is open across the abandoned-tab count by the time the team sees it. The same ~25-percentage-point conversion gap that the /slow-reply, /after-hours, and /process-breakdown pillars each describe from a different angle is exactly what produces the ~€4,500/month worked-loss envelope the booking-recovery map sizes. The map decides whether the booking-form abandoner is the dominant leak on a given shop or a smaller slice; the build layers the 24/7 agent on top of the form so the same visitor is qualified on their own clock, not left to walk.
02
After-hours booking intent — the quote-thread that arrives at 11 pm carrying purchase intent, not browsing
A meaningful share of the threads that arrive via the booking form carry purchase intent — calendar-fit questions, scoping clarifications, a price-floor check the visitor wants answered before committing a card. The after-hours booking-intent thread is the same one the /after-hours pillar catches on the visitor's clock, but the booking funnel narrows the surface: by the time the visitor opens the form, they have already self-qualified as a buyer, and the thread that waits hours / until morning is the conversion that walked. The booking-funnel map sizes the share against the helpdesk + CRM the team already keeps; the build installs the 24/7 agent that catches the thread on arrival.
03
Qualifying + escalation — the agent qualifies on the visitor’s clock and routes only the qualified thread to the owner with the full transcript
The booking-recovery bot doesn't book blind. It qualifies on the visitor's clock — budget, scope, timing — and routes only the qualified thread to the owner with the full transcript. The escalation path is the same one the /process-breakdown pillar wires to the silent-drop map: a sorted queue in the owner's inbox instead of a flat history of bookings nobody owns, with the after-hours thread pinned to the top because that's what the visitor expected a reply on at 11 pm the night before. The bot layers on the helpdesk / CRM the team already pays for; the morning handoff lands in the systems the team uses, not a parallel inbox.
04
Worked dollar-loss — the ~€4,500/month the booking-funnel map recovers before the bot ships
Take a 2-person service shop with 300 service enquiries a month, a 25-percentage-point conversion gap between threads answered inside five minutes and threads that wait hours / until morning, and a €60 average lead value. Apply the Oldroyd / Lead Response Management floor that a reply inside five minutes qualifies at a radically higher rate than a reply hours later. The lost threads the booking funnel leaks — 300 × 25% — is 75 lost conversations/month, × €60 average lead value = €4,500/month. The arithmetic is spelled out one section below; substitute your own enquiries/mo and lead value to rerun against your operation.

The arithmetic, with assumptions spelled out

How a 2-person service shop arrives at the ~€4,500/month booking-funnel leak.

Take a 2-person service shop with 300 service enquiries a month and a €60 average lead value. Apply the booking-funnel abandonment share — the visitor who opens the form and walks before any human reply — and the late-night booking intent on top (a meaningful share of those threads carry calendar-fit / scoping / price-floor intent, not browsing). Apply the Oldroyd / Lead Response Management finding that a reply inside five minutes qualifies at a radically higher rate than a reply hours later — concretely, a 25-percentage-point conversion gap between the five-minute bucket and the four-hour / next-morning bucket. The lost threads the booking funnel leaks — 300 × 25% — is 75 lost conversations/month, × €60 average lead value = €4,500/month sitting inside the form-side leak a mapped journey + 24/7 AI agent closes. Real shops skew higher once the enquiry volume grows or the lead value climbs; the rounded €4,500/month figure on the hero sits inside the same envelope across most 1- and 2-person service SMBs.

Source · Oldroyd / Lead Response Management (the 5-minute response-window study) insidesales.com. Worked example, not a guarantee — substitute your own enquiries/mo and lead value to rerun.

Sample inputs

Monthly enquiries
300
Avg lead value
€60
Abandonment share
~25-pp gap
Reply floor
< 5 min

Worked loss

300 × 25% × €60 ≈ €4,500/month

Picking up where the booking-funnel map leaves off

The 24/7 agent catches a different leak on every pillar — but the qualifying + escalation handoff is shared.

The four findings on this page are the same four the 24/7 agent covers on a real engagement — and the same four the mapping call decides between during week one. The sibling pillar on slow reply walks the same five-minute / after-hours track for reply times; the parallel on missed questions walks the FAQ-coverage version of the same leak; the form-side version this pillar covers is the visitor who has self-qualified as a buyer and walks before any human reply — the after-hours time-window version of the same leak lives on after-hours; the SMS-side version lives on cart recovery; how this stacks up against off-the-shelf tools lives on compare. The engagement shape on the pricing page covers how the build runs once the map is in hand — and the process breakdown pillar covers the four-finding map that decides which leak to tackle first.

FAQ

The questions a 2-person shop asks once they've read the four findings.

Quick answers about the booking-funnel abandonment share, the after-hours booking intent, the ~€4,500/month worked loss, and how the 24/7 AI agent + qualifying + escalation handoff actually work. If yours isn't here, send it directly to hatchloom-5@polsia.app.

One mapping call away

Tell us how your booking funnel closes today. The booking-recovery map comes from there.

No sales deck, no demo under NDA. Send us the shape of your operation, the helpdesk and CRM you already pay for, and a window for a 30-minute call. We'll tell you in plain English how much of the ~€4,500/month booking-funnel leak the 24/7 agent is positioned to close on a 2-person service shop — and whether the engagement fits. See how the engagement runs on the landing page.

Start a mapping call

Replies in one business day, usually faster.

Want more revenue-recovery tips?

Get more revenue-recovery tips, one short email at a time.

A short email when we ship a new teardown, a new lever, or a new worked example. No marketing drip, no sales sequence. Unsubscribe in one click.

Tips, one short email at a time

Revenue-recovery tips, monthly
A short, occasional email when we ship a new cart-recovery teardown, lever, or worked example. No spam, no retargeting.