10DLC Registration for Dealerships: Brand and Campaign Setup Without Rejections

How dealerships get 10DLC texting approved: what the provider files, sample wording, opt-in language carriers check and a checklist to avoid rejections.

10DLC registration is the carrier approval a dealership needs before it can text customers through software from a standard 10-digit local number. The texting provider submits two records to The Campaign Registry: a brand (the legal business) and a campaign (what the store sends and how customers agree). Most rejections trace back to mismatched business names or vague opt-in details.

At a glance

A dealership cannot register with The Campaign Registry itself; the texting provider registers the brand and campaign on the store's behalf.
The brand's legal name must match the IRS record for the store's tax ID exactly, so a rooftop that trades under a different name needs that DBA added to the brand.
Carriers check that the campaign description, sample messages, website and privacy policy all name the same business and describe the same kind of texts.
Opt-in consent belongs to one campaign and one sender, so a customer's consent to one texting tool does not carry over to another.
Approval can be instant or take several weeks, and changing the content after approval usually means registering a new campaign.

What 10DLC registration covers for a dealership

10DLC registration covers business texts sent from software over an ordinary 10-digit local number to US phones. The Campaign Registry describes 10DLC as an A2P (application-to-person) messaging channel in which brands and their campaign service providers are verified, and it states that direct registration is not currently available to brands. In practice the dealership's texting provider, such as its CRM or service texting vendor, files the registration for the store.

Registration has two parts. According to Twilio's A2P 10DLC documentation, the brand describes who is sending, so carriers can confirm the business is legitimate, and the campaign explains how customers opt in, opt out and get help, and what the messages are for. Amazon's 10DLC setup guide lays out the same order: register the company, optionally apply for vetting, register the campaign, then attach the phone number to the approved campaign.

Skipping registration is not a workable option. Twilio's Conversations documentation says carriers block A2P traffic to US recipients from unregistered Twilio 10DLC numbers, and its main 10DLC page says unregistered traffic carries additional carrier fees. Toll-free numbers and short codes are outside 10DLC and have their own approval processes.

10DLC registration is a carrier requirement, not a legal safe harbor. Federal and state texting laws still apply on top of it; the guide to text messaging rules for car dealerships covers those consent rules.

What the dealership has to supply for brand registration

The dealership supplies the legal and contact details the provider uses to register the brand, and the legal name is where most dealership brands go wrong. Twilio's error 30918 page says that for US businesses the legal business name must exactly match the name registered with the EIN on the IRS CP 575 notice or 147C letter, and it lists a DBA, trade name or subsidiary name used in place of the legal name as a cause of rejection. If customers know the store by a different name, Twilio's advice is to add the DBA to the brand registration before resubmitting the campaign.

That matters for dealerships because the name on the sign is often not the name on the tax record. A store called "Lakeside Ford" may be owned by "Lakeside Automotive Holdings LLC". Gather these before the provider asks:

The exact legal name, as printed on the CP 575 notice or 147C letter for the store's EIN.
The EIN itself and the business address on file with the IRS.
Any DBA the store uses with customers, and confirmation that it is registered.
The public website address, which should match the business name and be live, finished and not password-protected.
A named contact person, email address and phone number for the brand.

Brand type also affects the result. Twilio's registration approval guide says a business with an EIN cannot register as a sole proprietor and that such applications are rejected. Twilio's documentation also describes Low-Volume Standard and Standard brands, with Standard brands given higher daily sending limits based on a trust score. Other providers present these options differently, so ask yours which brand type it is filing.

Choosing the campaign use case for dealership texts

The campaign use case should match the texts the dealership actually sends, because carriers compare the use case with the description and samples. The Telnyx list of 10DLC use cases defines the standard categories, including these that are most relevant to a dealership:

