How Thumbtack's Trust & Safety Team Differs From the Refund Disputes Team

When a lead goes wrong on Thumbtack, most pros do one thing: fire off a refund request and wait. That works for the majority of cases, but it quietly misroutes an entire category of them. Thumbtack does not run one bad-lead process — it runs two, staffed by different teams, triggered in different ways, judged against different standards. The refunds team reviews requests lead by lead. The Trust & Safety team detects spam and fraud across the platform and can refund leads without you asking at all. Knowing which one owns your situation is the difference between a credit that lands and a 45-day window that expires while you re-explain yourself to the wrong inbox.

Trust & Safety exists to keep fake demand off the platform. Their job is not your individual charge — it is the account, the number, the script behind it. They look at signals no single pro can see: the same phone prefix generating requests in six metros, a customer account created minutes before it fired off twenty requests, wording repeated verbatim across categories.

Because they operate on patterns, their output is proactive. When a lead gets flagged as spam or fraudulent by Trust & Safety, Thumbtack can refund it automatically — the amount appears back in your Thumbtack balance with no request from you. That is why pros occasionally see a credit they never filed for. It also means one report from you can clear charges for every pro that bogus account touched, not just yours.

The refunds team does the opposite work. They evaluate one lead, one charge, one set of facts, against the list of approved refund reasons — wrong service area, customer never responds, fake or low-intent request, job already hired out, budget nowhere near your minimum, service you do not offer. They are not looking for a network of fraud. They are looking for whether your case matches a reason and whether you documented it.

This path is entirely request-driven. Nothing happens until you file, you generally have 45 days from the charge date to do it, and approval is at Thumbtack's discretion. Pros can escalate to refunddisputes@thumbtack.com. Approved refunds typically land as Thumbtack credit, and where a cash refund applies, expect roughly five to seven business days to reach the bank.

Sort by what went wrong, not by how annoyed you are. If the customer was never real — dead number, template wording, a cluster of near-identical requests, someone impersonating a homeowner, an obvious scam script — that is Trust & Safety territory, because the value of the information is in the pattern.

If the customer was real but the lead was worthless to you — they live 40 miles outside your radius, they wanted electrical and you do drywall, their budget is a third of your minimum, they ghosted after three documented attempts, they had already hired someone — that is a refund dispute. There is no fraud ring to detect. There is a factual mismatch to prove, and the refunds team is the only team that adjudicates it.

These are not competing options, and spam is the case where running both is correct. Report the lead so Trust & Safety can act on the account upstream, and file the refund request so your specific charge has a case on the record inside the window. Reporting alone does not guarantee your charge gets reversed; detection is imperfect and plenty of spam gets billed before anything flags it.

Order matters less than coverage. What you cannot afford is assuming the report handled the money. Pros who report a scam lead, get no auto-credit, and only circle back weeks later sometimes find the 45 days gone — the case was strong and the clock was not.

Write to the standard the reader applies. A Trust & Safety report should emphasize repeatability: the identical phrasing across separate leads, the phone numbers differing by one digit, the timing cluster, the customer account details. You are handing them a thread to pull, so more leads in the report is better than fewer.

A refund dispute wants the opposite discipline — one lead, one reason named upfront, two or three factual sentences, and evidence that maps directly to it. Timestamped call logs and message screenshots for an unresponsive customer. The lead's zip beside your configured radius for a service-area mismatch. The customer's own words for a low-intent request. Suspicion is useful to Trust & Safety; only documentation moves the refunds team.

There is a tempting shortcut when both feel slow: dispute the charge with your bank. Do not. A chargeback bypasses both teams and puts your account in violation of Thumbtack's terms, with permanent deactivation — and the review history attached to it — as a realistic outcome. You may win $60 and lose the profile you spent years building.

Both internal paths are slower than a chargeback and both are recoverable. Exhaust them first, and escalate to refunddisputes@thumbtack.com if a request comes back with a form denial that does not address your evidence.

Trust & Safety catches fake demand at the platform level and can credit you without a request; the refunds team adjudicates your individual charge against the approved reasons and does nothing until you file. Fake customer, report it — and dispute it too. Real customer, wrong fit, file the dispute with documentation. Either way the 45-day clock is yours to manage, and a report is never a substitute for a request.

RefundMyLead handles the second half of that split. Upload your screenshots or a call recording and it matches the lead to the correct approved reason and writes the dispute in the structure Thumbtack support actually reads — so the leads that got past Trust & Safety do not get to keep your money either.