What Deptly handles
Keep Customers Informed & Work Moving
Reduce customer chasing and keep waiting states owned.
Sound familiar?
It's 8:40 on a Tuesday night and you're returning the day's third 'just checking in' call. The Hendersons' remodel is actually on schedule — but they haven't heard anything since the deposit cleared, so to them, a week of silence sounds like a problem.
What does "Keep Customers Informed & Work Moving" cover?
Deptly answers routine customer questions, sends status and milestone updates before customers have to ask, chases missing documents, prepares customers for appointments, and flags delays early — using the phone, text, and email channels you already have, within rules you approve. Complaints and judgment calls come straight to you with full context. Customers stop chasing you for updates because every waiting state has an owner.
What is really happening
Your customers aren't difficult. They're waiting — and waiting without information is uncomfortable, especially after they've paid a deposit or handed over their car, their pet, or their case. Every 'any update?' call is a customer trying to close a loop your business opened.
The updates exist. You know the parts arrived, the adjuster responded, the crew is set for Thursday. But that knowledge lives in your head and your inbox, and sending it out is one more task competing with the actual work. So updates go out when something goes wrong instead of before customers start to wonder — which quietly trains customers to chase.
This is an owner-dependent workflow, not a communication failure. When status updates, prep instructions, and document requests only happen when you personally remember to send them, the business communicates exactly as well as your busiest day allows. The fix isn't trying harder — it's making waiting states owned by something other than your memory.
The complete workflow, trigger to closure
Not a feature that fires once — a loop that runs every time, with approvals where judgment is needed and verified closure at the end.
- Routine customer questions and FAQs
- Status updates at every waiting state
- Appointment and job preparation instructions
- Document requests, reminders, and tracking
- Milestone updates as work progresses
- Delay notices before customers have to ask
- Complaint intake and immediate escalation
- Multi-party coordination between customer, crew, and third parties
Trigger
A waiting state opens
A deposit clears, a car is dropped off, or a form goes out for signature — and the next thing the customer will see is days away. Deptly registers who is waiting, on what, and when they'd start to wonder.
Action
Deptly maps what needs to move
It checks the job record for the milestones ahead, the documents still missing, and the preparation the customer needs — then builds the update and request sequence from your approved library.
Communication
The customer hears what happens next
A confirmation goes out with the timeline, prep instructions, and a specific ask for anything missing — a signed authorization, a gate code, an insurance claim number — in your business's voice.
System
Everything lands on the record
Replies, documents, and confirmations are logged against the job in your platform, and pending reminders reschedule themselves when something arrives or a date changes.
Communication
Milestones and delays go out before the call comes in
As the work moves — parts arrived, drying complete, draft ready — the customer gets a short update. When a supplier pushes a date, the delay notice is drafted the same hour.
Approval
Sensitive messages wait for you
A delay past your threshold, anything touching price or scope, or a reply to a tense customer is queued with full context for your one-tap approval before it sends.
Escalation
Complaints reach a human immediately
An unhappy reply skips the routine flow entirely: you're flagged with the full history, routine messages to that customer pause, and the resolution stays yours.
Closure
The loop is verified closed
The customer has confirmed the current plan, documents are on file, and your weekly brief shows what went out, what came back, and the handful of items that actually needed you.
What this looks like in your industry
Same loop, native vocabulary. Three examples of where this responsibility shows up.
Restoration & insurance claims
A water-damage job has a homeowner who wants their house back, an adjuster who wants documentation, and a mitigation crew that needs access. Deptly keeps the homeowner updated at each drying milestone, sends the adjuster routine documentation, and confirms crew access windows — so the file moves without you playing switchboard.
Deptly for restoration & insurance claimsCollision & auto repair
A customer whose car is in the shop calls every day it goes silent. Deptly sends teardown, parts, paint, and reassembly updates as the repair moves, flags a backordered part before the promised date slips, and confirms pickup once the quality check is done.
Deptly for collision & auto repairEstate planning law
An estate plan stalls when clients sit on questionnaires and unsigned documents. Deptly sends the questionnaire, reminds politely until it comes back, updates clients between drafting milestones, and books the signing appointment when documents are ready — so matters don't quietly age in a drawer.
Deptly for estate planning lawWhat Deptly handles, asks about, and never decides
Every workflow above runs inside this boundary. You set the rules; anything outside them waits for you.
Deptly handles
Routine work done within the rules you approve.
- Answering routine customer questions from your approved answer library
- Sending booking confirmations and preparation instructions before appointments
- Status and milestone updates at the points you define
- Requesting, reminding on, and logging missing documents, photos, and forms
- Routine delay notices within the threshold you set
- Coordinating routine status between customers, crew, and third parties
- Logging every message on the job or client record
Deptly asks first
Anything judgment-shaped waits for your okay.
- Delay notices beyond the threshold you set
- Anything that changes price or scope
- Responses to a frustrated or unhappy customer
- New answers to questions outside the approved library
- Non-routine messages to adjusters, attorneys, or other third parties
Always human
The decisions that stay yours, always.
- Resolving complaints and deciding on goodwill, discounts, or refunds
- Judging the quality of the work itself
- Legal, clinical, or safety guidance to a customer
- Commitments that change what was sold or what it costs
- The hard conversations — relationship repair stays yours
The full rulebook — approvals, escalation, and audit history — lives on trust and control.
Systems and channels involved
- Your phone, text threads, and voicemail
- Your business email inbox
- Your scheduling or job platform (Jobber, Housecall Pro, ServiceTitan, or similar)
- Your CRM or client records
- E-signature and document tools (DocuSign, shared folders, photo upload links, or similar)
- Google Business Profile and social messages
These are examples of where this work usually lives, not guaranteed integrations. Deptly works within the tools you already have — setup starts from what you actually use, as described on how it works.
What typically changes
No invented numbers — just the differences owners can reasonably expect when this loop stops depending on them.
- Fewer 'any update?' calls reaching you, because information goes out before customers wonder
- Evenings back that used to go to returning status calls and chasing paperwork
- Jobs stall less often on missing documents when requests and reminders don't depend on your memory
- Customers who feel informed while they wait complain less and stay warmer for the next visit
See the loop close
Every proof item on this site is labeled for exactly what it is.
A backordered vanity, handled before the customer had to ask
Supplier email
Heads up — the vanity for the Alvarez remodel is backordered. New ship date pushes install from Tuesday to Friday.
Mon 9:15 AM
Deptly
This delay moves a promised date, so it's past your auto-send threshold. Drafted a notice for the Alvarezes with the new Friday install and queued it for your approval.
Mon 9:18 AM
Owner
Needs your OKApproved. Offer them the first slot Friday morning.
Mon 10:02 AM
Deptly to customer
Hi Maria — quick update on your remodel. Your vanity ships later than planned, so install moves to Friday at 8 AM. Everything else stays on schedule. Reply 1 to confirm Friday or 2 to see other times.
Mon 10:04 AM
Customer
Friday works. Thanks for telling us before we had to chase you!
Mon 10:31 AM
- Dinbox
Owner brief
Friday brief
Alvarez remodel: supplier delay handled. Customer confirmed Friday 8 AM, crew schedule updated, no open questions on the job. One approval needed from you all week.
The responsibilities around this one
Each loop hands off cleanly to the next — start with one, add others when you're ready.
- Get Found & Build Trust
- Respond & Capture
- Book & Protect Capacity
- Follow Up & Close
- Get Paid & Back Office
- Bring Customers Back
- See What Needs Attention
Keep exploring
Questions owners ask
It reads the signals your business already produces — schedule changes, notes in your job platform, supplier emails, crew confirmations. Where a stage isn't recorded anywhere, Deptly asks the person who knows with a quick one-tap question instead of leaving the customer in the dark.
Messages go out in your business's name and voice, from your existing numbers and inboxes, using wording you approved. Deptly never pretends to be you personally, and when a customer needs you specifically, the message says so and you get the handoff with full context.
Complaints skip the routine flow entirely. Deptly acknowledges receipt, flags you immediately with the full history, and holds any scheduled routine messages to that customer until you've decided how to respond. Resolving the complaint — and any goodwill decision — stays with you.
Yes — missing documents are one of the most common waiting states. Deptly sends the request, reminds politely on a schedule you approve, logs what arrives on the right record, and tells you when something is genuinely stuck rather than just slow.
Only within thresholds you set. A routine 'running 30 minutes behind' can go out automatically if you've approved that pattern; a delay that moves a promised date waits for your sign-off. You decide where the line sits, and you can move it as trust builds.
It doesn't guess. The customer gets an honest 'let me check with the team' and a realistic timeframe, you get the question with context, and Deptly follows up to make sure the answer actually went back out. The loop closes either way.
Routine multi-party coordination is exactly the kind of work Deptly carries: sending documentation, confirming access windows, chasing responses so the file keeps moving. Negotiating with an adjuster or making commitments on your behalf is not — those stay human.
During onboarding, Deptly learns your typical jobs, the moments customers care about, and how you like to sound — then you review and approve the answer library and update points. After that, your involvement is approvals and the exceptions Deptly raises, not writing messages.
The opposite is the goal: updates only at moments that matter to the customer — booked, prepped, delayed, done, next step. No marketing drip inside an active job, and every message tells them something useful or asks for something specific. Customers can always reply and reach a human.
One responsibility at a time
Would this loop make the biggest difference first?
Answer a few questions about where work waits in your business and get an honest read on which responsibility Deptly should carry first.