How to handle a client who demands their deposit back as a solo beauty pro
The text arrives a few hours after a no-show, or the morning after a late cancellation, or occasionally before the client even bothers to ask nicely: "I want my deposit back" or "If you don't refund me I'll dispute it with my bank." Most solo pros handle this from one of two failure modes. The first is immediate capitulation — the guilt of holding a client's money feels worse than the deposit itself, so the refund goes out before anything is checked. The second is reflexive defensiveness — "the policy says non-refundable" typed out in under two minutes, followed by an increasingly hostile exchange that often ends in a dispute anyway.
Neither response is a framework. A framework starts with a documentation check before any message is sent. It continues with identifying which of four demand scenarios you are actually in. It produces a decision — hold, refund, or offer a rebook credit — that is grounded in the math of the specific deposit amount and the quality of your documentation, not in whatever emotion is running highest in the moment.
This guide covers the window between "client texts demanding the deposit back" and "client files a formal bank dispute." The formal chargeback process — when the client has already gone to her bank — is a different situation covered in the Stripe chargeback response guide and the deposit dispute evidence guide. This guide is about the conversation before that. You can still shape the outcome here. Once the client has called her bank, you are in a dispute response process with a defined timeline and a Stripe evidence queue. Before that, you have options.
Before you respond: the documentation check
Do not send any response until you have answered these four questions. This check takes less than two minutes and changes everything about how you should respond.
Question 1: Do you have a booking confirmation that shows the deposit amount AND the non-refundable policy?
A booking confirmation that shows "Deposit: $75" is not the same as one that shows "Deposit: $75 — non-refundable if cancelled within 48 hours." The first one confirms the client paid. The second one confirms the client paid with notice of the policy. In a Stripe dispute, the evaluator asks whether the policy was disclosed before the deposit was collected. A deposit amount alone does not answer that question.
Pull the confirmation that was sent at the time of booking. Read it literally. Does the word "non-refundable" or equivalent language appear? Is the cancellation window stated in hours or days? If the answer to either is no, your position in a dispute is weaker than you think.
Question 2: Was the policy visible before the client paid the deposit?
There is a meaningful difference between "the policy is on my website" and "the policy appeared on the payment page before the client entered her card." A policy buried in a terms page the client had to navigate to separately, a policy in a bio link that wasn't part of the booking flow, or a policy stated verbally without a written follow-up — all of these are weaker than a policy that appeared on the screen between "choose your appointment" and "pay the deposit."
If your booking flow routes through a tool that shows the policy inline before payment, note that. If your booking flow is an Instagram DM conversation where you told the client the deposit is non-refundable before they sent the payment — screenshot the conversation and note the timestamp. If you cannot identify the moment before the payment where the client saw the policy, that is an honest assessment of how strong your position is.
Question 3: What is the cancellation or no-show timestamp versus your policy window?
Your cancellation policy specifies a window. "48-hour notice required" means cancellations more than 48 hours before the appointment are eligible for a refund (depending on your policy) and cancellations within 48 hours are not. Verify the actual timestamp of the cancellation message or the absence of a message.
If the client cancelled at 10:00 PM the night before a 9:00 AM appointment, that is 11 hours of notice against a 48-hour policy — clearly inside the window. If the client cancelled at 10:00 AM two days before the appointment, that is 47 hours against a 48-hour policy — arguably inside the window depending on how you count. Know the exact number before you communicate it.
Question 4: Did you say or write anything that could be read as a refund promise?
Search your DMs, texts, and emails with this client. If you have ever written "no worries, I can refund that," "I'll make an exception this time," or any variation — even for a different appointment — you have a complication. A client who received one exception will treat it as the established policy, and a Stripe evaluator reading that exchange will see it the same way.
If you find an exception granted in writing, note it. You may still hold the policy on the current demand — prior exceptions don't obligate future ones — but the communication about it needs to acknowledge the history rather than pretend it doesn't exist.
The four deposit demand scenarios
Every deposit demand falls into one of these four categories. The documentation check above tells you which one you're in. The response follows from the scenario, not from the tone of the demand.
Scenario 1: The demand is legitimate
This scenario is more common than most solo pros want to admit. The demand is legitimate when: you did not clearly disclose the non-refundable policy before the client paid; the client cancelled outside your stated policy window; you made a previous written exception that the client is reasonably relying on; or you communicated a refund promise and are now trying to walk it back.
In Scenario 1, refund the deposit. Not because the client is right on principle, but because you would lose a formal dispute anyway — and defending a dispute you're going to lose costs you the dispute fee ($15–25) plus the time to respond (30–60 minutes at your effective hourly rate) plus the deposit you'll return anyway. The proactive refund costs only the deposit.
When you refund in Scenario 1, include written settlement language. Do not simply process the refund and say nothing. The message matters:
"Hi [Name], I've processed a full refund of your $[amount] deposit — you should see it back within 3–5 business days. I also want to make sure our booking confirmation clearly states the cancellation policy going forward, so there's no confusion for future appointments. Thanks for reaching out directly."
The last sentence — "thanks for reaching out directly" — is not flattery. It is a clear signal that the preferred resolution channel is a direct message, not a bank dispute. That framing matters for clients who are on the fence about whether to go to their bank.
After this conversation, fix the documentation gap that put you in Scenario 1. If your policy wasn't clearly disclosed before payment, that is the fix — not the refund.
Scenario 2: The demand has partial validity
This is the most common scenario for long-term clients and for clients who cancelled inside the policy window but have a documented reason that isn't pure convenience. A client with 18 months of clean appointments who cancelled 12 hours before her appointment because her child was in the emergency room — and who has the hospital paperwork — is different from a client with two prior last-minute cancellations who has a vague excuse this time.
In Scenario 2, the decision is mathematical before it is relational. Run the refund math before you decide whether sympathy or policy should win.
For a deposit under $75 with documentation that isn't airtight: the expected cost of defending an uncertain dispute often exceeds the deposit value. A disputed $50 deposit with 50% win probability costs you $20 in dispute fees plus $30 in response time, and you recover the $50 in only half of those scenarios. Expected cost of defending: $20 + $30 + (0.50 × $50 loss if you lose) = $75. You spend $75 defending a $50 deposit that may or may not be yours to keep. In that math, the proactive refund is cheaper.
For a deposit of $100 or more with strong documentation (policy clearly disclosed, cancellation inside the window, no written exceptions): the math tips toward holding. A $100 deposit with a 75% win probability in dispute costs you $20 in fees plus $30 in time plus $25 expected loss ($100 × 0.25) = $75 in expected defending cost. You retain $75 net in expectation from a $100 deposit — worth defending.
For Scenario 2, the "apply toward a future appointment" offer is the most useful tool in the conversation. It is not a refund — the deposit stays with you. It converts a dispute-threat scenario into a future transaction scenario, and costs you nothing if the client rebooks. If the client never rebooks, you keep the deposit anyway:
"Hi [Name], I understand you had a difficult situation come up. I'm not able to issue a cash refund under our cancellation policy, but I can apply your $[amount] deposit toward your next appointment if you rebook within 60 days. Just reach out when you're ready and I'll hold it for you. I hope things are better on your end."
The 60-day window is intentional. It is long enough to feel generous without being indefinite. If the client doesn't rebook in 60 days, the deposit is retained under the original cancellation terms.
Scenario 3: The demand is policy-violating with strong documentation
The client cancelled inside the policy window with no extenuating circumstances, the policy was clearly disclosed at booking, there is no prior written exception in your records, and the cancellation timestamp is unambiguous. This is the scenario most solo pros think they are in when the demand arrives — and sometimes they are wrong because they haven't done the documentation check. If you have done the check and the documentation is genuinely strong, Scenario 3 is where you hold the policy.
The most common mistake in Scenario 3 is communicating the policy as if it's a personal decision. "I can't give you your deposit back" positions you as the decision-maker who chose this outcome. "Our policy is that deposits are non-refundable within 48 hours of the appointment, and your cancellation came in at [time], which is [X] hours before your appointment" positions the policy and the documentation as the decision-maker. The second framing is harder to argue with because there's nothing personal to push against.
"Hi [Name], I checked your booking — your cancellation came in at [time] on [date], which is [X] hours before your [time] appointment. Our policy is that deposits are non-refundable with less than 48 hours notice, and that was included in your booking confirmation. I'm not able to issue a refund, but I'd be happy to apply the deposit toward a future appointment if you'd like to rebook."
The rebook offer at the end is the same tool as Scenario 2, but here it follows the policy statement rather than leading it. In Scenario 2 you're offering it as the primary resolution. In Scenario 3 you're offering it as a goodwill option after clearly stating the policy hold.
If the client responds with "I'll dispute it then" — that is a Scenario 3 sub-situation covered below.
Scenario 4: The demand is a manipulation tactic
Some clients do not ask — they open with the threat. "Refund my deposit or I'll dispute this with my bank." Or the demand is for more than the deposit: a full service refund, a free redo, or a combination that exceeds the deposit value. These are not good-faith requests for resolution — they are attempts to convert a cancellation policy into a negotiation using the threat of a bank dispute as leverage.
Recognizing Scenario 4 matters because the correct response is different from Scenario 2 or 3. In Scenario 2 and 3, you might open with the rebook credit offer as a goodwill gesture. In Scenario 4, offering the rebook credit in response to an explicit threat rewards the threatening behavior and trains this client — and anyone she talks to — that the correct way to get your deposit back from you is to threaten a dispute.
The Scenario 4 response is factual and non-confrontational, but it does not lead with accommodation:
"Hi [Name], I understand. If you decide to file a dispute with your bank, the booking confirmation and cancellation record will be submitted as documentation — the policy disclosure, the deposit amount, and the cancellation timestamp are all on file. I'm happy to resolve this directly: I can apply your deposit toward a future appointment within 60 days if that works for you. But I'm not able to issue a cash refund given the timing of the cancellation."
This response does three things: it acknowledges the threat without reacting to it, it demonstrates that you have documentation without making it sound like a dare, and it still offers the rebook credit as a legitimate resolution path. The client who hears this understands that a dispute is not going to be a surprise — you have a record and you know what to do with it.
Do not threaten counter-action. Do not promise to write a bad review about them. Do not escalate language. One calm, documented response is more useful than three angry ones.
The explicit dispute threat: how to respond without folding or escalating
The explicit dispute threat is a sub-situation that can appear inside any of the four scenarios above, but it deserves its own treatment because the instinct to respond to it is strong and usually wrong. When a client says "I'll dispute this with my bank," most solo pros feel one of two things: fear (the dispute will be devastating to the business) or anger (how dare she). Both responses produce bad messages.
The fear response produces a refund offer that is faster and larger than the situation warrants — sometimes including more than the deposit because the pro wants the threat to go away. The anger response produces an escalating exchange that generates screenshots the client can include in a dispute filing and occasionally generates a review that is worse for the business than the dispute itself.
The correct response to an explicit dispute threat treats it as information, not provocation. The client has told you what she's considering doing. You are neither surprised nor frightened. Your documentation exists. Your response is calm because your position is clear:
"I understand — if you file a dispute, I'll submit our booking confirmation and cancellation record as documentation. I'd prefer to resolve this directly. I can apply your deposit toward your next appointment within 60 days. Let me know if that works."
Send this once. If the client responds with another threat, do not send a second version of the same message. If she files the dispute, you respond through Stripe with the documentation you already located in the check above. If she accepts the rebook credit, you've converted a dispute into a future transaction. If she goes silent, the deposit remains as retained income under your cancellation policy.
One important mechanical note: the dispute threat message itself is documentation. Screenshot it or save the text. If a formal dispute is later filed, the record of the client explicitly threatening the dispute before filing can be included in your evidence as context for the dispute's motivation.
The proactive-refund math: when refunding is cheaper than defending
This section runs the numbers so you don't have to do it under pressure in the moment. The question is not whether you have the right to keep the deposit — if your documentation is strong and the policy was clearly disclosed, you almost certainly do. The question is whether exercising that right is financially advantageous compared to refunding.
Defending a Stripe deposit dispute has three costs:
- Dispute fee: $15–25 charged by Stripe or Square regardless of whether you win or lose.
- Response time: 30–60 minutes to locate documentation, write the response, and submit it through the processor's interface. At your effective hourly rate — say $90/hr for a colorist — that is $45–90 in time value.
- The deposit itself if you lose: If you lose the dispute, the deposit is returned to the client and the dispute fee is not refunded.
The expected cost of defending depends on your win probability. Win probability in a deposit dispute is primarily a function of documentation quality:
- Strong documentation (policy disclosed before payment, cancellation timestamp clearly inside the window, no written exceptions): estimated 70–75% win rate based on reported solo beauty operator outcomes.
- Weak documentation (policy not clearly visible before payment, ambiguous timing, prior written exceptions): estimated 30–40% win rate.
Run the math for your specific situation:
Example A — $50 deposit, weak documentation (40% win probability):
Expected defending cost = $20 fee + $45 time + (0.60 × $50 deposit loss) = $95.
Deposit value: $50. Net outcome from defending: −$45 (you expect to lose
more defending than the deposit is worth). Refund proactively.
Example B — $50 deposit, strong documentation (75% win probability):
Expected defending cost = $20 fee + $45 time + (0.25 × $50 deposit loss) = $77.50.
Deposit value: $50. Net outcome from defending: −$27.50. Still negative
expected value. The $50 deposit is too small to justify the defense cost
even with strong documentation.
Example C — $100 deposit, strong documentation (75% win probability):
Expected defending cost = $20 fee + $45 time + (0.25 × $100 deposit loss) = $90.
Deposit value: $100. Net outcome from defending: +$10. Marginally positive
expected value. Defend if you have time; consider the rebook credit offer
first.
Example D — $150 deposit, strong documentation (75% win probability):
Expected defending cost = $20 fee + $45 time + (0.25 × $150 deposit loss) = $102.50.
Deposit value: $150. Net outcome from defending: +$47.50. Clearly worth
defending. Hold the policy.
The crossover point — where the expected value of defending equals the deposit — sits around $100–120 for most solo beauty pros at typical effective hourly rates. Below that threshold with weak documentation, the refund is almost always the cheaper choice. Above that threshold with strong documentation, the defense is worth running.
This math does not account for the behavioral compound: a client who received a proactive refund once may demand again. A client who received a clear policy hold with documentation rarely demands a second time. If you have reason to believe the client will return with another demand, the behavioral compound tips the math toward holding even on small deposits.
The rebook credit as a resolution tool
The "apply toward a future appointment" offer appears in every scenario above because it is the most useful resolution tool in a deposit demand conversation. Understanding what it is and what it is not helps you use it correctly.
A rebook credit is not a refund. The deposit stays in your account. You are not returning the money — you are agreeing that the money will be applied against a future service rather than against the missed appointment. If the client never rebooks within the stated window, the deposit reverts to retained income under your cancellation policy.
This structure has two advantages over a cash refund. First, the client who accepts the rebook credit has agreed to return — which converts a dispute scenario into a future revenue opportunity. Second, the client who accepts and then doesn't return loses the credit by inaction, not by your decision — which removes the emotional charge of "you stole my deposit" from the outcome.
When to offer the rebook credit:
- As the primary resolution in Scenario 2 (partly valid demand)
- As an add-on to the policy statement in Scenario 3 (strong documentation, holding the policy)
- As the resolution alternative in Scenario 4 after demonstrating documentation awareness (but not as a concession to the threat itself)
When NOT to offer the rebook credit:
- As the first response to an explicit dispute threat before any policy communication (rewards the threatening behavior)
- When the client already has a history of no-showing or cancelling rebooked appointments — the credit converts a held deposit into an eventual no-show
- When you have already decided to fire this client — offering a rebook credit while simultaneously intending not to rebook her creates a different kind of problem
The rebook credit window matters. Thirty days is too short — it creates urgency that can feel punitive. Ninety days is too long — it stays on your books as an open liability for too long. Sixty days is the standard that most solo pros find produces the best rebook rate without becoming a permanent obligation.
After the conversation: documentation in the client record
Regardless of how the demand resolved — refund, rebook credit, or held policy — write a note in the client record before you move on. The note should include:
- The channel and date of the demand (DM on [date], text on [date])
- The exact demand ("Requested full deposit refund; cancellation was [X] hours before appointment")
- The action you took (refund processed, rebook credit offered, policy held)
- Any dispute threat included in the demand (exact language, date)
- The client's response to your resolution offer
If you made an exception — refunding in a situation where your documentation was strong enough to hold — note it explicitly: "One-time exception granted on [date]; future deposits held under full policy." This protects you if the same client demands again. A prior written exception you granted once without documentation is a precedent. A prior written exception that is explicitly noted as a one-time exception is not.
If the client threatened a dispute, save the message. Screenshot it or copy the text into the client record. If a formal dispute is filed within 60–120 days, this message is part of your evidence bundle — it shows the dispute was threatened before it was filed, which provides context that the bank evaluator will see.
If the conversation ended with no resolution and no formal dispute, note the open status: "Deposit demand unresolved as of [date]; no dispute filed as of [date]; monitoring." A client who threatened and didn't follow through immediately may file weeks later when they realize the charge has been on the card long enough.
Vertical-specific patterns
Each solo beauty vertical has common demand scenarios that repeat with enough frequency to warrant vertical-specific handling.
Colorists
The most common deposit demand in the colorist vertical comes after a same-day cancellation or no-show where the client claims she "wasn't feeling well" — a vague reason that's difficult to dispute and difficult to verify. The colorist's instinct is to extend sympathy and refund. The documentation check changes the calculation: if the booking confirmation includes the policy, the cancellation timestamp is clear, and no written exception was previously granted, the rebook credit offer is the appropriate first response, not a refund.
Color correction clients generate a distinct demand pattern: the client who disputes the deposit after a consultation but before the service began, claiming the consultation alone isn't worth the deposit. This is a Scenario 1 or Scenario 3 situation depending on how you structured the deposit. If your deposit was for the appointment slot (not for the service), and the consultation was a full 30–45 minute analysis with strand tests, that consultation was a service you delivered. Document it as such: time spent, test results, products used. A consultation note that reads "30 min analysis, discussed realistic outcome range, performed strand test, determined color was not achievable in one session" is a record of service delivered, not just a conversation.
Lash artists
The lash vertical sees deposit demands most often in two patterns: the same-day cancellation with a claimed sensitivity or allergic reaction concern, and the client who cancelled after a long appointment window without contacting you and now claims she "couldn't get there."
For claimed sensitivity or allergic reaction demands, request documentation of the reaction before offering any refund or credit. "I'm concerned about a potential sensitivity" as a cancellation reason does not automatically entitle the client to a deposit refund — a sensitivity patch test should have been conducted at a prior appointment, and the record of that patch test result is relevant documentation.
If you have a patch test record showing the client was tested and had no reaction, that changes the demand conversation. If you have no patch test record because the client is new and you offer patch tests only at a separate appointment, document the intake process that led to the decision to proceed — and revisit whether that process is working as a documentation system.
Nail technicians
The nail vertical's most common deposit demand scenario is not a cancellation demand — it is a post-service damage claim combined with a deposit refund demand for the next appointment. The client had her nails done, reported a chip or lift within 24 hours, and is now asking both for a free redo and for the deposit on her next booking to be refunded because "I don't trust the work."
These are two separate requests and should be addressed separately. The redo request (if within your stated redo window and consistent with your redo policy) is a service issue. The deposit refund request for a future appointment is a cancellation policy issue applied to an appointment that hasn't happened yet.
Address the redo first: offer the complimentary fix within your stated window if the claim is consistent with a legitimate nail application issue. Then address the deposit separately: "Your deposit for the [date] appointment is held under our standard policy — if you'd like to keep that appointment, the deposit applies to the service. If you need to cancel, our standard policy applies." Keeping them separate prevents the damage claim from becoming a leverage tool for the deposit refund.
PMU and brow artists
PMU deposit demands are the highest-stakes version of this conversation because deposits in this vertical typically run $100–$200. The most common scenario is a client who books, pays the deposit, and then gets cold feet in the two to four weeks between booking and appointment — often after seeing something online that changes her expectations or frightens her.
The PMU deposit demand that arrives before the appointment — not after a completed service — is usually Scenario 2 (partly valid, first-time request from a client who hasn't had the service yet and is genuinely uncertain). The rebook credit offer works well here: it keeps the relationship open for a client who may be ready in three to six months when her hesitation resolves.
The deposit demand that arrives after a consultation where the client agreed to the procedure and then changed her mind is Scenario 3 in most cases, because the consent form and consultation documentation is the policy disclosure. If you have a signed consent form that includes the deposit terms, that is strong documentation. Hold the policy and offer the rebook credit.
For PMU specifically, the math in the proactive-refund section above almost always favors defending: a $150+ deposit with strong documentation (consent form, intake documentation, policy disclosure) is worth the response time in any dispute scenario.
Mobile groomers
Mobile groomers face a deposit demand scenario unique to their vertical: the client who cancels same-day, sometimes after the groomer has already driven to the location, and then demands a full deposit refund because "the dog was too stressed" or "something came up."
When the cancellation happens after travel has begun, the deposit gap is larger than the stated amount — the travel cost (fuel, time, wear on the vehicle) is a sunk cost that the deposit may not fully cover. This is a Scenario 3 situation where holding the policy is financially important and documenting the travel cost is critical: note the departure time, the mileage driven, the destination, and the time of the cancellation message if it arrived while you were in transit.
The mobile groomer who cancelled mid-service for a dog behavior reason — the dog was unmanageable, the groom couldn't be completed safely — is a different situation where a partial refund proportional to the work completed may be appropriate. The deposit for a full groom applied to a partial groom is the standard resolution, documented with a note on what was completed and why the service stopped.
Six common mistakes in deposit demand conversations
Mistake 1: Responding before doing the documentation check
This is the most common mistake. The demand arrives, the pro responds within minutes from pure emotion — guilt, defensiveness, or a combination — and the response either gives away money that didn't need to be refunded or commits to a position she can't defend. Two minutes of documentation review before any response changes the conversation completely. Do the check first, every time.
Mistake 2: Apologizing in the first response
"I'm so sorry about this" as an opener signals uncertainty about the validity of your own policy. Clients who receive an apology as the first message hear: "I feel guilty about keeping this money," which they reasonably interpret as an opening for negotiation. Empathy is appropriate; apology for holding a valid policy is not. "I understand this is frustrating" is different from "I'm sorry I have to do this."
Mistake 3: Leading with the rebook credit in response to an explicit dispute threat
If the client opened with "I'll dispute this," and your first response is the rebook credit offer, you have communicated that threatening a dispute produces a benefit. The correct sequence in Scenario 4 is: demonstrate documentation awareness first, then offer the rebook credit as an alternative to the dispute path, not as a concession to the threat.
Mistake 4: Handling the conversation by phone with nothing in writing
If the client calls and you resolve the demand verbally — agreeing to a refund, offering a rebook credit, or explaining the policy — you have no written record of what was agreed. Follow any phone conversation with a written summary sent to the client: "Following up on our call today: I've applied your $[amount] deposit toward a future appointment. If you rebook within 60 days, it will apply to the service. Please reach out when you're ready." If you held the policy verbally, a written follow-up confirming it is important: "Following up to confirm: I'm not able to issue a refund under our cancellation policy, as your booking confirmation includes the terms we discussed."
Mistake 5: Losing the dispute threat message
An explicit dispute threat that arrives in a DM or text has evidentiary value in the formal dispute process. A client who threatened a dispute before filing one has shown premeditation, which is relevant context for the bank evaluator. If the dispute is later filed, the threatened-before-filing message belongs in your evidence bundle. Screenshot it the moment you see it. Do not rely on finding it again later in a threaded conversation.
Mistake 6: Refunding without written settlement language
A refund processed without any written confirmation of what it settles leaves the door open for a chargeback filed after the refund is received. It sounds implausible — the client got her money back and then disputes the same charge — but it happens when the client believes she is also owed a redo, or when she disputes before the refund posts, or when the refund and the dispute are in flight simultaneously. When you process a refund, send a message the same day: "I've processed your refund of $[amount] — this concludes the [date] appointment. You'll see it in your account within 3–5 business days."
Three-year compound: the precedent effect of how you handle demands
Two solo lash artists, same market, same price point, same cancellation rate — 8% of appointments produce a last-minute cancellation, which works out to roughly one demand conversation every six to eight weeks at a full booking schedule.
Artist A handles each demand the fastest way available — usually a refund, often without doing the documentation check, because it feels easier than a confrontation. Over three years, she handles 24 demand conversations this way. She refunds 20 of them (five per year), retaining the deposit in four cases where the client accepted the rebook credit without pushing back. Average deposit: $60. Total unnecessary refunds: 15 (the five where documentation was strong enough to hold × 3 years) = $900. Additionally, a precedent builds: by year two, she notices she is receiving more demand conversations because the word in her client base is that she will refund if you ask. Demand rate increases to one per four weeks. She absorbs an additional $360 in years two and three from the higher demand rate — total unnecessary outflow from the precedent effect: approximately $1,260 over three years.
Artist B does the documentation check before every response, holds Scenario 3 demands with the policy and rebook credit offer, refunds Scenario 1 and 2 demands proactively with settlement language, and responds to Scenario 4 demands calmly with documentation awareness. Over three years, she handles the same 24 initial demand conversations. She refunds 8 of them (Scenario 1 and 2 cases). She holds 16 with documentation, offering the rebook credit. Twelve of those sixteen either accept the rebook credit or go silent — no formal dispute. Four file formal disputes; she wins three with her booking confirmation and cancellation records. She pays four dispute fees ($80 total) and response time on four disputes (approximately four hours at $60 effective rate = $240). She retains approximately $960 in held deposits across sixteen cases (16 × $60 average). Net position from held deposits: $960 retained − $80 fees − $240 time = $640.
The demand rate for Artist B does not increase over three years. It decreases slightly — clients who received the policy hold with documentation do not repeat the demand, and the ones who filed disputes and lost do not rebook. The client mix slowly self-selects toward clients who show up for their appointments.
Three-year difference from how they handle deposit demand conversations: approximately $1,900 in net position from the same cancellation rate, the same price point, and the same number of demand conversations. The entire gap comes from whether the documentation check runs before the response.
One-time setup: making the documentation check faster
The documentation check takes two minutes when everything is in one place and thirty minutes when it is spread across three apps, a DM thread, and a camera roll. Run this setup once, outside of any demand conversation:
- Save one copy of your current booking confirmation template to a notes app, clearly showing the deposit amount and the non-refundable policy language. When a demand arrives, open this first — it tells you immediately whether the current policy version includes clear disclosure.
- For each client, note the channel where your pre-booking conversation happened (DM, text, booking link, Square). When a demand arrives, you can immediately pull that channel and find the cancellation timestamp and any prior exception language without searching.
- Maintain a simple exception log — a note or a row in a spreadsheet — any time you refund a deposit that you technically didn't have to. One row: client name, date, deposit amount, reason. This takes fifteen seconds per exception and saves you from the situation where a client references a prior exception you can't find and can't remember.
- Write your four scenario responses as drafts now. When a demand arrives, you copy the appropriate draft, fill in the specifics, and send — rather than composing from scratch under pressure. The drafts don't need to be polished scripts; they just need to exist so you reach for them before you reach for a refund.
The demand conversation is almost always winnable — or at least resolvable without unnecessary loss — when the documentation exists and the response follows the framework rather than the emotion of the moment. Most solo pros who lose deposit demands lose them not because the client had the legal right to a refund, but because the documentation wasn't clear enough to hold the policy with confidence.
If you want the booking confirmation, cancellation record, and client history in a single place so the two-minute documentation check actually takes two minutes — rather than a half-hour search across three apps and an old DM thread — ChairHold is in early access at $9/month: one booking link, deposit to your Stripe, and every client's booking history, deposit status, and cancellation record in a single record from the first transaction forward.