Refund Policy for Water Damage Leads: How “Invalids Removed Before Invoice” Protects Your ROI
A clear quality policy turns pay‑per‑call from gambling into a predictable channel. For a practical example, review Real Time Lead Gen’s water damage leads program.
1) Why a Written Policy Matters
In restoration, speed and clarity win. That includes clarity about what you pay for. A written refund/credit policy prevents gray‑area disputes, protects cash flow, and aligns your team with your provider. The simplest, fairest standard in pay‑per‑call is removal of invalids before invoice—you never front the cost for non‑opportunities.
2) Define “Invalid” in Plain English
Wrong service: The caller needs a service you don’t offer (e.g., roof replacement instead of water mitigation).
Out of area: The address is outside your serviceable ZIPs.
Duplicate: Same caller and job within the policy window.
Spam/solicitation: Telemarketers, job seekers, vendors, or obvious bots.
Each item needs examples so reviewers can decide quickly and consistently. Add a short appendix with edge cases—e.g., “sewage backup” may be valid if you do mitigation, but not if you only handle clean water incidents.
3) Evidence Rules (Make Decisions Easy)
Decisions should rely on call recordings and routing metadata (source, timestamp, dialed number, geo filters). If a call clearly states an invalid reason—“I’m in {{Out‑of‑Area ZIP}},” or “I need roof tarping only”—that’s enough. Your team should never be asked to pay for calls that fail the provider’s own criteria.
4) Submission & Review Workflow
Flag the call within the stated window (e.g., 3 business days) and provide the reason.
Provider review pulls the recording and metadata, compares to definitions, and rules valid/invalid.
Outcome is recorded in your statement: confirmed invalids are removed before invoice.
Keep the process simple. The faster the loop, the more trust on both sides.
5) Edge Cases (How to Decide)
No answer / voicemail only: Not invalid by itself—fix routing and staffing. If the call is truly outside hours and no rotation is set, consider a short grace policy while you stabilize staffing.
Can’t reach the caller again: If the first call was clearly valid, it’s billable. Tighten your immediate call‑back process and confirm SMS reachability.
Call transferred to a partner: If the job fits your filters but you subcontract, it’s still valid; review your service filters if that’s frequent.
Insurance Q only: If the caller only wanted coverage info but has an active leak, treat as valid—your script should guide them to dispatch.
6) Publish the Policy (Trust Signal)
Putting your definitions and timelines on a public page is a conversion asset. It sets expectations and shows you’re confident in quality. Keep the language human; avoid legalese.
7) Metrics to Watch
Metric
What it tells you
How to use it
Refund/credit rate
Targeting & filter alignment
Rising rate = adjust filters or source mix.
Time to review
Operational friction
Keep it under 3 business days.
Dispute acceptance rate
Policy calibration
Low acceptance may signal unclear definitions.
8) Sample “Invalids Removed Before Invoice” Language
Quality Policy: You’re billed for legitimate restoration opportunities only. We define invalid calls as: (1) wrong service; (2) out of area; (3) duplicate within 14 days; (4) spam/solicitation. Provide the call time and reason within 3 business days; we’ll verify against recordings and remove qualified invalids before invoice.
9) Implementation Checklist
Write one page of definitions with 2–3 examples each.
Set your submission window and review turnaround time.
Align geo and service filters with crew capacity; revisit monthly.
Enable call recording and surface key metadata on your statements.
Train your dispatchers on the policy so they flag issues correctly.
10) Keep It Fair (Both Directions)
Quality policies shouldn’t be a game of “gotcha.” You want long‑term partners. Be consistent, keep evidence organized, and hold yourselves to the same speed‑to‑voice standards you expect from your provider. That shared responsibility is what keeps ROI stable across seasons.
FAQs
How long does a refund review take?
One to three business days is typical when recordings and metadata are available.
Do I pay for invalid calls?
Under a removal‑before‑invoice policy, confirmed invalids are excluded from the invoice—no upfront cost.
Can the policy be abused?
Clear definitions and recordings minimize abuse. Transparency benefits both parties and speeds resolutions.
What if my refund rate spikes?
First, examine geo/service filters and staffing. Spikes often indicate mis‑targeting or answer‑time issues, not provider failure.
P.S. We built our systems around one promise: We’ll Make Your Phone Ring!
