In brief: Use a text to identify the dealership, refer to the customer’s request and offer a clear next step. Route replies to a BDC rep, verify the channel and CRM record on a test contact, and use calls when the customer is ready for a live conversation.
When an internet lead arrives, a dealership BDC can answer by text, then call when a person is ready to talk. Use iMessage for eligible iPhone contacts, RCS when an Android phone and carrier support it, and configured SMS fallback where available. Keep replies attached to the CRM record and make a rep responsible for the handoff.
On a recent call, an auto dealer put the real problem plainly: leads touch the BDC, an automated follow-up and a stream of texts all in the same week, and nobody had agreed on when the automated message should start once a human had already reached out. The same dealer admitted their own reps go four or five days without following up on a lead despite being told to call back the same day. Texting will not fix a rep who will not follow up. It does close the gap between when a lead raises their hand and when anyone from the store actually reaches them, and it leaves a manager a written record of exactly what was sent and when.
How Fast Does a Dealership BDC Need to Answer an Internet Lead?
Internet leads can arrive through a form, chat widget or listing site. In a 2025 mystery shop, 61% of dealerships answered a web lead within 15 minutes, up from 55% in 2022, but 19% still took more than an hour to respond at all (DAS Technology data, via Ventavid’s 2026 benchmark review). A missed call may not tell the lead what the store is answering; a short text can identify the rep and refer to the vehicle they asked about.
Texting gives the customer room to read and reply when available. Podium reports a 98% open rate and 45% response rate for automotive texts, citing Gartner; treat these as vendor-published benchmarks, not a forecast for a specific store (Podium’s automotive texting data). A practical test is to send an appropriate first text, then call if the customer replies or the situation calls for a conversation.
What Should the First Text to an Internet Lead Say?
Keep the first text short, name the human sending it, and ask one question the lead can answer in two words. A wall of inventory specs reads like a blast; a plain, specific question reads like someone actually looked at the submission.
Copy this template and swap in your own fields:
Internet lead, first touch: “Hi [name], this is [BDC rep name] at [dealership]. Saw you’re looking at the [year/make/model] on our site, still want more info on that one or something similar?”
No exact stock match: “Hi [name], thanks for reaching out about the [vehicle]. That exact one just sold, but I’ve got two close matches on the lot. Want me to text you photos of both?”
After a quiet form fill: “Hi [name], following up on your note about the [vehicle]. Still shopping, or did you already find something?”
Each template ends with a question the lead can answer by just replying, not a link they have to click or a form they have to fill out a second time.
How Do You Confirm a Test Drive by Text Instead of a Call?
A test drive is an appointment, and the appointment-confirmation problem dealerships have is the same one every service business has: a confirmation call that lands in voicemail leaves the desk guessing whether the customer is actually coming. Our guide to confirming appointments by text instead of calling covers the general template; a test drive needs two extra fields a routine service appointment does not: which vehicle and whether it is still physically on the lot.
Test drive confirmation template: “Hi [name], confirming your test drive of the [year/make/model] tomorrow at [time] with [rep name]. Bring your license, and reply YES to confirm or RESCHED if you need a new time.”
Send that text the moment the drive is booked, then a short reminder the morning of the appointment. If the lead replies RESCHED, the BDC rep handles the new time inside the same thread instead of opening a fresh conversation, so there is one record of the vehicle, the time and every change instead of three disconnected notes scattered across the CRM.
How Do You Send Service Reminders That Actually Get a Reply?
A missed service appointment can leave a bay unused, but the size of that problem varies by store and appointment mix. Numa reports a 15% to 25% range and describes one dealership that reported a change from 23% to 11% after adopting a three-touch text program; those are vendor-reported figures, not a guaranteed outcome for another store (Numa’s service no-show guide).
Three touches means three separate messages, not three repeats of the same line: one when the appointment is booked, one the day before, and one the morning of the visit, each short enough to read at a glance.
Service reminder templates:
At booking: “You’re set for service at [dealership] on [date] at [time] for [service type]. Reply YES to confirm or call [service number] to change it.”
Day before: “Reminder: your [vehicle] is in for [service type] tomorrow at [time]. Need a loaner or a ride? Reply here and we’ll set it up.”
Morning of: “See you today at [time] for your [vehicle]‘s [service type]. We’re at [address].”
Dealers ask us this directly: with the BDC, an automated follow-up and these reminder texts all touching the same customer, when should the automated message start once a human already called or texted, and how many touches is too many before a customer feels hounded? The answer is a stop rule, not a feeling. Once a human rep has a live reply in the thread, hold every other automated message to that contact until the rep’s own conversation is resolved, and treat the rep’s message, not the automation schedule, as the record other workflows check before sending anything else.
How Do You Send Photos and Videos of a Vehicle Over iMessage?
A phone call cannot show a buyer the interior they’re asking about; a text can. iMessage carries photos and short videos directly in the thread, the lead sees them inline without opening a separate app or clicking out, and read receipts and typing indicators tell the rep whether the lead is actually looking at what was sent before anyone calls to close.
Use this for the walkaround the lead did not ask for by name but will watch anyway: when a lead asks about a specific trim or color, text two or three photos and a 30-second walkaround video of the actual VIN sitting on the lot, not a stock photo pulled from the manufacturer’s site. A lead who sees the real car, with any dent disclosed and the trim confirmed, shows up for the test drive already sold on walking in rather than merely curious.
Can a BDC Text an Entire Sale-Event List at Once?
A one-to-one reply thread and a sale-event blast to last year’s buyers are two different problems, and treating them the same way is how a dealership gets a line flagged. One-to-one lead and service texts should stay on the BDC’s assigned line, where volume tracks real, individual conversations. A larger sale-event send needs its own plan for budget, sending capacity and who answers the replies that come back in; see Beam’s outbound texting guide before you point a sale-event list at the same number your BDC uses for live leads.
How Do You Build This BDC Texting Workflow, Step by Step?
- Connect a Beam line to your CRM and assign it to the BDC queue, not a shared front desk number, so replies land with whoever is actually working that lead.
- Pull every internet lead source into the same inbox: website chat, Facebook lead forms, listing sites and any third-party lead provider, so a rep is not checking five separate places for a new alert.
- Map each lead stage your CRM already tracks, such as new, contacted, appointment set, test drive scheduled, sold or lost, to one template above, so the right message fires without a rep retyping it from memory.
- Add a stage-change trigger so the first-touch text fires automatically when a lead lands, and the test drive confirmation fires the moment an appointment is booked.
- Set the service reminder sequence on its own schedule tied to the appointment date, separate from the sales-lead sequence, so a service customer never gets a sales-style first-touch text by mistake.
- Write the stop rule into the workflow itself: once a BDC rep has a live reply in a thread, hold every other automated message to that contact until the rep’s conversation is resolved.
- Connect the GoHighLevel iMessage setup if that is your CRM, and confirm replies route back into the same contact record instead of spawning a duplicate.
- Run one real lead through the entire flow end to end, on a vehicle and a phone you control, before turning it on for the floor: first text, a reply, a test drive confirmation, and a service reminder.
- Check delivery on that test lead rather than assuming a sent text arrived; confirm whether it went out as iMessage, RCS or SMS fallback, and whether the reply landed back in the CRM.
- Train the BDC on the rule that matters most: a reply means a human picks up the thread, and an automated message never argues with a lead who already answered.
Screenshot: a CRM contact record showing one thread with the first-touch text, the test drive confirmation reply and a photo of the actual vehicle, all under the same contact, with a delivery tag (iMessage, RCS or SMS) on each message.
Quick checklist before you turn this on
- One lead source connected first, not five, for the opening week.
- A named rep assigned to the BDC line, not a shared mailbox nobody checks on weekends.
- Every template written without a locked-in price or a specific payment figure a buyer could later quote back as a promise.
- A stop rule that hands the thread to a human the moment a lead replies.
- A test lead run end to end before a real customer ever reaches the workflow.
- Delivery checked on that test lead, never assumed.
Should a BDC Text or Call an Internet Lead First?
Text first, call second, and the reasoning holds across every stage above: a text does not need both people free at the same moment, and it leaves the BDC a record of exactly what was sent. A call still earns its place for the lead who replies ready to talk specifics, or who needs the back and forth a thread cannot carry.
| Channel | Where it fits | What it misses |
|---|---|---|
| Phone call | A lead who already replied and is ready to talk specifics | Needs both people free at once; an unanswered call looks like no response at all |
| iMessage or RCS text | First touch, confirmations, reminders, photos and short videos | Not built for a long, back-and-forth negotiation |
| A full quote sheet or finance paperwork | Often sits unread for hours, much like a voicemail |
If the bottleneck at your store is not the texting workflow but getting a phone answered fast enough in the first place, RizzDial’s guide to AI dialers for dealership BDC automation covers the calling side: parallel dialing, answering machine detection and routing a hot lead to whichever rep is actually free. This article covers the channel that runs beside the dialer, not instead of it.
What Do Dealership BDC Teams Ask Before Turning This On?
How much does it cost to text internet leads through Beam?
Beam’s pricing is not posted here because it depends on your lead volume, number of lines and current CRM setup. Text our team to try it and get a quote scoped to your BDC instead of guessing from a generic rate card.
How long does it take to get a BDC texting workflow live?
There is no fixed timeline worth promising. It depends on whether your CRM already fires a clean event when a lead lands or a test drive is booked, whether your line is connected, and how many test leads it takes before the wording and timing hold up. Keep the workflow in draft until a lead you control moves through every stage correctly.
Does this work with our CRM and the DMS we already use?
Beam connects directly to GoHighLevel today. For a DMS or a different CRM, route lead and appointment events to Beam through the API or a webhook instead of assuming a native connection exists, and confirm the specific integration with your provider before you build a workflow around it.
Do we need A2P 10DLC registration to text internet leads?
It depends on the number type, not on whether the lead came from the internet. A2P 10DLC registration applies to local SMS numbers, iMessage lines do not need it, toll free numbers need toll free verification instead, and short codes need separate carrier approval. Confirm the registration status of each line before sending at volume.
We already blast texts for sale events. What does switching to this workflow cost us?
There is no published switching price because the real cost is process, not platform fees. Start with one lead source and one test drive flow, prove the reply and hand-off work, then expand. Text our team to try it on a line scoped to that pilot before you touch your sale-event blast list.
Set the stop rule and one clean lead source before the first real customer hits this workflow, and a BDC stops choosing between answering fast and keeping a record of what was promised. Start with Beam’s outbound texting guide for the sending side, check the GoHighLevel iMessage setup for the CRM connection, and text our team to try it on one lead source before rolling it out past a single BDC rep.