How Do You Handle Duplicate Leads From Angi, Thumbtack, and Your Website?

Match new leads against existing ones by phone number, email, and street address first, then by name similarity as a backup check. Whichever platform the homeowner contacted first becomes the source of truth — that's the thread you reply from. Every later submission from the same person gets merged into it silently, so only one person on your team ever reaches out.

If you've never built that logic into your process, you've probably lived the alternative: a homeowner fills out your Angi profile at 7:40pm, then — because Angi hasn't called them back yet — tries Thumbtack at 7:52, then finds your website and fills out the contact form at 8:05 out of pure anxiety. Three leads, one job. If your office manager replies to the Angi lead and your partner replies to the website form without talking to each other, the homeowner gets two different availability windows and possibly two different ballpark prices in the same hour. That's not a minor annoyance — it reads as disorganized to the one person deciding whether to trust you with their house.

{"h2":"Why one homeowner hits three platforms the same night"}

Homeowners shopping for a fence, a roof repair, or an interior paint job rarely wait around for one response before trying somewhere else. Angi and Thumbtack both train users to expect fast replies, so when nobody answers inside 15-20 minutes, the homeowner assumes the lead got lost and starts over somewhere else. Add a website contact form into the mix — especially if it's slow to respond or routes to a generic inbox — and you've got three parallel conversations starting with three different timestamps, phrased slightly differently each time ("need a quote for a wood fence," "fence install, 120 ft," "looking for fence pricing"), which is exactly why naive keyword matching misses most duplicates.

{"h2":"What matching actually has to check"}

A duplicate-detection system that only checks exact phone number matches will miss a lot. Homeowners frequently use a cell number on one platform and a landline or spouse's number on another, or they'll leave the phone field blank on a form and only give an email. The matching needs multiple signals working together:

• Phone number, normalized (strip formatting, compare last 10 digits)
• Email address, exact or close variant (gmail dot-aliasing, common typos)
• Street address — this is often the strongest signal since two people rarely submit the same address by coincidence
• Name similarity as a tiebreaker, not a primary match, since common names create false positives on their own

When two or three of those line up, it's safe to treat the new submission as the same person and merge it rather than creating a second lead card. When only one weak signal matches (say, just a shared last name), it should flag for a human to glance at rather than auto-merging, because false merges are worse than duplicates — they can bury a second, unrelated job under the wrong customer record.

{"h2":"Decide the source-of-truth rule before you need it"}

The practical rule that works for most shops: whichever platform the customer reached first owns the conversation. If Angi came in at 7:40 and the website form came in at 8:05, the Angi message is the one you reply to, and the website submission gets logged as a duplicate note on that same lead rather than opening a second thread. This matters for two reasons. First, it avoids the two-different-answers problem above. Second, it keeps your source-of-truth clean when you're later trying to figure out which lead channels are actually converting — if duplicates aren't merged, you'll overcount leads from whichever platform happens to be slowest to respond, since slow response is exactly what pushes a homeowner to try a second platform.

One exception worth building in: if the first platform is a paid-per-lead source like Angi or HomeAdvisor and the duplicate came in organically through your own website, some contractors still want visibility into both so they can see how much revenue their website is generating independent of what they're paying per lead for marketplace traffic. The merge should still happen for response purposes, but the lead source data is worth keeping intact underneath it.

{"h2":"The cost of getting this wrong"}

Beyond the awkward double-reply, duplicate leads waste real time. If every Angi, Thumbtack, and website lead lands as a separate card in your pipeline, you're estimating job volume, close rate, and lead cost on inflated numbers — a shop that actually gets 40 unique leads a month might be looking at a spreadsheet showing 55 and wondering why its close rate looks so bad. It also wastes crew time: more than one contractor has sent two different guys to do a walkthrough for the same job because nobody noticed the lead had already been assigned.

{"h2":"How Trusso handles it"}

Trusso pulls leads from Angi, Thumbtack, Yelp, Google Local Services, HomeAdvisor, and your website contact form into one inbox, whether that's through a connected Gmail or Outlook account or a forwarding address you set up once. An AI layer reads each incoming message and pulls out the customer's name, job description, photos, budget, and urgency automatically, then checks it against existing leads using email, phone, address, and name similarity before deciding whether it's a new lead or a duplicate of one already in your pipeline. You can read the full breakdown of how the import and matching works on the lead capture page.

When it's a genuine duplicate, Trusso merges it into the existing lead instead of creating a second card, so only one conversation moves forward and nobody on your team accidentally replies twice with conflicting information. Replies go out by email or text depending on how the lead came in, and they respect marketplace relay addresses so a reply to an Angi lead actually reaches the homeowner through Angi's system rather than bouncing. If you're still manually checking four separate inboxes for new leads, turning multi-platform leads into booked jobs is worth reading alongside this, and if your bigger problem is response speed rather than duplicates specifically, see how to respond to leads from Angi, Thumbtack, and Yelp.