How to Run Campaigns With AI Voice Calling

Start with a segment, not the whole list

The instinct with a new tool is to point it at everyone: the whole customer base, one big call. Resist that. A campaign works better when the list is narrow enough that a single conversation goal makes sense for everyone on it. Overdue service, open recalls, and seasonal reactivation are three different conversations with three different reasons for calling, and mixing them into one list means the AI is either generic with everyone or accurate with nobody.

Pull the segment the way you'd pull it for a human BDC push: overdue by mileage or date since last visit, recall status from the DMS, or customers who serviced with you last winter but haven't been seen since spring. The tighter the criteria, the more relevant the call sounds to the person picking up, and relevance is most of what keeps someone on the line instead of hanging up.

It's also worth trimming the list before it goes out, not after. Exclude anyone already booked for that reason, anyone who opted out of a previous campaign, and anyone flagged with an open complaint or a sensitive account note. A clean list saves you from explaining an awkward call afterward.

Decide the goal before you decide the script

Every campaign needs one clear goal, and it has to be decided before anyone thinks about what the AI should say. Overdue service and recall campaigns usually have an obvious goal: get the appointment booked. Seasonal reactivation is murkier. Sometimes the honest goal is just to remind someone the dealership exists and let them call back when they're ready, not to force a booking on that call.

This matters because the two goals need different conversations and different measures of success. A booking-focused call needs to reach available times and confirm one before it ends. An informational call can end well without a booking, as long as the customer got a clear reason to think about coming in. Trying to force every call into a booking turns an informational touch into a pushy one, and customers respond to that.

Pick the goal per segment, not per campaign in general. It's fine to run three campaigns in the same week with three different goals, as long as each one is clear about what it's trying to accomplish.

How the conversation should actually flow

A good outbound call follows a shape, not a script read word for word. It opens by identifying the dealership and the reason for the call plainly, then states the specific reason: the vehicle is due for service, there's an open recall on file, or it's been a while since the last visit.

If the goal is booking, the call should move to scheduling within a couple of exchanges, using the dealership's real availability and scheduling rules, not a generic slot confirmed later by a human. If the customer has questions, the conversation should answer the common ones (what the service involves, roughly how long it takes) before circling back to the ask. And if things get more complicated than a scripted flow can handle, the call should hand off cleanly along the dealership's configured escalation path rather than stall or guess.

The other thing a well-run call needs is a graceful exit. Not everyone wants to book on the spot, and not everyone wants to be called again. The conversation should make it easy to say no, ask to be called back later, or opt out entirely, and that response needs to be captured accurately, since it feeds directly into who gets called on the next campaign.

Tracking what actually happened on each call

Once calls start going out, every one of them needs to land in a small number of clear outcomes: booked, declined, opted out, no answer, or escalated to a human. This isn't just record-keeping, it's what makes the campaign usable afterward. A pile of call recordings with no structured outcome behind them is not much better than not having called at all, since nobody's going to listen back through hundreds of calls to figure out what happened.

Bookings should show up wherever the service department already tracks appointments, not in a separate report someone has to reconcile by hand. Opt-outs need to be respected on the next list pull automatically. Escalations, calls where the AI handed off to a person or the customer asked for something a script couldn't resolve, need to be visible to whoever follows up, ideally the same day, not buried until someone goes looking.

Reading the results and adjusting the next campaign

After a campaign finishes, look at four numbers before anything else: how many calls connected, how many of those turned into a booking, how many people opted out, and how many escalated to a human. Connection rate tells you whether the list and the calling window were reasonable. Low connection often means the list is stale or the calls went out at a bad time of day, rather than anything wrong with the conversation itself.

Booking rate against connected calls tells you whether the conversation is actually working, not just whether people picked up. If connection is fine but bookings are low, the issue is usually the offer or the goal, not the calling. Maybe the segment wasn't as relevant as it looked on paper, or the ask came too early or too late in the call.

Opt-out rate is worth watching closely even when everything else looks good. A campaign that books well but generates a lot of opt-outs is trading short-term bookings for a shrinking list to call in the future, a bad trade to make repeatedly. High escalation rates usually point to a segment that needed a more nuanced conversation than the goal assumed, which is useful for narrowing the segment next time, not a sign the whole approach failed.

None of these numbers mean much in isolation on the first run. The value shows up campaign over campaign, comparing this month's recall push against last month's to see whether narrowing the list, changing the calling window, or adjusting the goal actually moved the numbers. Treat the first campaign as a baseline, not a verdict.