The customer in front of you belongs to another rep
When the customer in front of you already belongs to another salesperson, most systems either block the record or quietly let you create a duplicate. bkd.ai does neither. You see enough to confirm it is the same person, request them in one click, and the rep who owns them gets a text to approve or deny.
Why do dealerships fight over lead ownership?
Because ownership is decided once, quietly, by whoever submitted first, and then it is invisible to everyone else. The rep standing at the desk with a live customer has no idea the record exists until they try to create it. What they hit is an error, and an error is not an answer.
From there it goes one of two ways, and both are bad. The rep gives up and makes a duplicate, so now the store has two records, two follow-up cadences and two people texting the same customer. Or the rep goes looking for a manager, and the customer waits while the store works out whose name is on the file.
The customer notices. They came in to buy a car and they are watching a dealership argue about who gets credit for them.
What should happen when you add a customer who already exists?
Three things, in this order. The rep should be told it is a duplicate before they finish typing. They should see enough to confirm it is genuinely the same person. And they should have one obvious action that resolves it, without leaving the screen or finding a manager.
What they should not see is the other rep's file. Notes, full contact details and deal history belong to the person who owns the record. Confirming a match needs far less than that, and handing over the whole file to settle a duplicate is how a store ends up with reps quietly working each other's pipelines.
How does a claim request work in bkd.ai?
When you add a contact whose number already belongs to someone else, bkd.ai shows a limited-info match: the name, the last four digits of the phone, the vehicle of interest and who owns them. Enough to know, not enough to poach. From there you request the contact in one click and add a note about why.
The owning rep is texted straight away and sees the pending request on the contact record and in their daily view, with approve and deny right there. If they approve, the contact moves and you are told. If they deny, you are told that too. A contact can have more than one request pending, so a busy walk-in does not create a traffic jam.
The point is that somebody answers. The worst outcome is not losing the claim. It is the customer standing there while nothing happens.
Who should decide, the rep or the manager?
The rep who owns the contact decides first, because they are the one who knows whether there is a live conversation behind the record. A record that was worked yesterday is different from one that has been dormant since spring, and no rule about lead age can see that difference.
Managers still need visibility, which is why every request and every decision is written down on the contact. The store gets a record of who asked, who answered and what they said, instead of a hallway conversation nobody can reconstruct a month later.
Frequently asked questions
What happens when two salespeople claim the same customer?
In bkd.ai the second rep sees a limited-info match and requests the contact instead of creating a duplicate. The rep who owns the record is texted and approves or denies from the contact or their daily view. Both outcomes are recorded on the contact, so the decision is traceable.
Should a salesperson see another rep's contact record?
No. Confirming a duplicate only requires the name, the last four digits of the phone, the vehicle of interest and the owning rep. Notes, full contact details and deal history stay with the owner. bkd.ai deliberately limits what the requesting rep can see.
How do you stop duplicate contacts in a dealership?
Catch the duplicate at the moment of entry rather than cleaning it up later. bkd.ai flags the match while the rep is still adding the contact and gives them a claim request as the obvious next action, so the store never accumulates two records and two follow-up cadences for one customer.