Text Messaging Consent Basics for Dealership Teams

The BDC manager is proud of the new cadence: same-day text, evening bump, Saturday reminder. The desk is proud of the appointment count. Nobody can answer a simpler question: for the last twenty numbers that received a sales text, where is the record that those people agreed to be texted? The answers come back as shrugs, screenshots, and "they messaged us first." That is not a consent program. That is a stack of assumptions.

Text messaging consent basics for dealership teams start with a definition the floor can use. Consent is a documented permission to send SMS to a specific number for a specific kind of message. A phone field on a lead is not consent. A Facebook Marketplace inquiry is not automatically a blank check for a personal-cell drip. A trade worksheet with a mobile number is not a marketing list until your process says it is, and until the customer has actually agreed.

This article is operational training for GMs, internet directors, and BDC leads. It is not legal advice and it does not quote statutes, penalties, or carrier thresholds. Confirm your store's requirements with counsel, with your texting vendor, and with current regulators. Then put a floor procedure in place that a new associate can follow on a Saturday.

Text Messaging Consent Basics for Dealership Teams: What a "Yes" Looks Like

If reps cannot describe a valid yes, they will treat every number as a yes. Teach examples, not slogans.

Sources that are not, by themselves, consent to a sales drip

Train these as yellow lights, not green lights:

• A phone number scraped from a Marketplace profile, a voicemail, or a caller ID.
• A number on a credit application used for financing contact, unless your process and disclosures cover SMS in a way counsel has approved.
• A number a spouse gave you for "if you cannot reach me."
• A number from an old deal file, a service RO, or a sold-customer list being reused for a new campaign.
• "They asked if the car was available," followed by a week of promotional texts about other units.

Some of those contacts may still be reachable on another channel. Some may have given SMS permission in a form your store already uses. The point is that the number's existence is not the proof. The proof is the captured yes.

Sources that the floor can treat as a conversation, with limits

A person who texts you first is in an active thread. That is not a license to enroll them in every future campaign. Conservative operating standard:

• Reply on the same thread about the vehicle they asked about.
• Do not add them to a blast list from that thread alone unless your documented process says that inbound SMS plus a disclosure equals campaign consent. Many stores should keep campaign enrollment on a separate, explicit yes.
• If you switch from answering their question to a multi-day drip, you have changed the nature of the messages. That is the moment to have a logged permission, not a hunch.

Platform inboxes add another layer. A Marketplace message is not SMS. Moving that conversation to text should be an ask, not an ambush. Customers who want to handle everything by text still need a number they chose to give you, and a record of that choice.

What to capture when they say yes

When a customer agrees to text, log it like a hold or a sold status: as a fact, not a vibe.

• Date and time.
• Number.
• Who captured it (employee name).
• How they agreed: verbal at the desk, written on a form, inbound text, checkbox on a web form your store actually uses.
• Scope, in plain language: appointment reminders, this vehicle only, or broader marketing, according to what they were told.

If you cannot fill those fields, you do not have a record. You have a story. Pair the consent record with handling text opt-out requests from leads correctly so the yes and the stop live in the same place.

Floor Rules That Keep Text Messaging Consent Basics From Depending on Memory

Policy that lives in a binder will lose to a rep who is behind on calls. Put the rules in the tools people already touch.

One outbound texting path

Pick a store-approved method: a vendor platform, a logged store phone, or another system your manager can audit. Ban freelance sales texting from personal cells except as a documented exception (after-hours emergency, manager-approved). Personal cells destroy consent records because nothing writes back to the CRM.

If a buyer insists on texting a rep's personal phone, the rep still logs the number, the consent, and the opt-out on the customer record. The conversation is store business. The phone owner does not get a private lead file.

Scripts that ask, instead of announce

Teach a short ask for the moment you want to leave the original inbox:

• "Is it okay if I text this number with the appointment time and a photo of the unit?"
• "We can keep this in Messenger, or I can text you the address. Which do you prefer?"

Do not say "I'm going to text you" as if the decision is already made. Do not hide the ask inside a paragraph of vehicle specs. The ask is its own sentence. Then log the answer.

Cadence cannot outrun the yes

A follow-up cadence is healthy. A cadence that continues after a vague "maybe" on SMS is how you manufacture STOP messages. Write:

