If you build a DMS, a dealership CRM or a service scheduler, your customers keep asking for the same thing: let us text the people in your system. A dealer wants to confirm a service appointment, tell a buyer the car is ready and answer "is the Tahoe still available?" without leaving your screen. This guide is for the software company adding that feature, not the dealer using it.
The hard parts aren't the send call. They're the account structure (a group with twelve stores is not one sender), consent that comes from a lead form or a service desk, and what happens when a customer texts STOP. We'll walk through each, using Ready's API as the example.
Why dealership software is a good fit for texting
Dealerships live on short, time-sensitive messages. A lead who filled out a form at lunch expects a reply in minutes, and a service customer wants to know when the car is done, not a voicemail saying call back.
The messages your customers will want fall into a few groups:
- Sales: lead acknowledgement, test drive confirmation, "your trade appraisal is ready", follow-up after a visit.
- Service: appointment confirmation and reminders, "we found something, can we approve it?", "your vehicle is ready".
- Finance and delivery: documents needed, delivery day logistics, a thank-you with a review request.
- Recalls and outreach: notices tied to a vehicle, sent only to people who agreed to hear from the store.
For wording ideas your dealer customers can borrow, our post on SMS for car dealerships covers sales, service and speed-to-lead templates. This post is about the plumbing underneath.
One sub-account per store or dealer group
The most common mistake is putting every store on one number and one registration. Carrier registration (10DLC) is tied to a business, so a dealer group with separate legal entities, or stores that market under different names, shouldn't share a sender. If one store's campaign gets filtered, you don't want the rest to go quiet with it.
On Ready, each customer gets a sub-account with its own numbers and its own registration. You create one with POST /v1/sub-accounts, list them with GET /v1/sub-accounts, and file the brand and campaign through the registration endpoints. Registration is one line: $25 a month per customer for the brand and its first campaign, $20 a month for each extra campaign, and $2 a month per number. Most approvals take 2 to 7 days. Ready registers businesses with an EIN only, so a store operating without one can't register.
A reasonable mapping looks like this:
| Your customer | Sub-account | Numbers | Registration |
|---|---|---|---|
| Single-store dealer | One | One main number, maybe one for service | One brand, a campaign for customer care |
| Group with separate entities | One per entity | One or more per store | One brand per entity |
| Group under one legal entity | One, or one per brand name | One per store | One brand, campaigns by use |
Our sub-account guide for vertical SaaS onboarding shows how to script this at signup so a new dealer isn't waiting on your team. The docs cover sub-accounts and registration in detail.
Where the customer's consent comes from
In a dealership, consent usually shows up in one of three places: a web lead form with a checkbox, a signed buying or service document, or a customer who texts the store first. Each is the dealer's to collect, and your software is the right place to store it with the date, the wording and the source.
Here's the limit to design around. When your software sends with consent_attested: true, Ready records the attestation: who sent, to how many, and when. That's an audit trail of the sender's promise, not a per-customer consent record. Ready doesn't store each recipient's opt-in time, wording or page URL, so keep that in your own database. The one exception is a sign-up on a Ready-hosted opt-in page, stored per contact.
An API send without consent_attested still goes out until January 20, 2027 (UTC), with a warning and no attestation. From that date it's refused with 403 api_consent_attested_required. Set it now. Compliance is always the sender's responsibility, and the attestation is a record of that, not a shield. Our consent record schema post has a table layout that fits a dealership's three sources.
Sending a service or sales text
A single send is one call. Use the sub-account's key, an Idempotency-Key header so a retry after a timeout never sends twice, and E.164 numbers.
POST https://api.tryready.com/v1/messages
X-API-Key: <the dealer's sub-account key>
Idempotency-Key: <one UUID per message, reused on retry>
{"to": "+12125550199", "body": "Your car is ready for pickup. Service desk closes at 6.", "consent_attested": true} Leave from out and Ready picks the number: the one this contact already texts with, otherwise the primary number, or the one nearest their area code if the dealer turned on Local presence. That means a customer who texted the service desk gets the reply from the same number.
Each segment costs the Standard rate of $0.0075 plus a $0.0045 carrier fee. A service reminder under 160 characters is one segment. An emoji drops a segment to 70 characters, so a long message with a car emoji can be three. See how segments are counted before you set a template length limit in your UI.
Opt-outs, quiet hours and replies
Three behaviors matter for a dealer's reputation.
- STOP is honored automatically. A STOP always blocks that number in the sub-account that received it. Whether it also blocks the other stores in a group depends on an account setting, so check
GET /v1/opt-outs/:phonebefore you send from another tool. Show your users the opt-out state in the contact record so a salesperson doesn't wonder why a text was refused. Opted-out numbers are refused up front and not charged. - Quiet hours follow the recipient's area. An API text is held only if the window opens within 6 hours. Otherwise the API answers
409 QUIET_HOURS_BLOCKand your software sends again once the window opens. A reply to someone who texted the store in the last 24 hours can go out at any hour. - Replies need a person. "Is it still available?" arrives in the inbox and reaches your app through webhooks. Our inbound webhooks guide covers the pattern, and routing inbound texts to reps shows how to hand a reply to the salesperson who owns the lead.
An example with stated assumptions
Say your DMS has 200 dealer customers and the average store sends 1,500 texts a month, each one segment. That's 200 × 1,500 = 300,000 segments a month, billed at $0.0075 each plus the $0.0045 carrier fee. Replies your customers receive bill the per-segment rate plus a lower received carrier fee. Add $25 a month for each registration and $2 a month for each number. The assumptions are yours to change, and the pricing page has the exact figures. If you expect volume well beyond that, talk to us.
Decide early whether you pass costs through, bundle them or resell. Our pricing SMS in your SaaS plans post walks through the options.
What this doesn't cover
Ready doesn't replace your DMS data model. You still need to decide which events in a deal or repair order trigger a text, where the conversation shows up for the salesperson, and how a customer who bought a car and later moved is handled when a phone number is reassigned. Don't put sensitive financial details such as full account numbers in a message body. And a dealership that wants to text purchased lists cold should talk to its counsel, because cold contact is by phone and mail, while SMS goes to consented or replied leads.
Frequently asked questions
Do I need a separate registration for each store?
If the stores are separate businesses or use different brand names, yes. One registration is tied to one business, so a clean mapping is one sub-account and one registration per entity.
Can a salesperson text from their own phone?
Your software sends through the dealer's registered number, not a personal one. That keeps the conversation in your system and the sender consistent for carriers.
Can we use iMessage?
Ready offers a blue line for iMessage. See the iMessage API guide for what it does and doesn't do.
Next step
Pick one dealer, map it to a sub-account, store its consent source in your own schema and run a single test send from the API quickstart. Once that works, script the rest of onboarding and add the service reminder first, since it's the easiest message to get right.
Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.