One customer, one thread: how Dealerloop stops one buyer from becoming three leads

A buyer emails about a car on Tuesday night. On Wednesday they send a text from their mobile. By Thursday they have filled in a web form too. To most systems, that is three separate leads. Three records, three cold starts, three people on your floor picking up a conversation that has no memory of what came before.

The customer does not see it that way. In their head, they have been talking to your dealership the whole time. When your next reply asks a question they already answered two days ago, the relationship starts to feel careless before anyone has quoted a price.

That gap between how the customer sees the conversation and how the software sees it is exactly what "One customer, one thread" is built to close.

The problem: one buyer wearing three disguises

Enquiries arrive on different channels, and each channel likes to think it owns the customer. Email lands in one place, SMS in another, the web form somewhere else again. Without a way to tie them together, the same buyer looks like three different leads.

The result is three disjointed conversations. Nobody has the full picture, so the customer gets asked the same things twice, follow-up doubles up or contradicts itself, and the person who was genuinely ready to buy slips into the pile of leads that only ever got half a reply.

This is the flip side of getting every lead source through one front door. Capturing the enquiries is step one. Matching them to the right human is what makes the capture worth anything.

How it works: matching across channels, not just within them

The first job is the phone number, because that is where most duplication hides. Dealerloop normalises phone numbers to a single Australian format before matching. So 0412..., +61412... and the spaced-out variants people type all resolve to the same person, rather than spawning a fresh record every time the format changes.

From there, an inbound text or email is matched to the customer's open lead across channels, not just within the channel it arrived on. The text that follows Tuesday's email joins Tuesday's conversation. It does not start a second one.

And because the match holds, the full conversation history rides along with it. The AI never re-asks what the customer already told you somewhere else. What they said by email is known when they text, and the other way around.

What it means on the floor

Day to day, this is the difference between a relationship and a stack of tickets. When a customer switches from email to SMS mid-decision, your team is not scrambling to work out whether this is a new lead or an old one. It is the same thread, already carrying everything that has been said.

The conversation reads like one relationship, which is what the customer thinks is happening anyway. No repeated questions, no contradicting follow-up, no sense that the left hand has never met the right.

It also protects the leads you would otherwise lose to the cracks. A buyer who feels remembered is far less likely to become one of the ones that got away, and far more likely to still be talking to you when the right car is ready.

One customer, one thread is one piece of everything Dealerloop does to keep enquiries from leaking. If your CRM currently treats a single buyer as three, book a demo and we will show you what one thread looks like on real channels.