A Customer Says You Damaged Their Property — Now What?

It's Going to Happen to You (If It Hasn't Already)

A customer texts you at 6pm: 'Your crew hit my sprinkler head today. I want it fixed.' Or worse — 'There are ruts in my lawn and I'm not paying until this is resolved.' Maybe you've already been there. Maybe you're reading this because you're there right now.

Every operator who runs enough crews for enough seasons will eventually face a damage claim or a billing dispute. It's not a question of if. The question is whether you have a process when it happens — or whether you're winging it every time while your stomach drops and your cash flow stalls.

Most operators don't have a process. They handle each dispute emotionally, inconsistently, and reactively. That costs money. Sometimes it costs customers. And occasionally it costs a lawsuit or a bad review that follows the business for years.

The Claims That Actually Show Up (And the Ones That Don't)

Let's be honest about what damage claims actually look like in this business. The vast majority are small and legitimate: a broken sprinkler head, a dinged fence post, tire ruts from a heavy mower on wet turf, a trimmer line that caught a flower bed. These are real, they happen, and a professional handles them without drama.

Then there's the murkier category — the claim that shows up three weeks after the job, the customer who decides their dead grass is your fault after a drought, the person who was already looking for a reason not to pay. These require a different kind of response.

And there are billing disputes — not damage at all, just a customer who thinks they were charged wrong, didn't understand the quote, or is unhappy with the quality of a cleanup job. These often get lumped in with damage claims but they have their own resolution path.

Knowing which type you're dealing with shapes everything that comes next. A legitimate small claim handled fast is a loyalty opportunity. A questionable claim handled badly becomes a one-star review.

• •Sprinkler heads, edging stakes, low-voltage lighting — most common physical damage
• •Turf damage from heavy equipment on wet ground
• •Trimmer damage to garden beds, downspouts, siding
• •Quality disputes — 'this isn't what I expected' or 'you missed a section'
• •Billing confusion — quote vs. invoice mismatch, unexpected charges
• •Pre-existing damage the customer didn't notice until after your visit

The Mistake That Turns a $75 Problem Into a $750 Problem

Here's the scenario that plays out more than it should: a customer reports a broken sprinkler head. The operator gets defensive, says the crew didn't do it, goes back and forth over text for a week, never resolves it, the customer disputes the invoice with their credit card company, and now the operator is dealing with a chargeback, a potential negative review, and a lost customer — over a $75 part.

The cost of that broken sprinkler head was never really $75. It was the hour of back-and-forth texts, the mental energy, the chargeback fee, and the customer's lifetime value walking out the door.

The smarter move — even when you're not sure the claim is legitimate — is to have a clear, calm response protocol that doesn't start with 'my crew didn't do that.' That instinct to defend is natural, but it's almost always the wrong first move. It signals that you're not listening, and it escalates instead of resolving.

Before we get into the process, ask yourself one honest question: do you have any documentation from that job? Photos, timestamps, a completed checklist? If the answer is no, you're negotiating blind every single time a dispute comes up. That's a fixable problem — how your crew documents jobs in the field can mean the difference between a he-said-she-said and a clear record.

A Simple Dispute Protocol That Actually Works

The goal of a good dispute protocol is simple: resolve it faster than the customer expects, at a cost you can control, without making it personal. Here's what that looks like in practice.

Step 1: Acknowledge first, investigate second. When a claim comes in, your first response should be acknowledgment — not admission. 'Thank you for letting me know. I want to look into this right away.' That's it. Don't defend, don't deflect. Just acknowledge. This single step defuses most situations before they escalate.

Step 2: Pull your documentation. Check your job photos, crew check-in timestamps, any notes from that visit. If you have photos of the property before the job started, pull those. This is where operators with good field documentation have a massive advantage over those who run on verbal agreements and memory.

Step 3: Assess the claim honestly. Did your crew do it? Probably? Possibly? No way? Your response should match your honest assessment. If it's clearly your crew's fault, own it fast and fix it. If it's genuinely unclear, say so professionally and offer to meet in the middle. If it's clearly pre-existing damage, explain that calmly with your documentation.

Step 4: Offer a resolution with options. Give the customer something to choose between — a credit toward their next invoice, a repair, a partial refund. Giving choices makes people feel heard. Dictating a resolution makes them dig in.

• •Respond within 2 hours — not two days
• •Never negotiate over text when a phone call would resolve it faster
• •Document the resolution in writing after the call
• •Close the loop — confirm the customer is satisfied before marking resolved

Documentation Is Your Defense — Set It Up Before You Need It

The single best thing you can do to prevent disputes from becoming expensive is to have job-level documentation built into your standard workflow — not as an afterthought when something goes wrong, but as a routine your crew does on every single job.

That means photos before and after, especially on first visits and on properties where pre-existing conditions exist (cracked edging, old sprinkler heads, worn fencing). It means timestamped check-ins so you know exactly when your crew was on-site. It means checklists your crew completes before they leave.

This isn't about not trusting your crew. It's about being able to tell a clear story when a customer asks. A photo of the sprinkler head intact at 9:14am, taken before the job started, is worth more than anything you can say in a dispute conversation.

The crew field app in Lawnager handles this as part of the job flow — crews check in, complete a checklist, attach photos, and check out with GPS timestamps. It's not extra work for a well-run crew; it becomes the routine. And it means when a dispute shows up two weeks after a job, you're not negotiating from memory.

Credits vs. Refunds: Knowing Which to Offer (And When)

When you decide to compensate a customer, you have two main tools: a credit on their account (applied to a future invoice) or an actual refund of money they've already paid. Which one you offer matters more than most operators realize.

Credits keep revenue in the business and keep the customer coming back. A $50 credit toward next month's service costs you less than a $50 refund and creates a reason for the customer to stay. For small claims from long-standing customers, a credit is almost always the right move. It communicates 'I value this relationship' without setting a precedent that you cut checks every time someone complains.

Refunds are appropriate when the customer paid and the outcome was clearly below the standard you promised — a no-show, a botched job you can't fix, a charge error. Issuing a refund quickly in those situations is actually cheaper than the chargeback and bad review that come when you drag your feet.

Lawnager handles both via the disputes and refunds workflow — you can issue a credit to the customer's account or process a Stripe refund directly. Here's how that works in the platform. The key is having that lever ready before a dispute lands, not scrambling to figure out how to send money back while a customer is waiting.

For quality disputes that don't involve damage — a customer who's unhappy with a cleanup job, for example — consider offering to come back and make it right before offering money. Most customers actually prefer the work done correctly over a partial refund. The re-do costs you time, but it costs the customer nothing and builds more trust than a check.

• •Credit: best for small claims, loyal customers, and 'I want to keep this relationship' situations
• •Refund: best for clear billing errors, no-shows, or jobs that were genuinely not delivered
• •Re-do the work: best for quality complaints where the issue is fixable
• •Partial credit + apology: effective middle ground for ambiguous claims

Setting Expectations Before a Dispute Happens

The best dispute resolution is the one you never have to have. A lot of claims and billing confusion come down to expectations that were never set clearly — a customer who didn't know what was included, who assumed something would be fixed that wasn't in scope, or who didn't read the quote before accepting it.

A few habits that prevent this:

Make your quotes specific. Vague quotes like 'lawn maintenance — $65' invite disputes. Itemized quotes that say 'mow, edge, blow, trim around flower beds — excludes weed removal' leave no room for 'I thought that was included.' The AI quoting guide covers how to build clean, detailed quotes that protect you as much as they sell the job.

Send a completion notification with photos. When a customer gets an automatic message after their visit that says 'your job is complete' with a photo attached, they're looking at your work the same day it was done. If something's wrong, they'll tell you now — not three weeks later when both of you have forgotten the details.

For commercial accounts especially, where the stakes per invoice are higher and the relationship is more formal, clear scope documentation is non-negotiable. Landing a commercial account unprepared is one of the fastest ways to find yourself in a billing dispute you can't easily resolve.

When to Let a Customer Go

Not every dispute is worth resolving. Some customers are chronically unhappy, dispute every third invoice, and cost you more in time and stress than they'll ever pay you in revenue. Recognizing when you're dealing with one of those customers — and making a clean exit — is a legitimate business decision.

The rule of thumb: if a customer has disputed more than once, if the claims never seem to match the documentation, or if they're consistently slow to pay AND quick to complain, do the math on what that account is actually worth. Factor in the admin time, the credit you've issued, the mental load of the relationship. That $200/month account that requires $50 worth of dispute management every other month isn't a $200 account.

If you decide to part ways, do it professionally. Finish the current billing cycle, send a clean final invoice, and let them know you're no longer able to service them. Don't explain in detail. Don't get into the history. Keep it short and professional — 'We won't be able to continue service after [date]. Thank you for being a customer.' That's it.

The customers worth keeping are the ones who communicate problems calmly, pay consistently, and respond well when you make things right. If you want more of those customers and fewer of the others, a referral program built around your best accounts tends to attract more of the same — good customers refer good customers.

• •Red flag: dispute on first or second invoice
• •Red flag: claims that don't match your documentation
• •Red flag: slow pay + high-maintenance communication pattern
• •Red flag: escalating to social media or credit card disputes without contacting you first
• •Green flag: customer who flags an issue calmly and accepts a fair resolution