1. What message types are allowed under appointment-level permission (time, address, "we are holding the car until 1:15").
2. What message types need a broader yes (new inventory, price-drop blasts, sold-customer "we want your trade").
3. A maximum number of unanswered sales texts before the cadence pauses, as a conservative store standard, not as a law.

Silence is not consent to increase frequency. Silence is a reason to try a call or to stop.

Manager Controls: Proof, Samples, and Vendor Settings

The internet director should be able to show, for a random lead, why that number was texted. If that audit is impossible, the program is too informal for the volume you are sending.

Weekly sample of outbound texts

Pull ten outbound SMS threads. For each, find the consent note. If the note is missing, that is a coaching event for the sender and a process event if the CRM has nowhere to put the note. Do not only sample deals. Sample the texts that did not result in a visit. Those are the ones most likely to be aggressive.

Vendor and form settings are part of the same system

If you use a web form, a chat widget, or a texting vendor, the language on those forms and the opt-out handling in the vendor are part of consent basics. Floor training cannot contradict them. If the form says you will send appointment texts, do not also enroll that number in a weekend blast without a separate, documented yes your counsel accepts.

Keep a contact preference log for calls, texts, and emails as the human-readable layer. Vendors fail, CRM fields get overwritten, and reps invent codes. A preference log with time stamps is the backup.

New hires

Consent is day-one training, not a memo after a complaint. In onboarding, have the new rep:

• Identify three fake leads that should not be texted.
• Log a mock yes.
• Process a mock STOP.

If they cannot pass that drill, they should not get blast-list access.

Edge Cases Dealerships Hit Every Week

Real lots do not only text neat web leads. Prepare the gray files.

Shared phones and wrong numbers

If the person who answers says you have the wrong number, stop. Do not keep texting because the CRM says that is the buyer's mobile. Fix the record. If a parent gave a child's number, get a yes from the person who owns the phone, or use another channel.

BHPH, service, and sales sharing a customer

A service reminder program and a sales campaign can collide on one mobile. A yes for "your oil change is due" is not automatically a yes for "we have a new truck." Keep purpose separate unless your documented, counsel-reviewed process combines them. Operationally, the floor should see purpose on the preference log: sales SMS, service SMS, or neither.

Marketplace to SMS handoff

Ask for the number. Confirm it in the thread. Log it. Do not harvest a number from a photo of a driver license sent for a different reason and enroll it. That is how stores create ugly fact patterns. For the sales conversation itself, stay inside the same professionalism you use in the original inbox; moving to SMS does not make a low-effort blast acceptable.

Again: this is not legal advice. Edge cases are exactly where you call counsel instead of inventing a store folklore rule.

How PostToMarket Automates This

Consent lives in your CRM, your texting vendor, and your playbook. PostToMarket does not send SMS and does not store a TCPA file. What it does is reduce the freelance behavior that skips consent: leads stuck on personal devices, unclear vehicle status, and a second rep "just texting them the other car" from a private phone.

Inquiries in a store-visible inbox

• Leads inbox for managers, so a Marketplace conversation is not the same thing as an unlogged mobile drip.
• Team analytics by rep and source so you can see who is working which origin, which is the first question in a consent audit.

Inventory that does not require extra bumps

Many unnecessary texts exist because the listing is stale or the backup unit is hard to find. Inventory statuses, mark as sold, AI-generated titles and descriptions you can edit, and unlimited vehicles in inventory cut the excuse for a speculative SMS about a car you are not sure you still have.

Roles instead of shared logins

• Admin, manager, sales rep, and associate roles, with per-rep queues and manager assignment for associates.
• Mobile dashboard to reorder a posting queue between customers, so the work happens in the product instead of in a side text thread.

Use your counsel-approved texting stack for consent. Use PostToMarket so the vehicle and the original inquiry are not living in a channel you cannot inspect.

Teach the Yes Before You Teach the Cadence

Text messaging consent basics for dealership teams are a record-keeping habit: a documented yes, a defined message type, a store-approved sending path, and a stop that every system honors. If your cadence is sophisticated and your consent file is empty, you built the program in the wrong order.

PostToMarket centralizes inventory and Marketplace inquiries so managers can see the work. Starter is $59 per month for a solo seller or independent lot with one login. Dealership is $299 per month for up to 13 team logins, including managers who can inspect queues and the leads inbox.

Start your 10-day free trial through secure Stripe checkout. Put the conversations in a place you can audit, then align SMS with a yes you can actually find. Cancel anytime.