Customers who come back on schedule—without chasing every due date yourself.

No. Deptly works inside the scheduling and route software you already run, and platforms like FieldRoutes, PestPac, and Jobber are exactly the kind of systems we scope during setup. The due list, job records, and customer notes stay where they are; Deptly reads them and acts on them within the rules you approve. If a system needs deeper integration work, we tell you during discovery, not after.

Messages go out in your business's name and voice, using scripts and tone you approve — the same way a good office manager would write them. If a customer asks directly, Deptly answers honestly. Most customers care that the visit gets scheduled and the question gets answered quickly; what they notice is that your company suddenly stopped missing things.

That conversation comes to you. Deptly can share the approved save offer if you've defined one, but it never negotiates, pressures, or invents a discount. You get the full context — service history, what triggered the cancellation, anything that went wrong — so if you want to make the call yourself, you're making it informed.

Surge weeks are the point. Deptly handles inquiries, reschedules, and confirmations in parallel — no busy signal, no triage fatigue by call forty — and applies the priority rules you set on a calm day: plan members first, existing customers before new ones, whatever your rules are. The rush stops being the season your rebooking discipline collapses.

Long intervals are where memory beats marketing. Deptly keeps the service record and reaches out when the pump-out window opens — before the homeowner has thought about it, and long before an alarm makes them call whoever answers first. Your records become the relationship, even on accounts you haven't touched in years.

It follows your policy: a polite request for an updated card, retries on your cadence, and a renewal notice that leads with the customer's service history instead of an invoice. Disputed charges and anything that turns into a complaint escalate to you. The goal is that plans stop dying of quiet billing failures nobody noticed.

Neither do we. Deptly follows an inspection finding with the technician's own report and photos, answers routine questions, and checks back on the cadence you approve — then records the yes, the no, or the 'not this year' and stops. No manufactured urgency, no scripts you didn't approve. A no is a closed loop, not a failure.

Intake and triage are. Deptly answers in parallel, sorts maintenance-agreement customers from new callers, applies your priority rules, and books against real technician windows while keeping everyone informed about where they stand. What's wrong with the unit stays your technician's call, and anything that sounds like a safety issue follows your emergency protocol straight to a person.

Yes. Reschedule requests, rebooking replies, new inquiries, and routine plan questions get handled whenever they arrive, so the Sunday-night 'can we move Tuesday's visit' text doesn't wait until someone is back at a desk. Anything urgent or safety-related follows the escalation path you define.

Yes. A cancellation opens a slot, and Deptly checks who nearby is due, waitlisted, or waiting on a missed-visit recovery — then offers the window before the route runs. Route decisions outside your standing rules, like anything that bumps another customer, come to you first.

Pricing is scoped by what Deptly carries: how many workflows, how much volume, which systems, and how much oversight you want. Most recurring service businesses start with a single workflow pilot — usually due-date rebooking or missed-visit recovery, because the value shows up in numbers you already track. The pricing page explains what determines cost, and the diagnostic gives you a scoped starting recommendation.