Deptly

What Deptly handles

Book, Dispatch & Protect Capacity

Turn interest into executable capacity without creating calendar chaos.

Sound familiar?

Your best installer texts at 6:40 AM that he's out sick. You're in the driveway rebuilding the whole day from your phone — calling customers, shuffling windows, trying to remember who said they were flexible — before you've left for your own first job.

See the Complete Workflow

What does "Book, Dispatch & Protect Capacity" cover?

Deptly turns booked interest into work your team can actually execute. It schedules jobs and appointments against real capacity, matches the right provider or crew, sends reminders and prep instructions, collects deposits where your policy requires, refills cancellations from the waitlist, and repairs the schedule when someone calls out. Anything outside your approved rules comes to you first, and every change is written back to the scheduling tools you already have.

What is really happening

A full calendar and an executable calendar are not the same thing. Booking is never one decision — it's a chain: does the time actually work, is the right person assigned, is the deposit collected, does the customer know what to prepare, and what happens when any link moves. Most scheduling tools hold the appointment. Nobody owns the chain around it.

So the loops stay open. A cancellation opens a slot and the waitlist never gets worked, because everyone is mid-job. Reminders go out when someone remembers. A call-out means the day gets rebuilt by hand, because the matching rules — who can do what, who's near where, which customer needs which person — live in your head and nowhere else. That isn't disorganization. It's an owner-dependent workflow doing exactly what it grew up doing.

Deptly takes ownership of the chain. It books against real availability, matches provider or crew fit by rules you approve, collects the deposit, sends the reminders, refills cancellations from the waitlist, and proposes the repair when a call-out hits. Anything outside your rules is a question, not a guess — and every change lands in your schedule of record, so the loop closes where your team can see it.

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.

  • Scheduling
  • Provider or crew fit
  • Reminders
  • Deposits
  • Routes
  • Waitlists
  • Cancellations
  • Call-outs

  1. Trigger

    A booking needs to happen

    An approved estimate, a qualified new inquiry, or a cancellation that just opened a slot — anything that should become time on the calendar.

  2. Action

    Check real capacity first

    Deptly reads your live schedule before offering anything: open windows, provider and crew availability, drive time between stops, and how the job fits the day's route.

  3. Action

    Match the right provider or crew

    Assignment follows rules you approve — skills, certifications, territory, customer history, and who this customer has worked with before. Fit is checked before the time is offered, not after.

  4. Communication

    Offer times, confirm, collect the deposit

    The customer gets two or three workable options, a confirmation once they choose, the deposit request where your policy requires one, and reminders with prep or access instructions scheduled from that moment.

  5. System

    Write it to the schedule of record

    The job lands in your scheduling platform with the assignment, notes, address, and access details — one source of truth your team already checks, not a separate calendar to reconcile.

  6. Approval

    Ask before anything outside your rules

    An overtime slot, a deposit waiver, squeezing one more job onto a full route — exceptions come to you as a clear yes-or-no with context, never acted on quietly.

  7. Escalation

    Escalate what genuinely needs you

    A call-out with no eligible replacement, a safety concern, or a schedule conflict with no clean fix gets escalated with the options laid out — Deptly proposes a repair, you make the call.

  8. Closure

    Verified closure

    The slot is booked or refilled, the customer is confirmed, the deposit is on file, and the assignment is visible to your team. Cancellations trigger waitlist outreach, and your weekly brief shows what was booked, refilled, and escalated.

What this looks like in your industry

Same loop, native vocabulary. Three examples of where this responsibility shows up.

Home services & emergency trades

A tech calls out at 6:40 AM. Deptly checks which of his jobs the remaining techs are certified for, reshuffles the arrival windows, moves the non-urgent maintenance visit to Thursday's route, and updates every homeowner — a repair plan is waiting for your approval before the first truck rolls.

Deptly for home services & emergency trades

Medical spas & advanced aesthetics

A client cancels a 90-minute laser session the night before. Deptly works the waitlist for clients already cleared for that provider and treatment, refills the slot by morning, applies your cancellation policy, and updates the provider's book — the room never sits empty.

Deptly for medical spas & advanced aesthetics

Moving & junk removal

A long-distance move books in. Deptly confirms the deposit, checks truck and crew availability against every existing move, blocks the load and delivery windows, and sends the customer a readiness checklist — so move day isn't the first time anyone checks the details.

Deptly for moving & junk removal

What 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.

  • Offering appointment times against real availability, drive time, and route fit
  • Matching jobs to the provider, tech, or crew your rules say fits
  • Sending confirmations, reminders, and prep or access instructions
  • Collecting deposits and booking fees where your policy requires them
  • Working the waitlist to refill cancellations and no-shows
  • Proposing a schedule repair when a call-out or delay hits the day
  • Writing every change back to your scheduling platform as the source of truth

