Missed call recovery
A two-truck plumbing company. Both crews are mid-job — one owner is under a house on a repipe — when a homeowner with a leaking water heater calls the main line. Nobody can pick up. This is the moment most service businesses quietly lose work, because the caller's next move is usually the next company on the list.
What does this demonstration show?
This demonstration walks through a missed call at a two-truck plumbing company, step by step. Deptly texts the caller back within minutes, recognizes an urgent water heater leak, books a same-day visit inside the company's real availability, and confirms it in writing. The owner gets a short heads-up, not another task. It is a labeled workflow demonstration, not a customer story — the standard workflow shown truthfully.
The workflow, step by step
Real product behavior with example names and details. The notes beside each step explain what is happening — including where Deptly asks instead of acting.
2:14 PM
Homeowner
Call to the main business line rings through to voicemail. No message left.
Deptly watches the phone line the business already uses. A missed call from an unknown number during working hours is a trigger it acts on — a caller who leaves no voicemail is usually already dialing the next company.
2 minutes later
Deptly
Sorry we missed your call — our crews are with customers right now. Is this about a repair or a quote? Happy to help by text, or we can call you right back.
A prompt text often reaches the caller before they commit to another company. The message is sent from the business's own number, in wording the owner approved during setup.
3 minutes later
Homeowner
Our water heater is leaking into the garage. How soon can someone come out?
Deptly recognizes urgency language. Active water leaks are on this owner's urgent list, so the conversation is prioritized and handled on the emergency path rather than queued as a routine quote request.
2:20 PM
Deptly
That sounds urgent — we can have a technician out today between 4 and 6 PM. Can I grab your address to lock that in?
Deptly checks the schedule the company already keeps and offers a real opening. It never invents availability — it books only within windows the owner has marked bookable, and same-day emergency slots are one of this owner's approved routine actions.
2:23 PM
Deptly
Heads up: new urgent job — water heater leaking into a garage, booked today 4 to 6 PM. Address and full thread are on the calendar entry.
The owner gets a short heads-up, not a task. Nothing needed approval here because the booking followed pre-approved rules; anything outside those rules — a discount request, an after-hours callout — would have come to the owner as a question instead.
2:31 PM
Homeowner
Address sent. Yes please, 4 to 6 works — I'll be home.
The caller confirms. If the reply had been something unexpected — a complaint, a warranty question, a request to speak to the owner — Deptly would route it to a human with the thread attached rather than improvise.
2:33 PM
Deptly
You're booked for today between 4 and 6 PM. You'll get a text when the technician is on the way.
The confirmation goes out in writing and the job is created in the scheduling tool the company already uses — the crew sees it the same way they see every other job.
That evening
DinboxOwner brief
The 2:14 PM missed call was recovered by text and booked as a same-day water heater job. Full conversation available if you want to review it.
Every recovered call appears in the owner's brief with the thread attached. Closure means booked, confirmed, and on the calendar — not just answered.
What the owner brief says
You don't watch this workflow run. It rolls up into your weekly brief alongside everything else that was handled — what closed on its own, and the few things waiting on you.
A full sample brief lives on the proof and examples page.
Your weekly brief
deptly · weekly summary
- Tuesday 2:14 PM missed call: texted back within minutes, urgent water heater leak, booked same day for the 4 to 6 PM window.
- The homeowner confirmed the appointment and received an on-the-way text before the technician arrived.
- No approvals were needed — same-day emergency booking within open windows is in your approved routines.
- One other missed call this week was a supplier calling about a delivery; it was passed to your inbox instead of the booking flow.
Example — how this workflow appears in your weekly brief
Verified closure
The missed call became a booked, confirmed same-day appointment on the company's own calendar — closure verified by the written confirmation and the calendar entry, not assumed from a sent text.
Closure means the loop is confirmed done — not that a message was merely sent. That standard, and everything behind it, is explained on trust and control.
The boundary this workflow ran inside
The steps above where Deptly asked instead of acting are the point, not a limitation. Every workflow runs within rules you approve — anything outside them waits for you.
Deptly handles
- Routine steps like the ones above — replies, follow-ups, reminders, status updates, scheduling holds
- Logging every action so the weekly brief writes itself
- Chasing the open loop until it verifiably closes
Deptly asks first
- Anything that touches price, scope, or an exception to your rules
- Messages that fall outside the wording you approved
- Situations the rules don't cover — flagged to you, not guessed at
Always human
- Pricing, hiring, and how the work gets done
- Sensitive customer conversations
- Final say on anything Deptly flags
How those rules get set up in your first weeks is on how it works.
See this loop in context
- The capability behind this demonstration: Respond & Capture Every Opportunity
- Deptly for home services & emergency trades
- Deptly for landscaping, tree & heavy property services
- Deptly for auto services, mechanics & specialty surface care
- Deptly for cleaning, restoration & exterior maintenance
- Deptly for moving, junk removal, hauling & estate cleanout
- See everything Deptly handles
- All proof and examples
Questions owners ask
Yes — the workflow runs on the business line you already have. Missed-call detection is set up through your phone provider or a lightweight forwarding rule, and setup confirms exactly what your system supports before anything goes live. Customers only ever see your number.
The conversation isn't a rigid script. Routine replies — booking questions, address details, timing changes — are handled within your rules. Anything unexpected, like a complaint, a warranty claim, or a request to speak with you, is routed to you or your staff with the full thread attached. Deptly never bluffs its way through a question it can't answer.
You decide. Many owners pre-approve routine bookings inside windows they've marked available, so those run without interruption. Discounts, emergency pricing, complaints, and anything touching money always go to a human — that boundary is set during setup and you can tighten or loosen it at any time.
Yes. Tone and wording are set with you during setup, and you can review drafts until you're comfortable. Most owners start with every message reviewed and move to approved routine wording once they've seen it in action.
After-hours rules are yours to define. Some owners have Deptly capture the details and book the first morning slot; others define what counts as urgent and have those calls escalated to a person immediately. Nothing is treated as an emergency unless it matches your definition.
It's a labeled workflow demonstration — a truthful walkthrough of the standard missed-call workflow in a realistic plumbing scenario. We show demonstrations instead of invented testimonials, and we label every piece of proof on this site for exactly what it is.
Your workflows next
What would this look like in your business?
Answer a few questions about where work waits in your week and get an honest read on which loop Deptly should close first.