Automotive BDC Follow-Up Schedule

A written cadence beats a motivated team every time, because the cadence still runs on the Saturday everyone is slammed.

Ask a BDC manager how many times a lead gets contacted before the store gives up and you will hear a number. Pull the actual activity data and the real number is almost always lower, frequently by half. This is not laziness. It is what happens when a cadence lives in someone's head rather than in a system.

The pattern repeats in every store. Day one is enthusiastic: a call, a text, an email, all inside an hour. Day two gets one call. Day three gets a call that goes to voicemail and nobody leaves one. Then a busy Saturday arrives, three walk ins land at once, and that lead is never touched again. Nobody decides to abandon it. It simply falls off the bottom of a mental list.

The consumer side of this is worth understanding, because it explains why persistence pays rather than annoys. Someone who submitted a form is shopping, and shopping takes weeks. They are talking to two or three stores, waiting on a trade payoff, waiting on a spouse, waiting on a pay period. Silence on day four means they were busy, not that they bought somewhere else. Our page on what to expect from car sales leads covers this in more detail, including why a shopper asking about a vehicle above their budget is a real opportunity rather than a waste.

The fix is unglamorous. Write the schedule down, load it into the system once, and let the system carry it. A cadence that requires memory is a cadence that stops the first busy week of the month.

Every other part of the schedule is negotiable. The first response is not. A lead that gets a real response within a few minutes behaves like a different lead than one answered three hours later, and every study the industry has produced points the same direction. We will not quote a specific figure at you, because the honest answer depends on your market and your traffic, but the direction is not in dispute. Our page on response time and close rate covers the relationship.

What a good first hour looks like in practice: the lead lands in the inbox and is distributed by rule, not by whoever happens to be looking. Within five minutes a text goes out, because a text gets read and a phone call from an unknown number frequently does not. Within fifteen minutes someone calls. If the call is not answered, a voicemail is left, and it is a specific one that names the vehicle rather than a generic request to call back. Within the hour an email follows with something useful in it.

Three tools carry most of this weight. Global lead distribution with rules puts the lead in front of a named person immediately instead of into a shared pile. Missed call text back means a shopper who calls while your lines are busy gets a text rather than a dead end, which is covered on our missed call text back page. And voicemail drop lets an agent leave a prepared message and move to the next call without waiting through the greeting, which is the difference between forty dials and seventy in the same hour.

This is a starting point rather than gospel. Adjust it to your traffic and your staffing, but change it deliberately rather than by drift.

That is roughly sixteen touches across four channels in two weeks. Compare it against what your team is actually doing this month before you decide it is too aggressive. Almost every store discovers it is running a third of it.

After day fourteen the cadence changes character. Daily pressure stops working and becomes noise. What replaces it is a long, low frequency rhythm that keeps you present without becoming a nuisance.

A workable long tail: one touch in week three, one in week four, then roughly every two weeks through week twelve, then monthly. Alternate channels so the same person is not receiving the same kind of message every time. Each touch needs a reason to exist. A price change on the unit they asked about. A similar vehicle arriving. A trade value update. A financing program change. If you have nothing to say, a message that says nothing is worse than no message.

This is where automation earns its cost, because no human being maintains a twelve week cadence across four hundred leads by hand. Drip campaigns with a drip editor handle the scheduled side. Automations and task automation create the calls that need a person. Reminders put the human touches on someone's calendar with a name attached rather than leaving them to goodwill.

One caution about tone. A twelve week cadence written in sales language reads as harassment by week six. Written as a helpful person keeping you posted, it reads as service. The difference is in the copy, not the schedule, which is why the text templates and call scripts matter as much as the timing.

Channel choice is not decoration. Each one does something the others cannot, and rotating them is what keeps a long cadence from feeling repetitive.

Text is the workhorse. It gets read, it gets answered, and it lets a shopper reply in the two minutes they have. SMS and MMS with real threading means photos of the actual vehicle land in the same conversation as the price. RCS with automatic SMS fallback gives you a richer, branded message on handsets that support it without cutting anyone off on handsets that do not.

Phone is for the moments that need a real conversation: a trade discussion, a payment objection, setting an appointment. Click to call with a VoIP softphone keeps the call inside the record, and call recording with transcription means a manager can read the conversation later rather than listening to all eleven minutes of it. Voicemail drop is for volume days, when leaving forty prepared messages is more valuable than having six live conversations.

Email carries what will not fit anywhere else: multiple vehicles, full photo sets, a link to a customer facing deal page with real numbers on it. It is also the channel that dies quietly, which is why an email validator matters before any campaign goes out. Sending to dead addresses damages your sending reputation for the addresses that are still good.

