Thumbtack's 45-Day Refund Window: What Happens If You Miss It

Every Thumbtack refund story has two deadlines, and pros only ever remember one of them. The reasons — wrong service area, an unresponsive customer, a fake request — get all the attention. The clock rarely does. But there is a hard 45-day limit on when you can even ask, counted from the day you were charged, and it does not care how airtight your case is. Miss it and a lead you had every right to dispute becomes money you simply eat. Here is exactly how the window works, why it is so easy to blow past, and the small habit that closes the gap for good.

For most situations, Thumbtack lets you request a refund within 45 days of the charge. Submit inside that window and support reviews the details and tells you whether your situation qualifies. Submit outside it and one of the most common denial reasons kicks in automatically: the request came in after 45 days from the charge. It does not matter that the customer never answered or that the lead was clearly spam — the door is simply closed.

Two things about that clock are worth burning into memory. First, it starts at the charge date, not the day you realized the lead was bad or the day the customer went quiet. Second, refunds are granted at Thumbtack's sole discretion even when you are inside the window — so the deadline is the floor, not a guarantee. Being on time does not win the dispute; being late guarantees you lose it before anyone reads a word.

The 45-day limit rarely trips up disorganized contractors. It trips up busy ones. A bad lead almost never announces itself with a moment that forces you to act. A customer goes quiet, a request turns out to be a tire-kicker, a job lands two towns over — and instead of dealing with it, you move on to the leads that might actually pay. That is the right instinct for running a business and the exact instinct that lets a refund quietly expire.

The problem is that nothing about a dead lead has urgency. There is no invoice due, no customer chasing you, no calendar reminder. Weeks pass, the lead fades from memory, and by the time you sit down to clean up your Thumbtack spending, the charge is 50 days old and there is nothing to recover. Pros do not miss the window because they do not care — they miss it because the window is silent and the rest of the job is loud.

A single expired dispute feels small — one $40 lead, one $90 lead. But the cost is not one lead; it is the pattern. If you let two or three disputable leads slip past 45 days every month because you never got around to them, that is easily a few hundred dollars a quarter in refunds you were owed and never claimed. On thin contractor margins, that is real money walking out the door on a technicality.

It also quietly distorts the number that actually tells you whether Thumbtack is working: your cost per booked job. Every dead lead you fail to recover stays in the denominator, inflating what each real job effectively cost you. Disputing in time does not just get your money back — it keeps your own performance math honest, so you are deciding whether to keep spending on the platform based on the jobs you won, not the leads you got stuck paying for.

The fix is almost boringly simple: the moment a lead looks even slightly disputable, write it down. Note the customer, the charge date, and one line on why — "out of area," "never replied," "just price-shopping." A sticky note, a phone note, a spreadsheet, whatever you will actually see. The point is to convert a vague memory that will fade into a dated record that forces the deadline into view while there is still plenty of runway.

Do this the day it happens, not the day you decide to dispute. Logging on the spot costs thirty seconds and captures the detail — the exact charge date, the customer's wording — that is impossible to reconstruct three weeks later. If the customer resurfaces and books, you cross the line out and move on. If they do not, you have a clean, timestamped case sitting ready well before day 45, instead of a frantic scramble on day 44 to remember what even happened.

Logging the lead is step one; capturing the proof is step two, and the same "do it now" logic applies. When a call goes unanswered, screenshot the call log. When a text sits unread, screenshot the thread. When the customer admits they were gathering ten quotes, screenshot that exact message. You are not committing to a dispute by doing this — you are just refusing to let the evidence evaporate the way the memory will.

The reward is that the case builds itself in the background. By the time you decide to file, the charge date is logged, the screenshots are saved, and you are comfortably inside the 45 days. Compare that to the alternative: opening Thumbtack on day 40, half-remembering a bad lead, and having no proof and no time to gather it. One approach recovers the money; the other explains, after the fact, why you did not.

Thumbtack's 45-day window is unforgiving precisely because it is quiet — there is no alarm, just a deadline that passes while you are busy running your business. The valid disputes you lose to the clock are pure, avoidable waste. Log every questionable lead the day it happens with its charge date, screenshot the proof while it is fresh, and file well before the deadline instead of racing it.

RefundMyLead is built to keep that runway on your side. It matches each logged lead to the correct approved refund reason and writes the dispute in the structure Thumbtack support actually approves — so once you have captured the lead in time, turning it into a filed, well-evidenced request takes minutes, not the hours you never have before day 45.