Same tone. Your own page.
A small chat launcher sits in the corner of your own site — answers the FAQ, captures the lead, and hands the booking off to the calendar line. The same tone as the text-back, the same receipt on your phone, the same <30s handoff when the visitor asks for a person.
Setup: $1k – $3k · Retainer: $300 – $1k / mo
Three jobs on the page where they turned up.
Holdfast web chat is the widget your visitor meets the moment they need an answer — and the line that catches the lead before they close the tab. Three jobs the line does before the visitor leaves the page.
- FAQ
Answers the FAQ in your voice.
The widget answers the questions the page already answers — hours, pricing, service area — in the same service-truck tone the storefront uses, so the visitor never leaves the site to find out the basics.
- Lead capture
Captures the lead before they bounce.
A short intake — name, address, job-type, the channel they prefer — runs inside the thread before the visitor can close the tab. No separate form, no “we'll call back” loop.
- Booking handoff
Hands the booking off to the calendar line.
When the visitor wants to book, the chat hands off to the AI booking line in the same thread — the calendar holds the time, the receipt lands in the same conversation they're already reading.
Four beats between the page and the slot.
The launcher opens on tap; the widget greets the visitor in your tone; the chat answers the question or captures the lead; the booking line takes over or the on-call line pokes in. Four beats the widget walks on every page the visitor touched.
Visitor taps the launcher — chat greets, asks what they're trying to find out.
tone-faithful · 2s
“Saturdays are emergency-only — but we run Thu mornings if Thu works.”
FAQ answered
Visitor asks to book — chat hands off to the calendar line, in the same thread.
booking · same receipt
“Actually I think this is an emergency.” → Holdfast pages Marrs HVAC.
on-call · <30s
Same four beats walk on every page the visitor touched. Quoted against the visitors you'd catch, not the hours the widget sits open.
The thread on the corner of the page.
Short, on-brand, no chatbot cadence. The same tone as the text-back — service-truck English, not a “type /help” menu. Question first, answer second, the next opening third.
Do you do quarterly tune-ups?
Yep — Thu 9a or Thu 1p on the books. Name + address and we'll hold one.
Marrs HVAC — 1318 Oak. Thu 1p.
Locked in. Thu 1p — we'll send the address the day before.
Mock-up of the live thread in the corner of the page. The owner gets the same summary on their phone when the slot's held.
A real person takes over the room.
The visitor types “can I talk to a person” or flags a job-type the intake says is custom — specialty repair, multi-day build, anything over your standing-cap — and the chat steps sideways to the on-call line. The chat never pretends to be human; the handoff takes under thirty seconds; the thread stays warm the whole way through.
Can I talk to a person?
One sec — Holdfast is paging Marrs HVAC now. Stay where you are.
Custom-quote triggers fire the same way — flagged on intake, the chat steps out, the owner takes the lead on their own schedule.
The receipt before the visitor closes.
Every web-chat session ends up in the owner's inbox as a one-line receipt — the name, the address, the job-type, the beat the chat walked. FAQ lead, captured lead, confirmed booking, or escalation all land in the same place, on the same phone. No “did this one come in?” loop on a Saturday morning.
Marrs HVAC — 1318 Oak St · pricing on Sun emergency call-out
via web-chat · 9s to answer
Rojas Property — 24 Elm Way · flat-tire swap · handed to booking line
via web-chat · 14s to capture
Singh Family — 55 Lake Dr · after-hours leak · on-call paged
via web-chat · <30s handoff
One schedule. Every chat, every reply, every receipt.
Mock-up of the owner dashboard for a typical Saturday morning of web-chat visitors.
The questions the intake call asks.
A short list, in plain English — the ones we hear on every walkthrough, before the retainer gets quoted.
Does the web chat ever pretend to be human?
No. The widget makes the visitor's correspondent plain from the first message — the intro line says so, the response tone is brief, and a “talk to a person” button sits on every screen. The handoff to a human is under thirty seconds; the visitor never has to guess which one they're typing to.
What if the visitor wants a custom quote?
The chat asks the qualifying questions first, and any job-type flagged “custom” on the intake — specialty repairs, multi-day builds, anything over your standing-cap — escalates to a human before the reply goes out. The visitor still gets a within-thirty-second acknowledgement; the quote itself comes from the owner on their own schedule.
Can it route to a person if the visitor asks?
Yes. A “can I talk to a person” triggers a handoff to the on-call line — the same one the text-back after-hours pings escalate to. The chat never pretends to be human, the handoff takes under thirty seconds, and the visitor stays in the same thread the whole time.
How does it share tone with the text-back line?
One intake call wires both lines from the same house rules — the same service-truck English, the same qualifying questions, the same “route to a human” triggers. The widget never sounds like a separate chatbot; it sounds like the same front desk the visitor would've reached on the phone.
Bring the page. We'll quote it against the visitors you'd catch.
Twenty-minute walkthrough. We'll bring the widget mock-up, the FAQ / lead- capture / booking-handoff pipeline, the on-call handshake, and quote the setup and retainer against the visitors you'd catch on a Saturday morning.