Deptly asks first

Anything judgment-shaped waits for your okay.

  • Booking anything outside approved hours, territory, or capacity limits
  • Waiving or reducing a required deposit or cancellation fee
  • Moving a confirmed customer to make room for another job
  • Committing overtime, a subcontractor, or an extra crew
  • Any customer-requested exception your rules don't already cover

Always human

The decisions that stay yours, always.

  • Final say on who is hired, staffed, or trusted with a job
  • Judging whether a job is safe, in scope, or worth taking
  • Clinical, legal, and licensing decisions about who may perform the work
  • Pricing calls and trade-offs between customers when capacity runs short
  • The work itself — what happens on site stays with your team

The full rulebook — approvals, escalation, and audit history — lives on trust and control.

Systems and channels involved

  • your scheduling platform (Jobber, Housecall Pro, Mindbody, or similar)
  • your calendar (Google Calendar, Outlook, or similar)
  • your phone and text line
  • email
  • your CRM or customer records, wherever they live
  • route planning or dispatch boards your team already uses
  • your payment processor for deposits (Square, Stripe, or similar)

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 empty slots after late cancellations, because the waitlist gets worked immediately instead of when someone finds a minute
  • Fewer no-shows when reminders, prep instructions, and deposit requests actually go out on schedule, every time
  • Call-out mornings stop starting with you rebuilding the day by hand — a repair plan is waiting for your yes
  • A calendar your team can trust: assignments, access details, and every change live in the schedule of record, not in your head

See the loop close

Every proof item on this site is labeled for exactly what it is.

Workflow Demonstration

A 2:00 cancellation, refilled before morning

  1. Client

    Hi, I'm so sorry — I have to cancel my 2:00 tomorrow with Dana. Family thing came up.

    8:12 PM

  2. Deptly

    Cancellation logged and the 2:00 slot with Dana opened. Working the waitlist: three clients are cleared for this provider and treatment. Reaching out in priority order.

    8:13 PM

  3. Deptly

    First waitlist client confirmed for 2:00 tomorrow. Deposit on file per policy. Book updated, reminder and prep instructions sent.

    8:41 PM

  4. Deptly

    Needs your OK

    The client who cancelled asked to rebook Saturday — outside Dana's hours. Offer Friday 4:30 instead, or open Saturday this once? Your rule says weekends need your approval.

    8:44 PM

  5. D

    Owner brief

    Friday

    inbox

    This week: 3 cancellations, all 3 refilled from the waitlist. 1 exception sent for approval — you kept the weekend closed and the client took Friday 4:30. No booked hours lost.

The responsibilities around this one

Each loop hands off cleanly to the next — start with one, add others when you're ready.

Keep exploring

Questions owners ask

It reads your live schedule and the capacity rules you set — working hours, territories, provider and crew availability, drive time between stops. It never offers a time you haven't made bookable, and if something is ambiguous it asks instead of guessing.

Deptly logs the cancellation, applies your cancellation policy, and immediately works the waitlist for customers who fit that slot, provider, and service. If the slot can't be refilled, you see that plainly — nothing gets quietly written off, and the customer who cancelled gets a rebooking path.

You approve the matching rules up front: skills, certifications, licensing, territory, customer history, and personal preferences like which customers ask for which person. Deptly assigns within those rules, and anything the rules don't cover comes to you as a question.

No — your scheduling platform stays the single source of truth. Deptly checks live availability before offering any time and writes every booking, change, and cancellation back to that system, so what your team sees is always what's real.

Yes, where your policy requires one — the deposit request goes out with the confirmation, through the payment processor you already use. Waiving or reducing a deposit is never done freely; that always comes to you first.

Deptly builds a repair plan: which jobs an eligible teammate can cover, which windows to shift, which visits to move to a later route, and what to tell each customer. You approve the plan before it moves. If there's no clean fix, it escalates with the options laid out rather than improvising.

No. Deptly works inside the tools you already have — Jobber, Housecall Pro, Mindbody, Google Calendar, or similar. If your schedule lives somewhere unusual, that's exactly what the first conversation is for.

Of course. Anything your team books by hand is respected as the source of truth. Deptly adds the follow-through around it — the reminders, the deposit, the prep instructions, the refill when it cancels — it doesn't take your phone away.

That's an exception, so it comes to you: the request, the context, and a recommendation, as a simple yes or no. Your hours and your limits hold unless you personally decide to bend them.

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.

Find My Best Starting PointTalk Through My Business