Before a dealership adds a BDC vendor, check the CRM phone integration underneath it: every call logged to the right customer record, clear routing between BDC, sales, and service, monitored call quality, and one named owner for each piece.
Last updated: October 28, 2026
Picture the Monday meeting. The BDC director has the weekend’s numbers, and the general manager wants to know why a shopper who says she called twice on Saturday has no activity in the CRM. Her number is in there. So is the lead. The calls aren’t. Somebody suggests a new BDC vendor, or one of the AI tools that answers every call, and the room nods.
Hold that thought for a week.
A BDC, human or AI, runs on plumbing it doesn’t own. The phone system carries the call. The network and the internet circuit carry the phone system. The CRM is supposed to end up with a record of all of it. When one of those pieces is off, a new vendor doesn’t fix it. It inherits it. Then it gets blamed for it.
I spent five years on the CRM side of this business before I came to Helion Technologies, and the lesson I took from it is a plain one. A CRM only knows what reaches it. This post is the check I’d run on the plumbing before signing anything new. It’s also how we look at phones and integrations as part of managed IT for dealerships, where one team owns the whole line from the handset to the customer record.
What CRM Phone Integration Means at a Dealership
CRM phone integration is the connection between a dealership’s phone system and its CRM that logs each inbound and outbound call, with its recording and outcome, to the right customer record. A BDC rep, salesperson, or manager can then see who called, who answered, and what happened next.
That’s the whole job. It sounds simple, and most demos make it look simple, because the demo uses one clean phone number and one clean customer.
Your store isn’t a demo. It has a main line, a service line, a parts line, tracking numbers on the website and in the ads, salespeople on their own cell phones, and customers who share one household number. Every one of those is a place where a call can happen and never reach the CRM.
The Four Pieces a BDC Runs On
Before you look at any vendor’s feature list, sort the plumbing into four pieces and write down who owns each one today. Be honest here. Most stores can fill in two of the four without calling anybody. The other two are where the trouble lives.
| Piece | What to check | What it looks like when nobody owns it |
|---|---|---|
| Call logging | Does every call, from every line and every tracking number, attach to the right customer record with its recording? | Leads with no activity, duplicate customers, recordings nobody can find |
| Call routing | Where does a call go when the BDC is busy, closed, or the caller wants service, parts or a specific salesperson? | Service calls ringing in sales, full mailboxes, callers who hang up after the third transfer |
| Quality and circuits | Who watches call quality, the network the phones ride on, and the internet circuit, and who gets the alert? | Choppy calls, dropped calls, and a store that only finds out when a customer complains |
| Ownership | Which vendor owns each piece, who has the admin logins, and who the store calls when it breaks? | Three vendors on a call, each sure the problem belongs to one of the others |
If you can’t fill in the last column with a name, you’ve found your first project.
Does Every Call Land on the Right Customer Record?
Start with the Saturday shopper from the Monday meeting. Her calls almost certainly happened. The question is where they went.
Most phone-to-CRM connections match a call to a customer by phone number. That works. Until it doesn’t. A caller from a number the CRM has never seen needs a rule: create a new lead, attach to an open one, or drop into a queue for somebody to sort out. Two customers on one household line need a rule too. So do calls that come in on a website or advertising tracking number and then get forwarded, because the CRM may log the tracking number instead of the customer’s. If nobody wrote those rules down when the integration went in, the system is making those decisions on its own. Quietly. Every day.
Then there’s the call that never touches the system at all. A salesperson texts and calls a customer from a personal cell phone, the deal closes, and the CRM shows a lead that went cold. Alexis Merchant covered the habit side of that in her post on CRM adoption at the dealership. The plumbing side is simpler. If the store’s phones can’t follow a salesperson onto the lot, the calls will go around them.
Here’s a quick test. It takes half an hour. Pull 20 calls from last Saturday’s phone records and look each one up in the CRM. Count how many you find attached to the right person, with the recording. You’ll learn more from that than from any vendor’s slide.
Your CRM can’t report on calls it never saw.
Where Does the Call Go When the BDC Is Busy?
Routing is the part everybody assumes somebody else set up. Usually somebody did. Years ago. Then they left.
Walk a call through your store on paper. A customer dials the main number at 7:45 on a Tuesday morning wanting to move a service appointment. Does it hit the BDC, the service desk, or a menu? If the service advisors are all on the drive, does it roll to a person, a mailbox, or back to the operator? Now do it again at 6:30 on a Saturday evening, and again for a parts counter call from a body shop. At a multi-rooftop group, do it once per store, because I’d bet the routing isn’t the same at all of them. Not even close.
Then ask who can change it. When the BDC director wants overflow calls to go to two senior salespeople on Saturdays, is that a five-minute change somebody at the store can make, or a ticket with a phone vendor that takes until next week?
One piece of routing isn’t optional. The FCC’s rules for multi-line telephone systems, adopted in 2019 under Kari’s Law and RAY BAUM’S Act, cover systems installed after February 16, 2020: callers have to be able to dial 911 directly, without dialing a 9 first, and the 911 call has to carry a location precise enough for responders to find the caller. When a store moves, adds a building, or reshuffles its lines, that location data has to move with it. Put it on the checklist.
Good routing is boring. That’s the goal.
Who Watches Call Quality and the Circuits?
A BDC rep can do everything right and still lose the customer to a bad line. The voice cuts in and out, the customer says “you’re breaking up” twice, and then she calls the store across town.
Nobody files that as an IT problem. The store just gets quieter.
Modern phones are data on your network, riding the same internet circuit as the DMS, the CRM, and the Wi-Fi in the customer lounge. Microsoft’s network guidance for Microsoft 365 calling puts the symptom plainly: calls that “have static and cut out, or voices sound like robots” could be jitter or packet loss. The same guidance recommends quality of service settings on every segment of the network, so voice gets priority, and warns that Wi-Fi isn’t necessarily designed for real-time voice unless somebody plans it that way. Any phone system. Same rule. So ask who at your store, or at which vendor, is watching call quality right now, and whether the phones roll to a backup circuit when the main one drops. Our dealership network management page covers the circuits, firewalls, and Wi-Fi.
Somebody will notice a bad line. Better it’s you.
Which Vendor Owns Each Piece?
Now the people part.
Here’s how it usually goes. Cybersecurity came from one company, network support from another, the phones from a third, and the CRM integration from whoever sold the CRM, so the store has five or six vendors before anybody has counted. Then on a busy Saturday the phones get choppy and the calls start. The network company looks at its gear and says it’s the phone system. The phone company looks at theirs and says it’s the internet, and the CRM folks say the integration’s fine on their end, which it probably is. The dealer ends up holding a problem everybody can see and nobody owns.
Adding a BDC vendor on top of that adds a seventh voice to the same call. So before you do, make the list. For each piece of the plumbing, write down:
- The company that owns it and the contract it’s under.
- Who at the store holds the admin login, and whether anybody who left still has one.
- The number the store calls when it breaks, and how fast they actually answer.
- Which other pieces it touches, because a phone change can break the CRM logging and a firewall change can break the phones.
- Who decides when two vendors disagree.
That last line is the one most stores leave blank. It’s also the reason we run phones, network, and integrations under one team in our managed dealership phone systems service. With 2,000-plus dealerships under management, we’ve seen the finger-pointing enough times to stop selling it in pieces. We manage the technology so dealers can sell and service cars and heavy trucks, and so the BDC director doesn’t spend Monday on a conference call between three vendors.
One owner. One phone number to call.
Where an AI BDC Fits
None of this is an argument against a new BDC vendor or an AI tool that answers the phones. Some of them are good. They just need the same plumbing a human BDC needs, and they’re less forgiving about it, because an AI agent that can’t find the customer record can’t fake it.
The questions about the AI itself are a different list. What it can read and change in your CRM and DMS, whose consent covers its texts, and who owns the conversations are in my post on questions to ask before an AI BDC works your leads. Recording, consent, and security for a voice agent are in the AI phone agent security and consent checklist. I won’t repeat them here.
To be clear about our lane: Helion Technologies doesn’t build or sell the customer-facing AI. We run the phones, the network, and the connections that AI depends on. And if your store is changing DMS at the same time, the phone and network contracts deserve a look of their own, which is what the guide to phones and network when leaving CDK for Tekion covers.
The plumbing comes first, whoever answers the call.
What Dealers Ask Before Adding a BDC Vendor
Can’t the new BDC vendor just handle the phone integration for us?
How do I know if calls are actually reaching the CRM?
Our BDC is only four people. Does any of this matter at our size?
Who should own the phone system: IT, the BDC director, or the phone vendor?
What happens to all of this when we switch CRMs?
Check the Plumbing First
A new BDC vendor is a decision about how your store talks to customers. The plumbing under it is a decision about whether those conversations get recorded, routed, and kept. Make the second one first. The first one gets a lot easier.
If you want an outside look before you sign, start with our complimentary IT and cybersecurity assessment. We’ll look at how your phones, network, circuits, and integrations are set up today, who owns each piece, and where the calls are going missing, and we’ll tell you plainly what’s ready for a new BDC vendor and what isn’t. That’s the tried and true way to buy one with some peace of mind.