Two supporting tools most stores do not expect a CRM to include. A phone validator checks numbers before your team spends an afternoon dialing disconnects. And IVR with call routing through AutoMail makes sure the inbound half of the conversation, which is the half where the customer is actually motivated, gets answered rather than ringing out.

A flat schedule is a starting skeleton. What separates a real BDC from a dialing operation is what happens when the lead does something.

They answer and set an appointment. The follow-up cadence stops and an appointment cadence starts: confirmation immediately, a reminder the day before, a reminder the morning of, and a text with directions and a name to ask for. Appointments and reminders live on the calendar with an owner so nothing depends on memory.

They no show. This is the most under worked branch in the industry. A no show is not a lost customer, it is usually a scheduling failure. Reach out the same day, without blame, and offer two new times. Our page on no show appointment recovery covers the sequence.

They answer but are not ready. Ask when, then set the follow up for that date rather than dropping them back into a generic drip. A lead with a real date attached is worth more than a lead with a status.

Wrong number or bad contact data. Mark it and stop. Continuing to dial a disconnect is how agents lose faith in a call list.

They ask you to stop. Honor it immediately and permanently across every channel and every rooftop. Opt outs are a compliance obligation, not a preference, and the blacklist exists so a stop request in one place stops everything.

Here is the practical build order, and it takes an afternoon rather than a quarter.

1. Write the cadence on one page first. Day, channel, owner, message intent. Argue about it with your managers before you build anything, because arguing about it inside the software is slower.
2. Load the message library. Text templates and email templates for every scheduled touch, so an agent is editing rather than composing. Composing from scratch is where cadences lose their fifteen minutes per lead.
3. Build the follow-up process. Scheduled sends handle the automated touches. Task automation creates the calls that need a human, assigned to a named person with a due time rather than a due day.
4. Set the branches. Appointment set, no show, not ready, bad contact, opt out. Each one changes the path.
5. Set distribution rules. Decide who receives what before the first lead lands, not after the first argument about it.
6. Watch it for two weeks, then adjust one thing. Changing five variables at once teaches you nothing.

Our page on CRM follow-up cadence covers the configuration side in more depth.

Every store believes its cadence is running. The data usually disagrees, and the gap between belief and behavior is where the month goes.

Three numbers tell you almost everything. Median time to first response, measured in minutes rather than as an average, because one lead answered on Monday morning drags an average into fiction. Touches per lead before the trail goes cold, which is the number that exposes a cadence that exists only on paper. And contact rate by time of day, which almost nobody measures and which routinely shows that the hours your team calls are the hours nobody answers.

Because communication happens inside the platform rather than on personal cell phones, that data is real rather than self reported. Activity reporting shows what individual agents did. Company reporting shows store level performance. Management reporting rolls it up. Call logs and global lead history let you answer the argument that starts with a manager insisting a lead was never received.

Call transcription changes coaching more than any dashboard does. A manager who can read four calls in the time it used to take to listen to one starts coaching weekly instead of quarterly. The BDC manager dashboard page covers what to watch daily.

One honest note to finish on. We cannot guarantee close rates or appointment volume, because those depend on your market, your inventory and your people. What a written schedule running inside a system does is remove the variable that is entirely yours to control, which is whether the follow up happens at all.

How many times should we contact a lead before stopping?

Far more than most stores do. Roughly sixteen touches across four channels in the first two weeks, then a lower frequency rhythm out to twelve weeks and monthly after that. Stop immediately if the customer asks you to.

How fast does the first response need to be?

Minutes, not hours. A text inside five minutes, a call inside fifteen, an email inside the hour. Nothing later in the schedule recovers a slow day zero.

Is texting this often a compliance risk?

Texting is consent based and opt outs must be honored immediately across every channel and every store. The blacklist and opt out handling exist for exactly this. Frequency alone is not the issue; contacting someone who asked you to stop is.

Can the schedule run automatically?

The scheduled touches can. Follow-up processes and drip campaigns handle timed sends, and task automation creates the calls that need a person, assigned by name with a due time. The human touches still need humans.

What should we do about no shows?

Treat a no show as a scheduling failure rather than a rejection. Reach out the same day without blame and offer two specific new times. It is the most under worked branch in most stores.

How do we know the cadence is really running?

Measure median time to first response in minutes, touches per lead before the trail goes cold, and contact rate by time of day. Because the communication happens inside the platform, that data is measured rather than self reported.

We will build your schedule in the platform, load your templates, and show you the reporting that proves it ran. Month to month, no long term contract.