Marketing: any message with marketing or promotional content, such as a sales event, a trade-in offer or a service coupon.
Customer Care: customer care conversations, including account management and support, such as replying to a shopper's question about a unit.
Account Notification: standard notifications for account holders about their account.
Delivery Notifications: updates about the status of delivery of a product or service.
Mixed: two to five sub use cases on one campaign, for brands that want to run several types together.
Low Volume Mixed: up to five sub use cases for brands that only need very low throughput, such as small businesses.

Most dealerships send a blend: sales follow-up, appointment reminders, service status updates and occasional promotions. A Mixed campaign that names those sub use cases is often the honest description of that blend, while a store that only sends service updates may fit a narrower category. This is a suggestion, not a carrier rule; the provider makes the final call. Choose carefully, because Syniverse's 10DLC knowledge center says a use case cannot be changed after registration and the campaign has to be deactivated and registered again.

How to write the campaign description and sample messages

A campaign description passes review when it says who is sending, who receives the texts and why. Twilio's campaign registration recommendations say the description must answer those three questions and that generic text, such as a line saying the campaign sends messages to customers, is rejected.

What a dealership campaign description can say

The wording below is a starting point to adapt, not approved carrier language. Replace every bracketed field with the store's real details:

[Legal name] doing business as [Store name], a [new and used auto / RV / boat / powersports] dealership in [City, State], sends text messages to customers and shoppers who have opted in. Messages include replies to vehicle inquiries, appointment confirmations and reminders, service status updates when a vehicle is ready, and occasional promotional offers. Customers opt in through a consent checkbox on the [website lead form], a signed consent on the in-store [credit application / service repair order], or by texting START to [number]. Message frequency varies.

Sample messages written for a dealership

Sample messages should look like real production texts, with templated fields in brackets. Twilio's recommendations ask for the business name in at least one sample and opt-out language in at least one sample, and the samples must match the use case and description. Example samples a dealership could adapt:

Sales follow-up: "[Store name]: Hi [First name], the [Year Make Model] you asked about is still on the lot. Would [Day] at [Time] work for a test drive? Reply STOP to opt out."
Appointment reminder: "[Store name] reminder: your service appointment is [Day] at [Time]. Reply C to confirm or call [Phone] to reschedule. Reply STOP to opt out."
Service status: "[Store name] Service: your [Model] is ready for pickup. We are open until [Time] today. Reply HELP for help."
Promotion (only if the campaign includes marketing): "[Store name]: Our [Month] service special on [Service] runs through [Date]. Book at [full store website address]. Reply STOP to opt out."

Use the store's own full web address in samples. Syniverse lists public URL shorteners among the reasons campaigns are rejected.

Opt-in, HELP and opt-out responses

The provider also registers the automatic replies customers receive. Twilio's recommendations say the opt-in confirmation must include the brand name, HELP instructions, opt-out instructions, a recurring-message disclosure with frequency, and "Message and data rates may apply". The opt-out reply must name the brand and confirm no more messages will be sent, and the HELP reply must name the brand and give a phone number or email address. Dealership versions might read:

Opt-in confirmation: "[Store name]: You're signed up for texts about your inquiries, appointments and service. Msg frequency varies. Msg and data rates may apply. Reply HELP for help, STOP to opt out."
HELP reply: "[Store name]: For help call [Phone] or email [Email]. Reply STOP to opt out."
STOP reply: "[Store name]: You have been unsubscribed and will receive no further messages."

Opt-in language carriers check on dealership forms

Carriers want to see exactly where and how each customer agreed to texts, so the opt-in method has to be specific and verifiable. Twilio's recommendations say every opt-in method used should be listed, consent cannot be hidden in terms for other services, and opt-ins behind a login or on paper need verifiable evidence such as a hosted screenshot. Twilio's approval guide adds that a web consent checkbox must stand alone and be unchecked by default.

A dealership often collects consent in three places, and each needs its own evidence:

Website lead and service forms: a separate, unchecked checkbox with consent wording next to it, plus links to the terms and privacy policy.
In-store paperwork: a consent line on the credit application, repair order or delivery paperwork, with a sample image the provider can host.
Text-to-join: a keyword such as START sent to the store's number, followed by the opt-in confirmation above.

