Lead Replacement Review: What Happens to a Bad Lead

Every lead in your zone is delivered, so some will be wrong numbers, test entries or people who deny ever asking. This is the path a bad lead takes from the moment a salesperson flags it.

Lead replacement review is the post delivery process where a dealership reports a lead that was never workable, our Quality Control team reviews the report against the lead record, and an approved report marks the lead Bad Lead and sends it into replacement review. That is the whole mechanism, and it sits inside the LeadLocate CRM rather than in an email thread with an account manager.

It exists because of a decision made on purpose. We ask pre-screening questions at capture and then deliver every submitted lead in your zone, exclusively, without a scoring step or a quality filter in front of it. Nothing is held back, so the store sees the same leads we see, and the honest consequence is that a few of them will be a wrong number, a duplicate submission, a test entry from somebody checking a form, or a person who denies ever filling anything out. The what to expect from car sales leads page explains why most leads that look strange are still real buyers. Replacement review is for the ones that are not, and it handles them after the fact, with a record, instead of pretending a filter could have caught them in advance.

Picture a Tuesday afternoon. A rep has a lead from this morning, has called twice, texted once from the CRM inbox and sent an email. The number rings straight to a disconnected tone, the text shows Not delivered on the bubble, and the email address bounces. She opens the lead, and in the lead detail she clicks Report Lead To Quality Control. A short form asks for the reason for review. The prompt is specific: tell the Quality Control team why this lead should be reviewed as a bad lead, and explain which methods of communication were tried, such as phone calls, text messages and email. She types three lines, hits Submit Request, and goes back to her other leads.

That is the entire rep side of the process. Nobody has to find the account manager's email, screenshot the lead, or remember a support address. The request is filed from the lead it concerns, and it carries the lead data, the recent notes and the communications log with it, so the review starts with the evidence already attached. A rep who has really worked the lead has nothing to assemble; the CRM assembled it while she worked.

Leave your number and a lead specialist calls you back to answer your questions about pricing, coverage, and setup. Mon - Sat, 9:00 AM - 6:00 PM Pacific.

Prefer to talk right now? Call or text 844-376-2274.

The distinction matters because the review looks at the record, not at the rep's frustration. A bad lead is one that could not be worked: contact information that does not connect to anyone, a submission that was clearly a test, a duplicate of a lead you already received, or a customer who states they never submitted a request. Those are the cases the reason field is for, and the lead's own communications log usually confirms them in seconds.

A lead that is not a bad lead is a lead that is simply hard. A shopper with a small budget asking about an expensive truck is a real lead. A customer who wants to negotiate before they visit is a real lead. Someone who went quiet after one reply is a real lead that needs a follow up process, not a replacement request. The Mark Lead As Lost popup in the same lead detail exists for exactly that second category, with reasons like No Agreement Reached, Shopping Out of Area and Bought Different Brand Elsewhere, and the sibling page on lost reason tracking covers it. Keeping those two actions separate is what makes the replacement numbers honest: the lost reasons tell you about your process, the quality control requests tell you about the lead source.

Submitted requests land on the Quality Control Requests page, where each one shows the company, who requested it, the reason, the lead data and the recent notes on that lead. The reviewer opens a request, reads the evidence, and takes one of two actions. Approve marks the lead as Bad Lead and it moves into replacement review. Reject returns the lead to New, which puts it back in front of the rep as a lead to work rather than leaving it in limbo. Either way a resolution note is attached, so the answer to why a request was decided the way it was is written down next to the request.

The statuses are plain: Submitted, Approved, Rejected. There is a filter by status and by company, and a printable Quality Control Request Report for a manager who wants to walk through the month's requests on paper. A salesperson never has to wonder whether a report went anywhere; the lead's status changes, and the request has a visible outcome.

One thing worth saying plainly, because every lead vendor gets asked: an approved request is a replacement review, not a promise of a specific count on a specific day. Leads are delivered as consumers submit them, and nobody can promise what a consumer will do. What the process does promise is that a bad lead gets looked at by a person, decided on the record, and not quietly forgotten.

At most stores the bad lead process is an email. A manager builds a list at the end of the month, sends it to the vendor, and waits. The vendor asks for proof, the manager digs through a rep's phone for call history, and by the time the argument is settled the leads in question are six weeks old and the credit, if any, is a line on the next invoice nobody checks. The cost is not just the lead. It is the manager's hours, the rep's cynicism about the source, and the fact that a real lead sometimes gets reported as bad because reporting is easier than working it.

