Automotive BDC Case Study Proof: What Dealers Should Verify

Learn how to verify an automotive BDC case study through source records, outcome definitions, date windows, exclusions, and CRM evidence.

An automotive BDC case study should let a dealer follow the evidence, not just admire the result. Start with the date window and customer population. Define each outcome. Name the systems used to verify it. Show the exclusions and explain how duplicate records were handled.

A testimonial can add useful context, but it is not the same as performance evidence. The FTC's current endorsement guides say endorsements must reflect the endorser's honest opinions, findings, beliefs, or experience. The guides also say an advertiser needs adequate substantiation when a consumer endorsement communicates that the experience is representative of what others will generally achieve.

That makes a simple review question useful: can the claim be traced from the published sentence back to the source records?

Quick answer

A useful BDC case study should provide:

If any of those pieces are missing, treat the case study as a starting point for questions rather than proof that the same result will transfer to another store.

Separate the story from the evidence

A case study usually has two jobs. It tells the reader what changed, and it supports the claims made about that change. The story may be short. The evidence rarely is.

The story can explain the operating problem, the BDC model, the handoff, and the result. The evidence package should contain the records behind those statements. A sentence such as "follow-up became more consistent" needs a defined measure. A statement about appointments needs appointment records and status definitions. A claim about visits or sold outcomes needs a matching source beyond the BDC's own notes.

This does not mean every public article should expose customer data or internal reports. It means the publisher should have reviewed enough source material to support the public wording. Customer details can remain private while the method, definitions, and evidence boundaries stay clear.

The same distinction improves BDC call review. A polished call excerpt can illustrate one conversation. It does not establish how the whole queue performed.

Freeze the starting population

A result is difficult to evaluate when the starting population changes after the work begins.

Record which customers, leads, campaigns, stores, departments, channels, and lead sources were eligible at the start of the date window. Keep the inclusion rules with the case study. If records enter later, label them as additions rather than silently mixing them into the original group.

The population should also match the claim. A service follow-up example should not include sales inquiries unless the report separates them. A campaign sent to previously contacted customers should not be described as new-lead performance. A result from one lead source should not be presented as the result for every source.

Use stable identifiers when possible. Customer IDs, lead IDs, appointment IDs, and event timestamps make later reconciliation easier than names or free-text notes. If the source systems use different identifiers, document the matching rule and keep ambiguous matches out of the final count until someone resolves them.

This is where lead-routing rules matter. A record that changed queues or owners can still belong in the original population, but the ownership history should explain who controlled the next action at each point.

Define every outcome before counting

Words that sound obvious often hide different business rules.

"Appointment" can mean the customer asked for a time, an agent entered a time, the store confirmed the visit, or the customer arrived. Those are separate states. "Contacted" can mean a call connected, a text delivered, a customer replied, or an agent left a voicemail. Those events should not share one definition.

Write the outcome dictionary before the final report. For each status, define the required source record, timestamp, owner, and evidence. Then map every reported result to one status.

A practical appointment sequence might include requested, scheduled, confirmed, arrived, completed, canceled, and no-show. The exact labels can differ by CRM, but each event should have one meaning. Moving a customer through several states must not create several appointments.

Clear lead disposition definitions help keep the BDC's activity records separate from dealership outcomes. The BDC can document its work. A visit or sold claim should come from the system authorized to record that outcome.

Trace each result across source systems

A case study becomes stronger when each outcome can be traced across the systems that created it.

The BDC record may show the call, text, email, note, or appointment request. The CRM may show the current lead state and owner. The scheduling system may show the booked time. The DMS or an approved dealership outcome log may show whether the customer arrived or purchased. None of those systems should be asked to prove more than it records.

Build a reconciliation table with one row per customer or outcome. Include the source IDs, event dates, status history, and final inclusion decision. Keep the original timestamps rather than replacing them with the date the report was built.

Pay attention to time zones and calendar boundaries. A call near midnight, an appointment rescheduled into another month, or a visit recorded after a delayed sync can move between reporting periods. State which timestamp controls each metric and use it consistently.

The final report should identify missing sources. If the DMS export was unavailable, do not convert appointments into sold outcomes. If a CRM integration failed during part of the window, name the gap and limit the claim.

Show exclusions and duplicate rules

Exclusions are part of the result, not cleanup that can be hidden at the end.