Example checkbox wording to adapt: "I agree to receive text messages from [Store name] about my inquiry, appointments, service and offers at the number provided. Msg frequency varies. Msg and data rates may apply. Reply HELP for help, STOP to opt out. Consent is not a condition of purchase. [Terms] [Privacy Policy]." Have the dealership's own counsel review consent wording before it goes live.

The privacy policy needs one specific line. Twilio's recommendations say a compliant policy must state that no mobile information will be shared with third parties or affiliates for marketing or promotional purposes, and Twilio's approval guide calls the absence of that language a major source of rejection.

Consent is also tied to a single program. The CTIA Messaging Principles and Best Practices (July 2019), section 5.1.2.2, says an opt-in should not be transferable or assignable and applies only to the campaign and sender it was obtained for. CTIA released an updated edition in 2023, according to a May 2026 Holland & Knight analysis; the 2019 text is quoted here because it is the edition that could be opened directly. For dealerships the practical point is that consent collected for one texting tool does not automatically cover another tool texting the same customer.

Why dealership 10DLC campaigns get rejected, and how to fix each

Dealership campaigns are usually rejected for a handful of fixable reasons that provider and carrier documentation describe consistently. The common ones, with the fix for each:

Business name mismatch. The brand uses the store's trade name instead of the legal name on the EIN record. Fix: use the exact legal name and add the DBA to the brand (Twilio error 30918).
Vague campaign description. Text such as "marketing messages to our customers" does not say who, to whom or why. Fix: use a description like the one above that names the store, the recipients and each message type (Syniverse; Twilio).
Weak samples. Placeholder text, no store name, no opt-out language, or content that does not match the use case. Fix: real-looking samples with brackets, the store name and STOP language (Syniverse).
Unclear opt-in. "Customers opt in" without saying where or how, or missing disclosures such as frequency and rates. Fix: list every method and supply evidence for paper and in-store consent (Syniverse; Twilio).
Privacy policy gap. No statement that mobile information is not shared for marketing. Fix: add the line and confirm the page is public (Twilio).
Website reviewers cannot verify. The site is under construction, password-protected or under a domain that does not match the business name. Fix: point to the live dealership site that shows the store name (Twilio).
Wrong use case. Promotional texts registered as notifications, or a low-volume store using a category built for higher volume. Fix: re-register under the right use case, since it cannot be edited (Syniverse).
Consent from someone else's list. Syniverse says contacts from third-party lists are not acceptable and each brand must collect its own consent. Ask the provider how it treats leads forwarded from third-party marketplaces before texting them.

If the store's texting has gaps beyond registration, such as slow replies or follow-up that stops after one message, the Revenue Leak Audit reviews lead response, follow-up and conversion and walks through the findings with the dealership.

A pre-submission checklist for dealership 10DLC registration

A dealership can catch most rejection causes by checking each item below before the provider submits. The list combines the provider and carrier guidance cited above with dealership-specific steps:

List every tool that texts customers from a 10-digit local number: CRM, service texting, review requests, missed call text-back, chat. Ask each vendor whether it registered a campaign for the store and under which brand name.
Confirm the legal name, EIN and address match the IRS CP 575 notice or 147C letter exactly.
Confirm every DBA the store uses with customers is on the brand registration.
Check that the website is live, public and shows the same store name used in the samples.
Add the no-sharing line to the privacy policy and make sure the terms mention text messaging and the types of messages sent.
Make the website consent checkbox separate and unchecked, with frequency, rates, HELP and STOP wording beside it.
Photograph or scan the consent line on in-store paperwork so the provider can host it as evidence.
Pick the use case that matches what the store sends, including promotions if any will go out.
Write a description that names the store, the recipients, each message type and every opt-in method.
Prepare at least three sample messages with the store name and STOP language, using the full store web address instead of a link shortener.
Write the opt-in confirmation, HELP and STOP replies with the store name.
Agree internally that live messages will stay within what was registered, and route new message types through the provider first.