Filing from the lead record removes the digging. The communications log, which keeps every call, text, MMS, email and voicemail on the lead in one place, is the proof. A request that shows two calls, a text with a Failed status and a bounced email is decided quickly. A request with nothing in the log is also decided quickly, in the other direction, and that is fair to both sides. There is no separate tool, no per request fee and no dispute form to download; the review is part of the platform, and the pricing page shows the plans it comes with.

Dealers sometimes ask why we do not just filter the bad ones out up front. Two reasons, and both are compliance reasons before they are product reasons. First, exclusive delivery of every submitted lead in a zone means the store is not competing with three other rooftops for the same person, and that only works if nothing is withheld. The moment a vendor starts deciding which submissions are worth sending, the dealer is trusting a black box and the exclusivity claim gets soft.

Second, financing campaigns run under fair lending rules that forbid narrowing an audience by age, gender, income, marital status, household size, education, language or ZIP. A pre delivery quality filter that learns from outcomes tends to drift toward exactly those proxies. A post delivery review of a specific lead, on a stated reason, by a person, with the record attached, does not. It looks at whether the phone rang and the email bounced. That is a defensible process, it produces a written trail on every decision, and it keeps the store's own lead handling clean too: the reason for review and the resolution note are stored with the lead, alongside the encrypted Customer Profile that holds the consumer's information.

There is nothing to turn on. Report Lead To Quality Control is in every lead detail from the day the account is created, for any user role, because the person who worked the lead is the person who knows it was bad. Master Administrators and managers see the outcomes on the lead status and can review the month through the printable report. If a store wants requests routed through a manager before they are submitted, that is a workflow question our team sets up on request rather than a switch in the product.

The process also does not depend on us being reachable in the moment. If the CRM is briefly unavailable, the leads you already received are in your lead inbox and on the LeadLocate mobile app once it reconnects, the notes and communications log are retained, and a request filed later still carries the full history of what was tried and when. Nothing about a bad lead needs to be reported the same hour it was worked. The contact page reaches a person for anything that does not fit the form.

The stores that file the fewest replacement requests are not the ones with the best leads. They are the ones whose first hour on a lead is the most thorough, because a lead that has been called, texted and emailed inside the CRM either turns into a conversation or turns into an obvious, well documented bad lead. Three features do most of that work. Lead notifications put the new lead in the rep's hand by text and sound the moment it arrives. The Phone Validator and Email Validator show validity dots on the lead so a rep knows before dialing whether the number is live. And custom lead statuses and tags let a store mark a lead Attempted, Contacted or Appointment Set so a manager can see, before anyone reports anything, which leads were actually touched.

Pair those with the DNC Blacklist, which blocks inbound spam in both directions and runs a live do not call lookup on numbers, and the leads that reach the Quality Control page are the genuine exceptions. The full list of what surrounds this feature is on the all features page.

What happens to a bad lead after I report it?

It appears on the Quality Control Requests page with your reason, the lead data and the recent notes. A reviewer approves or rejects it. Approval marks the lead Bad Lead and it moves into replacement review; rejection returns the lead to New so it is worked again. A resolution note is stored with the request either way.

Where is the Report Lead To Quality Control button?

In the lead detail inside LeadLocate CRM, on every lead, for every user role. It opens a short form with a reason for review field and a Submit Request button. The request carries the lead's data and communications log with it automatically.

What should I write in the reason for review?

What you tried and what happened. The form asks which methods of communication were used, such as phone calls, text messages and email, and why the lead should be considered bad. Two or three specific lines decide a request faster than a paragraph of frustration.

Is a lead that will not answer a bad lead?

Not by itself. A lead that went quiet is a lead that needs a follow up process. A bad lead is one that could not be worked: a disconnected number, a bounced address, a duplicate, a test entry or a customer who says they never submitted anything. Use Mark Lead As Lost for the first kind and Report Lead To Quality Control for the second.

Why does LeadLocate deliver every lead instead of filtering first?

Because exclusive delivery of every submitted lead in your zone only means something if nothing is withheld, and because financing campaigns run under fair lending rules that a learned pre delivery filter tends to drift against. Reviewing a specific lead after delivery, on a stated reason, keeps both promises.

Does replacement review cost extra?

No. It is part of the platform on every plan that includes lead delivery. There is no per request fee and no separate dispute tool. Plans and prices are on the pricing page.

Every lead in your zone is delivered exclusively, and the ones that were never workable get reviewed on the record. Watch the pre-recorded demo or ask us to walk through the Quality Control page.

Prefer to talk right now? Call or text 844-376-2274.