Reading a Thumbtack Lead Before You Pay for It

Most advice about bad Thumbtack leads assumes you get a moment to inspect one and decline it. On a direct lead you usually don't. When a customer reaches out and the request matches the targeting you already set, the charge lands — there is no approve step in between. The decision was made weeks earlier, in your settings.

So reading a lead well is three separate skills: knowing which charges you can still stop, checking the handful of fields that decide whether a charge is contestable, and telling a defective lead apart from an ordinary customer who simply didn't hire you.

Thumbtack sends you more than one kind of work, and they bill differently. A direct lead is the customer contacting you first; if it matches your preferences you pay automatically, at the price you set for that service. Reading it before paying is not on the table.

Opportunities are the exception. You see the cost up front, and you're only charged if you reach out and the customer responds to your message. That is a genuine decision point — the one place where reading the request carefully directly saves money. Instant Book charges work differently again, keyed to the availability and services you published rather than to a conversation.

The practical upshot: on an Opportunity, read everything before you message. On a direct lead, the reading you do is about what happens next, not about whether to pay.

Thumbtack's refund request form asks you to pick a reason: Location, Timing, Job type, Charged twice, Phone disconnected, or "Reason not listed." Four of the five things worth checking on arrival map straight onto that list, which is why the check takes a minute and pays for itself.

First, location — the zip or address against the service area on your profile. It is factual and checkable, and it is the cleanest kind of dispute to write. Second, category against actual scope: the request came in under one of your services, but the description is work you don't do. Miscategorised requests are common and they map to Job type.

Third, timing — the date the customer wants against the availability you set. Fourth, the phone number: call it early, because a number that returns "not in service" is its own named reason and needs almost no argument. Fifth, size. A job under your minimum isn't a refund reason at all; it's a targeting setting you haven't tightened. Noting it still matters, because that's the fix.

Targeting is where you decide, in advance, which leads are allowed to charge you: service area, the job types you want, timing, a minimum project value, a max lead price per service, and a weekly budget. Thumbtack's position is that it doesn't charge for leads outside the parameters you set — which is precisely why mismatches are worth contesting. The charge contradicts your own configuration, and that's an argument about a record, not about your opinion of the customer.

Prices move with job type and size, how dense your market is, and how many pros are competing, so the same targeting mistake costs very different amounts depending on where it happens. Reported lead prices run from roughly $8 on a small cleaning job to $150 or more on a large remodel or HVAC install. A stale service radius in a cheap category is an annoyance; the same error in your most expensive one is a standing monthly bill.

Audit the settings on a schedule rather than after a bad week. A radius you set when you had a second van, or a job type you added to test and never removed, will keep billing you quietly for as long as you leave it.

Because you're already charged, triage is not about whether to respond. Respond fast either way — on a shared lead, speed is most of what decides who gets the job. Reading for intent tells you how much time to invest after that first reply, not whether to send it.

The signals are ordinary ones. A request with a specific address, a date, and a described scope is a different customer from a two-line inquiry sent through a bulk "get quotes" flow by someone who never opened your profile. The first deserves a call and a real quote; the second deserves a fast message and a follow-up sequence you don't hand-write.

Low intent is not a lead defect. A customer who was pricing a job for spring, hired their neighbour's guy, or simply stopped replying is the normal distribution of a shared-lead marketplace. Filing those as defects clutters your history and makes it harder to be taken seriously on the cases where a named reason genuinely fits.

Screenshot the lead as it arrived, before the thread grows and the details get edited or buried. If you call, note the time; if you text, keep the timestamps visible. This takes seconds at the moment and is nearly impossible to reconstruct three weeks later.

If one of the named reasons already fits on arrival, file it the same day. Refund requests have to be submitted within 45 days of the charge, and the window closes without a warning — busy months are exactly when a bad charge sits unnoticed until it's too late to contest.

One detail worth knowing before you file: an approved refund posts to your Thumbtack balance as credit by default. If you want the money back on your card instead, that has to be requested within 10 business days of approval.

You cannot inspect a direct lead before paying for it, so put the effort where it still moves money: targeting settings that decide what can charge you, a one-minute check on arrival against location, category, timing, phone and size, and a fast reply regardless of what you find.

When that check turns up a real mismatch, file it while the evidence is fresh. RefundMyLead takes what you already have — the lead screenshot, the message thread, the call log — identifies which of Thumbtack's reasons your facts actually support, and writes the request in the structure its reviewers read.