What Evidence Actually Gets a Thumbtack Dispute Approved (Real Examples)

Every pro who has filed a few Thumbtack refund requests learns the same thing: the reason is rarely what loses the case. The lead really was fake, the customer really had already hired someone, — and the denial came back anyway. What lost it is that you told support all of that instead of showing it. A reviewer working a queue cannot verify your memory, only what is on screen. Here is what a complete evidence package looks like for the three reasons hardest to document.

First, the standard. A useful attachment answers three questions at a glance: which lead is this, when did it happen, and what does it prove? Miss one and it is decoration: a text thread with no visible date does not establish that the customer was booked before you got charged, and a call log with no name does not connect to the lead in question.

So build every attachment to carry all three: full screens rather than tight crops, timestamps in frame, and the lead name or request title in the same image as the proof. One claim per screenshot, in the order your letter states them.

This is the hardest reason to win because your honest experience of it — no real person was ever on the other end — is an absence, and absences do not screenshot. You have to convert it into positive artifacts, and a verifiable package usually has three pieces.

First, the original request showing the generic or impossible details: no address, no timeline, no scope, or a name and a project that do not fit together. Second, proof the contact path is dead — a call screen reading "number disconnected" or a connection that failed at zero seconds, plus a text thread with a delivery failure. Third, and most persuasive when you have it, a second lead: two requests with wording repeated close to verbatim, side by side, dated. One suspicious lead is your judgment call. Two matching ones are a pattern, and a pattern is evidence.

Here the entire case is one comparison, and most pros submit half of it. They attach the customer's message — "sorry, we already went with someone last week" — and stop. That proves the customer is booked now. It does not prove they were booked before Thumbtack charged you, which is the actual claim.

The winning package puts both dates in front of the reviewer. Attachment one: the message with its timestamp visible, and ideally the customer's own words about when they hired — "last week," "Tuesday," "before you messaged." Attachment two: your charges screen showing the date and amount for that lead. Then state the comparison in the letter rather than leaving it to be inferred — charged on the 14th, customer says they hired on the 9th. That is an argument a reviewer can confirm in seconds, and confirmable is the whole game.

Unresponsive leads feel like the simplest reason and get denied constantly, because "I reached out and heard nothing" and "I sent one message and moved on" produce identical paperwork. What separates them is documented cadence: several attempts, across channels, spread over days.

A package that holds up is three or four attachments in sequence — the in-app thread showing your opening reply with its timestamp and nothing beneath it, a call log entry or two with dates and short durations, and a text thread from a later day. Three attempts across roughly a week is a reasonable bar. Order the letter to mirror the attachments so the reviewer is reading a timeline, not assembling one.

The first is cropping: zooming in on the customer's sentence and cutting the date turns proof into a quote. The second is summarizing instead of attaching. The third is stacking reasons — leading with an unresponsive customer, then adding that the budget was low and the area was far, which reads as searching for something that sticks. Pick the strongest reason and prove that one.

The fourth is waiting. Screenshots are easy the day it happens and harder every week after — threads scroll, call logs roll off the phone. And the clock is real: you generally have 45 days from the charge date to request a refund, so a case you meant to document eventually is a case that expires.

When a lead looks wrong, screenshot the request that day. When a customer mentions already hiring, a budget, or a service you do not offer, screenshot it before you reply. One folder per lead and the package assembles itself.

None of this makes approval certain — refunds stay at Thumbtack's sole discretion, and refunddisputes@thumbtack.com is where you escalate a denial that never addressed what you sent. But a dispute where every claim points at a dated attachment is a different document from the one most pros file.

Reasons get you into the queue; evidence gets you the credit. Show which lead, show when, show the claim. Convert fake leads into artifacts and patterns, prove "already hired" by putting the hire date beside the charge date, and prove silence with a documented cadence.

RefundMyLead is built for this step. Upload the screenshots or call recording you captured and it identifies the strongest approved reason, states the comparison the reviewer needs, and writes the dispute in the structure Thumbtack support actually reads.