Item 1 is the one dealerships most often miss. A store may run three or four texting tools, and each one sends under its own registration, so one approved campaign does not mean every tool is covered.

How long 10DLC approval takes and what happens after

10DLC approval time varies by provider and by how complete the submission is. Amazon's setup guide says campaign approval is instant in most cases but can take up to four weeks. Plivo's 10DLC guide says carriers manually verify campaigns and that vetting takes about one to two weeks, and the Text Request help center says full approval can take several weeks, during which texts are marked undelivered. Plan new numbers and new tools with that window in mind, and expect a rejected campaign to restart the wait after it is corrected.

Approval is not the end of the work. Syniverse warns that live messages that drift from the registered content, purpose or frequency can lead to compliance reviews and suspension, and the SignalWire 10DLC campaign checklist advises not changing content once a campaign is approved and creating a new campaign when it must change. For a dealership, that means a store that registered only service updates should talk to its provider before sending a sales event blast from the same number.

Next steps for the person who owns dealership texting

The next step depends on where the store's registration stands today:

Not sure what is registered: ask each texting vendor for the brand name, use case and sample messages it filed, then compare them with the checklist above.
Campaign rejected: ask the provider for the exact rejection reason, fix that item and the related ones in the checklist, and resubmit once.
Adding a new texting tool: confirm how the new vendor registers the store and how it handles consent collected by other tools before any texts go out.
Registered and sending: keep message content within the registered campaign and put text consent on every form and repair order.

Shiftix Cloud's Unified Customer Inbox runs two-way SMS connected to the customer record. Its page says it automatically adds the required business name and opt-out disclosure to the first message to any contact and that STOP, UNSUBSCRIBE and equivalent keywords are recognized and honored permanently. The same page says carrier registration, consent and deliverability requirements still apply. The Shiftix Cloud integrations page lists Telnyx and Twilio as communications integrations. For the day-to-day side of texting, see the guides to missed call text-back for dealerships and dealership review request texts.

A 10DLC registration only gets texts delivered; what the store does with replies decides whether they turn into appointments and sales. The Shiftix Cloud Revenue Leak Audit is complimentary, carries no obligation and needs no software purchase. It looks at lead response, follow-up, conversion, customer retention, accountability and workflow, and Shiftix Cloud walks through the findings with the dealership.

Frequently asked questions

Does a toll-free number need 10DLC registration?

No, a toll-free number does not go through 10DLC registration, but it has its own approval. Twilio's documentation says toll-free numbers and short codes are not part of the 10DLC system. Plivo's guide says toll-free verification typically takes four to six weeks. A dealership choosing between a local number and a toll-free number should ask its provider which approval applies and what consent evidence each one needs.

Do dealership groups with several rooftops need separate 10DLC brands?

Dealership groups often need more than one brand, depending on how the rooftops are owned. Each brand is tied to a tax ID, so stores under different EINs register separately. Twilio's documentation says each tax ID can register up to five Standard or Low-Volume Standard brands, and campaigns for brands beyond that may be rejected without a valid business reason. Rooftops sharing one EIN should list their DBAs.

Does 10DLC registration make dealership texting legally compliant?

No, 10DLC registration is a carrier requirement and does not by itself satisfy federal or state texting laws. Carriers check that the campaign is described honestly and that consent is collected properly, but the dealership still has to follow the Telephone Consumer Protection Act, state rules on marketing texts and its own consent records. Dealership counsel should review consent wording and texting practices.

What happens to texts a dealership sends before 10DLC approval?

Texts sent before approval from an unregistered 10DLC number are likely to be blocked or filtered. Twilio's Conversations documentation says carriers block A2P traffic to US recipients from unregistered Twilio 10DLC numbers, and the Text Request help center says messages are marked undelivered until registration is approved. Staff should call or email in the meantime.