What PoolBoss Says
Respond inside your processor's dispute window - commonly 7-21 days - with dated proof the service happened: the visit record with chemical readings and a photo, the signed service agreement, and the invoice. Then call the customer, because most disputes on a recurring service are a forgotten charge, not fraud.
The email arrives on a Tuesday and it is never a good one: a payment you collected weeks ago has been pulled back out of your account, the customer's bank is asking you to justify it, and there is a date attached. A chargeback is not the same problem as a customer who never paid - that money arrived, cleared, and got spent on chemicals and payroll before anybody questioned it.
What makes this winnable is that the evidence was created at the pool months before the dispute existed, if you were keeping records at all. What follows is the deadline and what to send, which evidence answers which dispute reason, why a phone call usually beats a formal response, and what the whole thing costs even in the cases you win.
At a glance
Key takeaways
- Respond inside the processor's window - commonly 7-21 days from their notice, not from when you read it - because a missed deadline loses the dispute regardless of your evidence.
- Read the dispute reason code first and answer that specific claim; sending general proof that you are a real business is how defensible disputes get lost.
- Call the customer before you file - most recurring-service disputes are an unrecognized charge, and a withdrawn dispute closes in days instead of 60-90.
- Your proof of delivery is a timestamped visit record with chemical readings and a photo, not a tracking number - collect it on every stop, not after an email arrives.
- Expect a $15-25 dispute fee that you pay whether you win or lose, and expect the disputed amount to be debited while the case is open.
- Set your statement descriptor to the name customers know you by, and send a report or itemized invoice each cycle so the charge always arrives with the work attached.
- Move an account to prepay or end it if the same customer disputes twice - at that point you are not resolving a misunderstanding.
What do I do if a customer disputes a pool service charge?
Work it in four steps, and start the same day the notice lands, because the clock is the part you cannot get back. Processors typically give you 7-21 days to respond and the window is counted from when they notified you, not from when you opened the email. Miss it and the dispute is decided against you by default, regardless of how good your records are.
First, read the dispute reason code - it tells you exactly what the card network wants proof of, and sending the wrong evidence is the most common way a defensible dispute is lost. Second, pull the paperwork: the visit records for the period being disputed, the service agreement, and the invoice and payment record behind the charge. Third, call the customer before you file anything. Fourth, submit your response through the processor's dashboard, one document per claim, with a short plain-English cover note.
Keep it separate in your head from an unpaid balance. A disputed charge is money that arrived and was reversed by a bank, on a bank's timeline, with a bank deciding the outcome; a customer who simply never paid is yours to chase on your own schedule, with reminders and a pause-service rule. The two feel similar on the day you notice the money is missing and they call for completely different moves.
Each dispute reason asks for a different piece of evidence
Match what you send to what is actually being claimed. A dispute is not a general request to prove you are a real business - it is a specific allegation, and the response that wins is the one document that contradicts that specific allegation. Most pool service disputes land in one of four buckets, and three of the four are answered by records you already generate on every stop.
| What the customer claimed | What answers it | Also include |
|---|---|---|
| "I never authorized this charge" | The signed service agreement plus the customer's own autopay enrollment or prior paid invoices on the same card | The payment history showing months of accepted charges |
| "The service was never performed" | Timestamped visit records for every stop in the billing period, with chemical readings and photos | The route record showing the tech was on the property |
| "The service was not as described" | The service agreement's scope of work next to the visit records showing that scope was performed | Any texts or emails where the customer acknowledged the service |
| "I was billed twice" or "I cancelled" | The invoice history showing one charge per period, and the dated cancellation request if one exists | Your written cancellation terms and notice period |
Most recurring-service disputes are a forgotten charge, so call before you fight
Pick up the phone before you build a case, because on a recurring service the most likely explanation is that nobody recognized the charge. Card disputes run well under 1% of transactions for most small service businesses, and the ones that do happen on a route are rarely fraud - they are a spouse who does not handle the pool, a statement line that reads like a company nobody recalls hiring, or a customer who thought they cancelled in March and did not put it in writing. A two-minute call sorts most of that out.
The move that ends it fastest is asking the customer to withdraw the dispute with their own bank, which they can usually do by calling the number on the card. That is worth doing even when you would win, because a withdrawn dispute closes in days while a contested one runs 60-90 days and sometimes longer before the network decides. Send the customer the visit dates and a copy of the invoice while you are on the call, so they are looking at the same thing you are.
Stop being nice at the point where the story stops changing shape. If a customer acknowledges the service happened and still will not withdraw the dispute, or if the same account has done this twice, you are no longer resolving a misunderstanding - you are being used as a free service. File the response with everything you have, and treat the account as one to move to prepay or end after the dispute closes, whichever way it goes.
A timestamped visit record with readings and a photo is your delivery confirmation
Every chargeback guide written for online sellers tells you to submit proof of delivery - a tracking number, a signature, a carrier scan. None of that exists for work performed in somebody's backyard, which is why generic advice is useless the moment you try to apply it to a route. Your equivalent of a tracking number is the visit record: the date and time the tech started and completed the stop, the chemical readings logged there, and a photo of the water.
That combination is hard to argue with because it is granular and it is dated. Three numbers, a timestamp, and a picture of a clean waterline say the tech stood at that pool far more convincingly than an invoice line that says "August service" ever will. This is the same record that answers a quality complaint or a liability question, so the visit record that proves the service happened is worth keeping properly for reasons that have nothing to do with disputes.
Take a three-truck operator running 210 pools around Cape Coral who gets a $340 dispute in October on a quarterly-billed account. The visit records for all four August and September stops carry a start time, free chlorine and pH readings, and a photo of the waterline; the service agreement is on file with the rate and the schedule. Assembling the response takes about fifteen minutes, because none of it is being reconstructed - it was collected at the pool months before anyone disputed anything. The operator who logged those stops on paper spends the same afternoon deciding whether the $340 is worth the search.
PoolBoss keeps that record as a byproduct of the visit rather than a separate filing job: the tech logs readings and photos on the stop, and the visit stays attached to the pool and the invoice it was billed on. What the software does not do - and no pool service software does - is file the dispute for you. The response happens in your payment processor's dashboard. Your side of it is having evidence worth submitting.
A dispute costs you even when you win
Budget for the fee regardless of outcome. Processors commonly charge a dispute fee in the $15-25 range, and it is usually non-refundable even when the decision goes your way - you are paying for the bank's handling, not for being right. On top of that the disputed amount is typically debited from your account while the case is open, so a $340 dispute is $340 of working capital gone for two or three months on a maybe.
Run the arithmetic against the account, not against your whole month. With weekly residential service running roughly $150-$225 a month in most markets, a single $25 dispute fee is more than a tenth of what that customer pays you for a month of work, before you count the hour you spend on the response. Card acceptance already costs you something - what taking cards actually costs runs about 2.5-3.5% per transaction - and a dispute is the tail risk on top of that, rare but expensive when it lands.
There is also a threshold worth knowing about: card networks monitor merchants whose dispute ratio climbs past roughly 1% of transactions, and merchants who stay above it face higher fees or, at the far end, losing card acceptance. A pool route will almost never get near that - one dispute a year against a few hundred transactions is nowhere close - but it is the reason a pattern of disputes on one account is worth ending rather than absorbing.
Prevention is a recognizable statement line, a monthly report, and a card the customer set up themselves
Nearly every preventable dispute comes from a customer not recognizing the charge, so make the charge recognizable in three places. Set your payment processor's statement descriptor to the business name the customer actually knows you by - if they hired "Blue Water Pools" and the statement says a holding company name, you have manufactured a dispute. Send a service report or an itemized invoice each cycle so the amount arrives with the work attached. And keep the service agreement current, because it is the document that answers the authorization claim.
The agreement carries more weight here than operators expect. The service agreement the charge rests on is what turns "I never agreed to this" into a paperwork question rather than a credibility contest, and it is also where your cancellation notice period lives - the term that decides who is right when a customer says they cancelled. A signed agreement plus a payment history on the same card is close to unanswerable on an authorization dispute.
Autopay helps for a reason that is easy to miss: in PoolBoss the customer enrolls their own card or bank account through their portal, so the authorization is something they set up themselves rather than a number you keyed in. That is a materially better position to argue from than a card on file the customer does not remember giving you. Pair it with a report that lands every month and the customer sees the work before they ever see the statement line - which is the whole game, because a dispute you never receive costs nothing to win.
FAQ
Frequently asked questions
Do I lose the money while the dispute is open?
Usually yes, temporarily. Most processors debit the disputed amount from your account as soon as the dispute is filed and hold it until the case is decided, so a $340 dispute is $340 you cannot spend for the 60-90 days a contested case typically runs. If you win, the amount is returned; the separate dispute fee generally is not. Plan for this rather than being surprised by it - the practical impact on a small route is a cash-flow hole in the middle of a month, not a permanent loss. It is also a good argument for resolving the dispute directly with the customer, because a dispute they withdraw releases the hold far sooner than one that goes to a decision.
Can I charge the customer back for the dispute fee?
In practice, no - and trying to is usually a bad move even where nothing forbids it. Adding a $25 fee to the account of a customer who just disputed a charge is close to guaranteed to produce a second dispute, and now you are the merchant with a pattern. The cleaner response is commercial rather than punitive: if the dispute was frivolous, the account is one to move to prepay or to end. Where an operator does recover something, it is normally through the service agreement's own terms on returned or reversed payments, agreed to before any of this happened, not a fee invented after the fact. Check your state's rules and your processor's agreement before adding any fee of this kind.
Should I keep servicing a pool while a payment is disputed?
Keep servicing for now if it is a first dispute on a long-standing account, and stop if the same customer has done it before. The reasoning is practical: most first disputes are a misunderstanding that resolves in a week, and cancelling service over one turns a fixable problem into a lost customer. What you should not do is keep accumulating unbilled work on an account that is actively refusing to pay - if the dispute is still open after a full billing cycle and the customer will not talk to you, pause the stop the way you would for any non-payment. Document the decision either way, because a service you continued in good faith reads well if the dispute escalates.
Can I stop taking cards from a customer who has disputed before?
Yes. Nothing obliges you to accept a particular payment method from a particular customer, and moving a repeat disputer to check, cash, or bank transfer is a normal commercial decision. Tell them plainly and without drama: the account is moving to payment by check before service going forward. Bank payments are not immune to reversal, but the process is narrower and the informal dispute route a card gives a cardholder does not exist in the same form. The stronger version of this move is prepayment - the month is paid before it is serviced - which removes the exposure entirely. Reserve both for the accounts that have actually shown you a pattern, not for a customer who queried one charge and then paid it.
Can I still collect the balance if I lose the dispute?
Losing a dispute settles who holds the money, not whether the debt exists - so yes, an unpaid balance for work you performed is still owed, and you can pursue it the way you would any other unpaid invoice. What you cannot do is re-charge the same card for the same transaction; that is prohibited by the card networks and will produce a worse outcome. Invoice the balance, send it in writing with the visit records attached, and treat it on your normal past-due timeline. For amounts large enough to be worth it, small claims is the usual route, and the same evidence pack you assembled for the dispute is what the court wants to see. For small amounts, ending the account is often cheaper than pursuing it.
Is a disputed bank or ACH payment handled the same way as a card chargeback?
No - bank payment reversals run on different rules and, for consumer accounts, often a longer window. A consumer can typically have an unauthorized bank debit returned for up to 60 days after the statement it appeared on, and the return is generally processed on the customer's assertion rather than through the evidence-submission process a card dispute uses. That means your defence is front-loaded: a signed authorization for the debit, kept on file, matters more than anything you can send afterwards. The practical implication for a pool route is that bank payments are cheaper than cards and reverse less often, but when one does reverse you have fewer moves available, so keep the enrollment record for every account paying that way.
