Why deposits deserve a written policy
Most service businesses take deposits inconsistently. One dispatcher asks for money up front on a special-order part and another does not. A technician waives it for a friendly customer. The owner remembers the job where the customer vanished after the part arrived, and the next week everyone asks for deposits on everything, until a few customers balk and the habit fades again.
That inconsistency is the real problem. A deposit that some customers pay and others do not is hard to defend when someone disputes it, and it confuses the team about when to ask. A written policy fixes both: everyone applies the same rules, and the customer hears the same explanation every time.
As of September 2026, collecting a deposit is mechanically easy. A payment link by text takes seconds, and the record of what was paid and why is created automatically. The hard part is deciding when to ask, how much, what is refundable, and how to say it so the customer agrees before anything is charged. This guide walks through each of those decisions.
The platform referenced throughout is Run with Jarvis, and the case for keeping quotes, booking, payments and customer records in one system rather than stitched across tools is set out in all-in-one platform vs disconnected point tools. This is operational guidance, not legal advice; rules around deposits and refunds vary by location, and it is worth a conversation with an attorney before you finalize terms.
What a deposit actually protects
A deposit is insurance against a specific loss. Before deciding when to require one, name the losses you are insuring against.
Parts you cannot return. A special-order key, a module programmed to one vehicle, a custom-cut component, a part with a restocking fee. If the customer disappears after you order it, you own something you cannot use or sell.
A slot you held. When you block a technician's morning for a big job and the customer cancels the night before, the morning is gone. On busy weeks that slot could have gone to someone else.
A trip that went nowhere. After-hours dispatch costs a technician's evening and fuel. A customer who is not there when the truck arrives, or who changes their mind at the door, leaves you with the full cost and none of the revenue.
Work done ahead of payment. On larger jobs you may carry material and labor costs for days before invoicing. A partial payment up front narrows that exposure.
Notice what is not on the list: ordinary small jobs from repeat customers. The loss there is small and rare, and asking for money up front costs you bookings. A deposit policy is a set of targeted protections, not a blanket rule.
When to require one
Here is a practical way to decide, by situation. Treat it as a starting point and adjust to your trade and your history.
| Situation | Require a deposit? | Suggested size | Refund terms |
|---|---|---|---|
| Special-order or non-returnable parts | Yes | At least the part cost plus shipping | Refundable until the part is ordered; not after, if stated in advance |
| Large or multi-day job | Yes | A meaningful partial payment, balance on completion | Refundable with reasonable notice before materials or scheduling are committed |
| After-hours or emergency dispatch | Often | Roughly the trip and minimum service charge | Applied to the job; refundable if you cannot arrive as promised |
| First-time customer, expensive job | Often | Partial payment or parts cost | Same as the job type above |
| Repeat customer, routine job | Usually no | None | Not applicable |
| Small routine job, any customer | Usually no | None | Not applicable |
Special-order parts are the clearest case. If the part only works on this customer's vehicle or equipment, or the supplier charges to return it, take at least the part cost before ordering. This is the deposit customers understand most easily, because the logic is visible: we are buying something just for you.
Large jobs justify a partial payment because the exposure is large. The exact share is a business decision, but it should be enough to cover the materials and the scheduling commitment, with the balance due on completion. Tie any further payments to visible milestones so the customer always knows what they are paying for.
After-hours dispatch is a judgment call. Many businesses take the trip and minimum charge up front for night calls, because the cost of a wasted trip at 11 p.m. is high and the customer is usually motivated. If you do, the deposit should be applied to the final bill, not added on top of it. How to price the after-hours premium itself is a separate question, covered in the guide on after-hours calls.
First-time customers booking expensive work carry more risk than repeat customers, simply because you have no history with them. A modest deposit on large first jobs is reasonable. On small first jobs it usually is not, because it discourages exactly the customers you are trying to win.
How much to ask for
The most defensible deposit is one you can explain in a single sentence, tied to a real cost.
Tie it to the cost you are protecting. For a special-order part, the deposit is the part and shipping. For after-hours dispatch, it is the trip and minimum. For a large job, it is the materials plus the value of the committed schedule. When the customer asks why the number is what it is, the answer should be obvious.
Avoid arbitrary round percentages without a reason. A percentage is easy to state but hard to justify on a job where the part is most of the cost, or where no parts are involved at all. If you use a percentage for large jobs, pick one you can explain.
Keep it proportionate. A deposit that is most of the job price starts to feel like full prepayment, which some customers resist and which changes the refund conversation. Unless the parts genuinely are most of the cost, a partial payment is easier to accept.
Quote the deposit and the balance together. The customer should hear the total, the deposit, and the balance in one breath: "The total is four hundred and eighty dollars. We take one hundred and ninety up front for the part, and the rest when the job is done."
Refund rules that hold up
Most deposit disputes are really refund disputes. The customer paid, something changed, and the two sides disagree about whether the money comes back. Clear terms, stated before payment, prevent most of them.
Refund what you have not spent. If the customer cancels before you order the part or commit the schedule, returning the deposit is fair and usually the right business decision. Keeping money for work you have not done invites a dispute you may lose and a review you will not like.
Keep what you have genuinely spent, if you said so. Once a non-returnable part is ordered, a non-refundable deposit covering it is reasonable, provided the customer was told that clearly before paying. The key word is before.
Set a notice window for scheduling. For large jobs, say how much notice a cancellation needs for a full refund. The logic parallels a cancellation policy, and the two should be consistent; the fuller framework is in the cancellation and reschedule policy guide.
Refund promptly when you are the one who changes. If you cannot perform, the part is back-ordered indefinitely, or you cannot arrive when promised, return the deposit quickly or offer a clear choice. Holding a customer's money while you are the one who failed is the fastest route to a dispute.
Put the terms in writing. The quote text, the payment link description, or the confirmation message should restate the amount, what it covers, and when it is refundable. A term that was only spoken is hard to prove later.
Rules on deposits, refunds and consumer contracts differ by state and locality, and some trades have specific requirements. The Small Business Administration and the Federal Trade Commission are reasonable starting resources for general guidance, but the specific terms should be reviewed by an attorney who knows your jurisdiction.
Collecting the deposit by payment link
The mechanics matter because friction at the payment step loses bookings.
Send a link, do not take a card over the phone. A payment link sent by text lets the customer pay from their own phone, in their own time, without reading a card number aloud. It also creates a record of the amount, the date and what the payment was for, attached to the job.
Send it while they are still engaged. The best moment is during the call or immediately after. A link sent hours later competes with everything else in the customer's day.
Confirm the booking when the payment clears. Tell the customer that the slot is held once the deposit goes through, and send the confirmation automatically when it does. That makes the sequence clear and avoids the awkward middle state of a booked job with no deposit.
Follow up on unpaid links. Some customers open the link and get distracted. A short reminder before the slot is released recovers many of them. The broader approach to reducing time-to-payment is in the guide to getting paid faster with payment links.
On Run with Jarvis, invoicing with three payment providers, the POS system and QuickBooks bidirectional sync are included on every plan, starting at Core for $500 per month. The deposit, the balance and the final invoice live on the same customer record, so whoever finishes the job can see what was already paid. Plan details are on the pricing page.
Stating the deposit on the phone
The phone is where a deposit policy succeeds or fails, because that is where the customer decides whether to book.
Say it as part of the quote. The deposit is information the customer needs to decide, so it belongs in the quote, not after the yes. "The part is special order for your vehicle, so we take the part cost, one hundred and ninety dollars, before we order it. If you cancel before it is ordered, you get all of it back."
Never introduce it after the booking is agreed. A customer who has said yes and then hears there is money due up front feels ambushed, even if the policy is completely reasonable. That surprise is what turns a fair deposit into a complaint.
Explain the why in the same sentence. "Because it is special order", "because it is a night call", "because it is a three-day job". The reason makes the request feel fair rather than suspicious.
Offer the easy path. "I can text you a secure payment link right now." That is easier than asking for a card and more trustworthy to many customers.
Be consistent. Whoever answers, whether a front-desk person, a technician, or the AI Receptionist, should say the same thing for the same situation. That consistency is the whole point of writing the policy. When the AI Receptionist answers, the deposit rule is part of the instructions it follows, in English or Spanish, and it states the amount and terms before asking for the booking.
Handle hesitation honestly. If a customer hesitates, restate what the deposit covers and the refund terms. If they are still unwilling on a special-order part, it is reasonable to decline to order it. A customer who will not commit to a part built for their vehicle is telling you something useful.
Avoiding disputes and chargebacks
A deposit dispute usually arrives as a chargeback: the customer asks their card issuer to reverse the payment. Your defense is the record you built when you took the deposit.
The record that wins. A written quote with the amount and terms. A payment link or receipt showing what the payment was for. A confirmation message restating the refund terms. And, for completed work, proof the job was done: photos, the signed-off job, a timestamped arrival. The more of this exists from the start, the easier any dispute becomes.
Match the description. The payment description the customer sees on their statement should make sense to them. A charge that looks unfamiliar invites a dispute from a customer who simply does not recognize it.
Respond to disputes quickly and completely. Card issuers set deadlines, and a thin response loses. The full approach is in the chargeback defense guide.
Chargeback defense is included on every Run with Jarvis plan. It works best when the quote, the terms, the payment and the proof of work already live on one record, which is another argument for not scattering those across separate tools.
Special cases worth deciding in advance
A written policy should cover the situations that come up often enough to cause arguments. Deciding them once is far easier than deciding them on the phone with a customer waiting.
Reschedules. When a customer moves a job rather than cancelling it, the deposit should normally carry over to the new date. Treating a reschedule like a cancellation punishes the customer for being honest about a conflict, and it pushes them to simply not show up next time instead of calling ahead. Decide how many times a deposit can roll forward before the refund terms apply, and say it.
Commercial accounts. Property managers and business customers with an established payment history usually work on invoice terms, not deposits. Asking a long-standing account for money up front on a routine job can damage the relationship for very little protection. Special-order parts are the exception worth keeping even for good accounts, because the part cost is real no matter who ordered it.
Jobs that change on arrival. Sometimes the technician arrives and the job is different from what was described: the part is not the one expected, the work is larger, or it cannot be done that day. The policy should say what happens to the deposit in each case. The fair default is that the deposit applies to whatever work is actually done, and anything unused is refunded or credited, with the customer told which before they leave.
Partial completion. On multi-day work, if the customer halts the job partway, the deposit should be reconciled against the work and materials delivered so far, with a written statement of what was applied. That statement is also the document you will want if the customer later disputes the charge.
Customers who paid but cannot be reached. Occasionally a customer pays a deposit and then goes silent. Set a rule for how many attempts you make to reach them and what happens to the money if the part arrives and nobody responds. Writing it down protects you from making it up under pressure, and a record of your attempts protects you if the customer reappears months later.
Training the team and the system on one rule
A deposit policy only works if every person and every system that talks to customers applies it the same way. That includes the front desk, the technicians who quote in driveways, the owner who takes calls from the truck, and the AI Receptionist.
Put the policy where people actually look: in the quoting instructions, in the booking rules, and in the price list notes for each service that needs a deposit. A policy that lives only in a binder in the office is one that nobody applies at 9 p.m.
Then check it. Once a month, pull a few jobs that required a deposit and confirm the deposit was stated, collected and recorded correctly. Where it was missed, find out whether the person did not know the rule or the rule was unclear, and fix the right one. Treating an unclear rule as a people problem is the fastest way to lose the team's cooperation.
Common mistakes
A few patterns cause most deposit trouble.
Asking for deposits on everything. Blanket deposits lose small, routine jobs to competitors who do not ask, and the protection they buy on those jobs is tiny.
Surprise deposits. Stating the deposit after the yes, or only in a text sent later, reads as a bait-and-switch.
Vague refund terms. "Deposits are non-refundable" with no explanation invites a dispute the first time you are the one who cannot perform.
Keeping money you have not spent. Holding a deposit for a part you never ordered is hard to defend and damages trust.
Losing track of what was paid. A deposit taken on one system and a final invoice built on another is how customers get billed twice or credited nothing. Keep them on the same record.
Where to start
Pull the last three months of jobs and mark every one where you lost money to a no-show, a cancelled special-order part, or a wasted night trip. That list tells you which deposit rules actually matter for your business.
Then write the policy on one page: which situations require a deposit, how much, and the refund terms for each. Add a one-sentence phone script for each situation, and make sure every person and system that answers the phone uses it.
Then set up payment links so the deposit is collected in the same call as the booking. Plans are on the pricing page: Core $500, Pro $750, Elite $1,200 per month, no setup fees, month-to-month. To talk through your policy against your own job mix, get in touch.
