10DLC for Auto Repair Shops: Who Really Needs It

Five o'clock at a two-bay shop is phone-tag hour. Three cars are done, three owners need telling, and nobody picks up an unknown number anymore. So the shop buys the obvious fix: software that texts "your vehicle is ready" the moment the job is closed, and a service reminder six months later. A few weeks in, an email arrives about brand registration, campaign use cases and a monthly fee, and suddenly there's a compliance project parked next to the Transit.

This is the workshop's version of something every US small business hits when it buys anything that texts customers. The general explainer — what 10DLC actually is, who has to register, what it costs, how long approval takes — is over here and worth ten minutes. None of it gets repeated below. This post is only the part that's specific to a business with a ramp.

A workshop's messages are exactly the traffic being policed

An auto shop doesn't send many kinds of message, but the ones it sends are the textbook definition of application-to-person traffic:

• Ready for pickup. Fired by the job being closed in the system, to whoever's car it is. Software, on a trigger, to a list.
• The approval mid-job. "Found the front discs lipped while we were in there — photo attached, another $180 fitted, say the word." Sent while the car is up on the ramp and the clock is running.
• The service reminder. Oil at intervals, the MOT or state inspection on its anniversary. Scheduled months ahead, by definition sent by a machine.

Here's the trap in that list: most of it isn't marketing, and shops assume the rules are about marketing. They aren't. 10DLC polices how a message is sent, not how reasonable it is. "Your car is ready" from a tool needs registration the same as any promotion — and unregistered traffic doesn't bounce, it silently stops arriving. The failure mode at 5pm is a customer who never got told their car was done, and no error anywhere telling you why.

The service writer's personal cell

Every trade has its wrinkle. Barbershops have chair rental — that one's covered here. A workshop's wrinkle is standing at the counter right now, texting a customer from his own phone.

It happens for a good reason: photos. The fastest way to get approval for extra work is a picture of the actual worn part with a price under it, and the fastest route for that picture is the service writer's personal cell. Compliance-wise it's fine — a human thumbing a message to another human isn't A2P traffic at all, no registration needed.

Everything else about it should worry you. That thread now holds the evidence that the customer approved $400 of extra work — on a personal handset the shop doesn't control. When the "I never agreed to that" dispute comes, the shop's defence is a screenshot an employee may or may not still have. When he moves on, the thread, the photos and the customer numbers go with him. And his number has quietly become the shop's real customer channel, unrecorded and unowned.

So shops end up with the worst fork in this whole subject: formalise the texting through a tool and inherit 10DLC, or leave it on personal phones and own no record of the conversations that authorise the work. Most shops never choose. They drift into the second and find out during a dispute.

The question before any form gets filled in

Who are these messages actually for? Not strangers — carrier SMS is built for reaching anyone with a phone number, and that reach is what the compliance file pays for. A workshop's messages go almost entirely to people whose cars have already been on the ramp. You'd be paying the full cost of reaching anybody, to reach people whose keys you have held.

Blinko takes the other route: messages travel through the app, not the carrier network. Blinko doesn't send SMS at all — broadcasts and direct messages go to customers who've connected with your shop by scanning your code, so there's no brand registration, no campaign use case, no per-message carrier fee, and no list of phone numbers sitting in your records needing to be looked after. The mid-job photo works the way the service writer's cell does — picture of the part, price, "say the word" — except the thread belongs to the shop, the approval is on record, and none of it walks out the door with an employee. Service and inspection reminders run as Automations on the same channel, and the quote-request flow collects make, model, mileage and photos before you price a job. Blinko has a free forever plan and a 0% platform fee.

The trade is the honest part: SMS reaches anyone; an app channel reaches people who've connected — a customer new to Blinko does a one-time free download, and existing users connect on the spot. For pickup notices and service cycles, where the audience is by definition people who've already been in, that's usually the audience you wanted. For the stranger at 8:30pm searching "brake repair near me", the answer isn't texting at all — it's being findable.

If you register anyway

Sometimes SMS is the right call — a reminder list built over fifteen years, customers who won't install anything. Fair enough; the general guide has the checklist. The workshop-specific parts:

1. Register what you'll actually send, separately. "Your vehicle is ready" and "20% off an air-con regas this week" are different use cases. Registering one and sending the other is how a shop's messages quietly get filtered.
2. Move the approvals off personal phones first. Registering the shop's number while the real conversations happen on the service writer's cell buys compliance for a channel nobody's using.
3. Keep the yes. The photo, the price, the customer's go-ahead — stored where the shop can find them in eighteen months. That record settles disputes; it's worth more than the registration.

The short version

10DLC applies to an auto shop the moment "your car is ready" comes out of software instead of somebody's thumb — operational or not. The registration is survivable. The real exposure is the thread on the service writer's personal phone: the one channel customers reliably answer, holding evidence the shop doesn't own, on a number that leaves when he does. Decide where that lives on purpose, before a dispute or a resignation decides it for you.

See how Blinko reaches customers →