The first 30 days with an outsourced BDC should run in four steps: the store hands over its hours, logins, rules and contacts; the vendor builds and tests the call flow; calls go live on a narrow scope while both sides listen to recordings; then a first report and a day-30 review decide what changes.
Before Day One: What the Store Hands Over
An outside team can only be as accurate as what you give it. Agree on one owner at the store (usually the GM, the sales manager or the BDC manager) and have that person collect the items below before the kickoff. Every item that arrives late becomes a week of agents saying "let me check on that" to your customers.
| What to hand over | Who at the store has it | Why the agents need it |
|---|---|---|
| Hours by department, holiday hours, after-hours rules | GM | So nobody books a Sunday appointment at a store that is closed Sunday |
| Brands, model lines, what you do and do not sell or service | Sales and service managers | To answer the first question on most calls |
| Inventory source: the live feed or website the agent should trust | Internet manager | To confirm a vehicle is there before setting the visit |
| CRM and scheduler logins, one per agent | CRM administrator | To log every touch where your managers will see it |
| Scheduler rules: shop capacity, appointment length, loaner and shuttle rules | Service manager | To book the shop without overbooking it |
| Talk tracks and what agents must not quote | Sales manager, BDC manager | So the call sounds like your store and stays inside your rules |
| Escalation contacts and the warm-transfer list, by hour of day | GM | So a ready buyer or an upset customer reaches a person |
| Lead sources and phone numbers in scope | Internet manager, marketing | So both sides agree on what the vendor is answering |
Two of those deserve extra care. Logins should be named, one person each, with the narrowest role that does the job; the detail is in our piece on giving a BDC vendor CRM access. And the transfer list has to be real. If the people on it do not pick up, the agent is left holding a live customer with nowhere to send them.
If you have no written talk tracks, say so at the start. A vendor can work from its own until yours exist, and the BDC script library on this site is a reasonable base to edit from.
Week 1: Build the Call Flow and Break It on Purpose
Week one produces two documents and one round of testing.
The first document is the playbook: the handover items above turned into what an agent says and does, call type by call type. You approve it. The second is the call flow: which numbers ring where, after how many seconds a call rolls to the outside team, what the caller hears, what caller ID an outbound call shows, and how a recorded call is announced in both directions. The mechanics of rollover are covered in overflow call handling for dealerships.
Then test it. Before any customer reaches the new flow, place calls yourself:
- Call the sales line and the service line during open hours and let them ring.
- Call at lunch, at shift change and after close.
- Submit a web lead on a specific vehicle and time the reply.
- Ask for a warm transfer to each name on the transfer list.
- Open the CRM and find each test call: the note, the agent's name, the recording.
Any test that fails gets fixed and run again. Our five-minute secret shop describes the same exercise from the customer's side, and it is worth repeating every month after launch.
Week 2: Go Live Narrow and Listen
Start with the smallest scope that proves the setup: after-hours only, overflow only, or one lead source. A narrow start keeps a mistake in the playbook from touching every customer on the first day.
Then listen. For the first two live weeks, the store's owner and the vendor's account lead should each hear a handful of calls every day, including some that did not end in an appointment. You are listening for store knowledge more than for sales skill: wrong hours, a model you do not carry, a loaner promised that the store does not offer, a transfer to someone who left in March.
Send corrections in one channel, in writing, and ask for them to be added to the playbook. A correction given by phone to one agent is gone by the next shift.
Tell your own people what is happening. Salespeople and advisors should know who is setting these appointments, where the notes are, and that the customer was promised a specific person at a specific time.
Week 3: The First Report and the First Corrections
By the third week there is enough volume for a first report. What you are checking is whether the report can be produced at all, with the right lines and the right denominators, and whether its counts match what your CRM and phone system show for the same days. If the vendor says 61 calls were offered and your phone report says 84, find the difference now.
The lines to expect are laid out in the weekly report an outsourced BDC should send you. In week three, resist judging the rates. Judge the plumbing: is every appointment in the CRM, is every shown appointment marked shown, is every recording reachable.
This is also the week to widen the scope if the narrow start has been clean, or to hold it if the corrections list is still growing.
Week 4 and the Day-30 Review
Put the day-30 review on the calendar at the kickoff. It should have an agenda and it should end with decisions.
- The numbers. Calls offered and answered, leads worked, contacts, appointments set and shown, against the baseline you had before launch.
- The corrections log. What was wrong, what was fixed, what keeps coming back.
- The handoff. Are transfers being picked up? Are appointments being greeted by the person promised?
- The scope. Widen, hold, or narrow.
- The playbook. One updated version, dated, that both sides sign off.
Thirty days is early for sold numbers, because many of the appointments set in the month have not had time to turn into deals. It is not too early to know whether calls are being answered, logged and handed off the way you agreed. If you set this up as a trial, the longer measurement plan is in how to pilot an outsourced BDC for 90 days.
Where Onboarding Stalls on the Dealer's Side
Vendors cause delays too, but these are the stalls you control.
- No owner. Three managers each assume another one is answering the vendor's questions.
- Logins that never arrive. The CRM administrator was not told, or the store hands over one shared login to save a seat.
- Scheduler rules that live in someone's head. The service manager knows the shop takes six waiters a morning. The scheduler does not.
- A transfer list nobody agreed to. Names were written down without asking the people named.
- The floor was not told. The first outsourced appointment arrives and the salesperson asks what brings them in today.
- No baseline. Without last month's numbers, the day-30 review is a matter of opinion.
- Playbook changes by hallway conversation. A new special or a new hours policy never reaches the agents.
If you are building an in-house room instead, the equivalent checklist is in our roadmap to starting a BDC from scratch.
How Pinnacle Describes Its Own Start
The calendar above is what we think a dealer should expect from any vendor. It is not a published Pinnacle schedule. What Pinnacle does publish for BDC On Demand is three steps.
- A complimentary consultation with the BDC operations team to assess the store's call volume, staffing gaps and missed-opportunity rate.
- A custom plan. Pinnacle learns the store's brands, CRM workflows, appointment process and service menu. Agents follow the store's own processes and talk tracks, and if the store wants a better playbook, Pinnacle's trainers help build one.
- Launch, with call recordings, performance metrics and regular reporting.
The timing, scope and reporting rhythm for a given store are set in its plan. The rest of this series is in the Dealership BDC Guide.
Frequently Asked Questions
How long does it take to onboard an outsourced BDC?
It depends mostly on how fast the store hands over logins, scheduler rules and a transfer list. A store with those ready can be testing a call flow within days. A store that has to write its rules down for the first time should allow longer. Ask the vendor for its usual timeline and what it needs from you to hit it.
Who at the dealership should own the outsourced BDC relationship?
One named person with authority over both the phones and the floor: the GM, a sales manager or an existing BDC manager. That person answers the vendor's questions, approves the playbook, listens to calls in the first weeks and runs the day-30 review. Shared ownership is the most common reason onboarding drags.
Do I need written scripts before an outsourced BDC can start?
No, but you need written rules: hours, what agents may quote, who takes transfers and how the shop is booked. Talk tracks can start from the vendor's and be edited toward your store's voice. What cannot be borrowed is the store-specific information, and that is what callers ask about first.
Should my in-house BDC agents be involved in onboarding?
Yes. They know the questions customers really ask, the quirks of your scheduler and which transfer extensions go unanswered. Have them review the playbook and place test calls. If the outside team is covering overflow or after-hours, your agents also need to know how to pick up a lead the vendor touched first.
What should I check on the first day calls go live?
Place a call yourself, then find it in the CRM with its note, agent name and recording. Ask for a transfer and see who answers. Confirm that the appointment you set appears where your managers look for appointments. If those three things work on day one, the rest is refinement.
Summary
A sound first 30 days has a handover before day one, a tested call flow in week one, a narrow launch with daily listening in week two, a first report checked against your own systems in week three, and a day-30 review that ends in decisions. Most delays come from the store's side: no owner, late logins, unwritten scheduler rules and a floor that was never told. Fix those before launch.
