What is a BDC lead disposition?

A BDC lead disposition is the status assigned to a lead after an action or conversation. It should describe what happened and what happens next. Useful dispositions separate no answer, bad contact information, active conversation, appointment set, customer purchased, and closed records instead of hiding several outcomes under one vague label.

Why clean the CRM before launching a new BDC workflow?

A new workflow uses the records already in the CRM. If those records contain duplicates, stale tasks, unclear owners, or inconsistent labels, the team starts by acting on bad information. Cleanup creates a reliable starting point for assignments, follow-up rules, and reporting.

Which BDC records should be reviewed first?

Start with open leads that have overdue tasks, no assigned owner, repeated no-answer labels, conflicting notes, or recent customer activity. Those records are most likely to create an immediate customer experience problem or distort the first weeks of performance reporting.

Should old dealership leads be deleted during cleanup?

Usually not. Deleting records can remove useful customer history and create reporting gaps. Archive or close records with a documented reason, preserve the notes, and define when the record can return to an active queue. Delete only when policy, consent, or data-retention rules require it.

Before the First Call: How We Clean Up a BDC Lead Queue

A practical BDC lead disposition cleanup process for removing stale tasks, duplicates, and unclear ownership before a new workflow goes live.

A new BDC workflow does not begin with a clean slate. It begins with whatever is already sitting in the CRM.

That usually includes good customer history mixed with duplicate records, overdue tasks, unclear owners, and dispositions that mean different things to different people. If the team starts calling before those records are sorted, old data problems become new operating problems.

The first job is not writing a script. It is making the queue honest.

Why the labels cannot be trusted yet

A disposition looks precise because it lives in a dropdown. The label may say "no answer," but that does not tell a manager whether the advisor called once, left a voicemail, sent a text, discovered a bad number, or reached the customer on another record.

The same problem shows up with "not interested." One advisor may use it after a clear refusal. Another may use it when a customer says the timing is wrong. A third may select it to clear an overdue task. The CRM stores one label for three different situations.

We treat broad dispositions as claims that need a quick check. The notes, task history, call recordings, and recent customer activity provide the evidence. The goal is not to relitigate the entire history. It is to stop a vague label from making the next decision automatically.

Start with the records that can cause trouble today

Reviewing an entire database at once is a good way to spend days cleaning records that may not enter an active workflow. We start with the queue most likely to affect a customer now:

Open leads with overdue tasks
Records with no assigned owner
Duplicate contacts with activity on more than one record
Leads marked "no answer" after very little documented outreach
Closed records with recent calls, replies, or website activity
Appointments with no clear confirmation or outcome

This gives the team a working set. Records outside that set can be handled by a separate retention or archive process. They should not slow down the active queue cleanup.

Each selected record gets one of three outcomes: ready for action, needs manager review, or inactive with a documented reason. Those outcomes are intentionally plain. A team can work from them without interpreting a long list of inherited status codes.

Define each disposition in one sentence

If a disposition needs a paragraph to explain, advisors will not use it consistently. We write a one-sentence definition and pair it with the next required action.

"No answer" means the contact attempt reached no person and produced no reply. It does not mean the number is bad. It does not close the lead. The next action is another contact attempt using the approved cadence.

"Bad contact information" means the phone number or email failed and the failure is documented. The next action is to verify another contact method or route the record for research.

"Not interested" means the customer clearly declined further conversation. It requires a note in the customer's own words and the correct contact preference. It is not a shortcut for an uncomfortable call.

This definition work feels fussy until two advisors classify the same conversation differently. Then the cost becomes obvious. Reporting cannot be cleaner than the decisions underneath it.

Resolve duplicates without erasing history

Duplicate records are rarely exact copies. One may contain the original web lead. Another may hold a service appointment. A third may have the phone number the customer actually answers. Merging blindly can bury the useful timeline or attach activity to the wrong opportunity.

We choose a primary record based on identity, recent activity, and the current reason for contact. Then we preserve relevant notes, communication preferences, and appointment history before linking or merging the duplicates. If ownership differs across records, a manager decides which team owns the next action.

The test is simple: after the merge, can an advisor understand what the customer asked for, what has already happened, and what should happen next? If not, the cleanup is incomplete.

Assign one owner and one next action

Shared responsibility often means no responsibility. A record assigned to a store, a department, and two advisors can still sit untouched because each person assumes someone else has it.

Each active lead should have one accountable owner. Other people may contribute, but the CRM should show who owns the next action and when it is due. If the lead crosses departments, the handoff should create a new task for the receiving owner rather than leaving both names attached to an old task.

We also remove tasks that no longer have a purpose. An overdue task is not automatically useful. If the customer already purchased, opted out, or moved into another workflow, the task should close with a reason. Moving stale tasks into tomorrow only makes tomorrow's queue less believable.

Check a sample against the customer history

Before the cleaned queue goes live, we test it. A manager pulls records from each major disposition and compares the label with the notes, calls, messages, ownership, and next task.

This is where hidden rules surface. Maybe one advisor uses "contacted" after leaving a voicemail while another uses it only after a conversation. Maybe service opportunities are being assigned to sales by default. Maybe a closed lead can still receive an automated follow-up.

The sample is not meant to prove the data is perfect. It tests whether the definitions and routing rules produce sensible decisions. When a mismatch appears, fix the rule first. Correcting one record without correcting the rule leaves the same failure mode in place.

What the team receives on launch day

The cleanup ends with a short operating document, not a giant data report. It contains the active dispositions, the sentence that defines each one, the required next action, the ownership rules, and the path for exceptions.

The team also gets a queue that can be explained. Advisors know why a record is active. Managers know which assumptions were reviewed. Reporting begins from a named baseline instead of quietly mixing old habits with the new process.

That baseline matters more than a polished launch presentation. Scripts can be improved after real conversations. Cadence can be adjusted when the team sees response patterns. A queue built on unclear labels cannot support either decision.

Before the first call, make the data tell the truth.

Need a second set of eyes on your BDC queue? Talk with Paramount Lead Solutions about a practical workflow review before your next process change.