List test records, employees, duplicate profiles, canceled campaigns, bad contact data, preexisting appointments, and records outside the approved date window when they are excluded. Explain why each category does not belong in the reported population.

Use a written duplicate rule. Two records with the same phone number may be one customer, a shared household number, or two different people. A name match can fail after a spelling change. A vehicle match can connect unrelated owners over time. The rule should use the strongest available identifiers and send uncertain cases to review.

Keep the raw count, deduplicated count, excluded count, and final analyzed count separate. That lets a reviewer reproduce the path without exposing customer information in the public article.

Treat testimonials as claims with context

A testimonial should preserve the speaker's actual meaning. It should not be trimmed until a limited experience sounds universal.

The FTC's current endorsement guides state: "Endorsements must reflect the honest opinions, findings, beliefs, or experience of the endorser." The same section says the endorsement may not be presented out of context or reworded in a way that distorts the endorser's opinion or experience.

The consumer endorsement section addresses another issue. A consumer's experience can communicate what other customers will generally achieve. The guide says the advertiser should have adequate substantiation for that representation. If it does not, the ad should clearly disclose generally expected performance and have substantiation for that disclosure.

For a BDC case study, keep the speaker, date, relationship, scope, and original statement with the review file. If the customer received compensation or another benefit connected to the endorsement, route the disclosure through qualified counsel and the dealership's approved policy.

Do not attach a stock photo to a real testimonial in a way that suggests the pictured person is the speaker. Use an approved real image, identify an illustration as such, or publish the words without a portrait.

Compare like with like

A case study from another store can inform a decision. It cannot remove the need to examine local conditions.

Compare the work before comparing the outcome. Check the lead sources, departments, date window, coverage hours, staffing model, channels, customer mix, inventory conditions, CRM configuration, and appointment definitions. A result from a narrow campaign should not be treated as proof for the entire BDC.

Ask what changed besides the vendor or workflow. New inventory, different media spend, a seasonal event, staffing changes, pricing policy, or a CRM migration can affect the same outcome. The case study should identify known changes and avoid assigning all credit to one cause.

This is also why the BDC vendor access plan belongs in the review. A provider with broader data or write access may appear more complete simply because it can see or edit more of the customer journey.

Ask for the review package

A dealer does not need every customer record in a sales conversation. It does need a clear way to evaluate the claim.

Ask for a redacted method note that covers the population, dates, definitions, systems, exclusions, duplicate rules, attribution window, and reviewer. Request a sample reconciliation row with customer details removed. Ask whether the dealership reviewed the final wording and whether the experience is presented as one example or as typical performance.

Then test one reported outcome in each category. Follow an appointment from the original conversation to the schedule record. Follow a visit to the dealership's approved outcome source. Follow a sold result to the record authorized to establish it. If the links break, the case study needs more work before it becomes sales proof.

Frequently asked questions

What should an automotive BDC case study include?

It should identify the date window, starting customer population, channels used, outcome definitions, exclusions, source systems, and reconciliation method. A dealer should be able to trace each reported appointment, visit, or sold outcome back to the approved records that support it.

Does a dealership testimonial prove typical BDC results?

No. A testimonial describes one endorser's experience. The FTC's endorsement guides say consumer endorsements can communicate that an experience is representative, which requires adequate substantiation or a clear disclosure of generally expected performance. Dealers should ask what broader evidence supports the claim.

How should BDC appointments be verified?

Define an appointment before counting it, then connect the appointment record to the customer, date, requested department, scheduled time, and final status. Separate requested, scheduled, confirmed, arrived, completed, canceled, and no-show states so one event is not counted as several outcomes.

What questions should dealers ask a BDC vendor about case studies?

Ask who supplied the data, which systems were checked, whether results were deduplicated, which records were excluded, how attribution was assigned, whether the dealership reviewed the figures, and whether the reported experience is presented as one example or as a typical result.

Proof should survive the handoff

A useful case study can move from marketing to operations without losing its meaning. The definitions remain clear. The records still reconcile. The exclusions are visible. The public claim stays inside the evidence.

That standard may produce a quieter story, but it gives a dealer something better than hype: a method that can be checked before the next BDC decision.

Reviewing a BDC proposal or case study? Talk with Paramount Lead Solutions about outcome definitions, source records, attribution, and the operating review behind the claim.