The text thread the owner actually reads.
Driver dispatched, driver on scene, vehicle hooked, lot arrival, release ready, balance confirmed. The owner knows where their vehicle is at every stage, from a dedicated Twilio 10DLC number with your area code. The dispatcher stops answering the same six questions by phone.
North County Recovery — dispatcher to owner, over 94 minutes.
Sarah’s Civic clipped a guardrail on the 101. North County Recovery’s dispatcher opened the thread the moment Mike was dispatched; the whole conversation ran through Twilio on a dedicated 10DLC number. Here’s what Sarah saw on her phone, next to the use-case list the dispatcher never has to type by hand.
North County Recovery
+1 (760) 555-0144
Today 7:14 PM
Templates that fire themselvesDispatcher edits once at onboarding
| Use case | Trigger | Delivery |
|---|---|---|
| SMSDriver dispatched“Driver [name] dispatched, [class], ETA [min].” | CRM: Open → Hooked | 98.4% |
| SMSDriver on scene / hooking“Driver on scene, hooking now. [Vehicle verify].” | Driver app: On scene | 99.1% |
| MMSHook condition photoPre-tow photo attached, cuts damage-claim disputes 44%. | Driver app: Hooked | 97.2% |
| SMSLot arrival“Vehicle secured at lot [address]. Hours [X–Y].” | CRM: En route → Awaiting release | 98.9% |
| SMSRelease ready“Release ready. Balance $[amt]. Insurer [name] notified.” | CRM: paperwork complete | 98.6% |
| SMSLien expiry warning“Lien letter mailing in 72hrs. Last window to settle.” | State lien schedule + Day N | 97.8% |
Everything in the package.
- Dedicated Twilio 10DLC number with your area code, provisioned and verified
- Carrier registration (The Campaign Registry) with your dispatch use case documented
- Six baseline templates: dispatched, on scene, hook photo (MMS), lot arrival, release ready, lien expiry
- MMS enabled with pre-tow condition photo attached from the driver mobile app
- Spanish-language variant of every template, selectable per owner at hook
- STOP, HELP, and START auto-responses per TCPA, logged for compliance
- Two-way thread view: dispatcher sees owner replies in a shared inbox, same number every time
- Nora AI intake handles replies outside dispatcher hours, escalates real-time scene questions
- Monthly deliverability report: open rates (where carrier reports), opt-outs, carrier reputation score
- Twilio consent artifact logged with every opt-in and attached to the dispatch CRM file
The owner texts, the dispatcher sleeps, the lien letter still goes out on time.
An owner who gets a dispatched-driver SMS at 2:14 a.m. does not call back at 2:16 to ask where the truck is. That phone call never happens, and it’s the dispatcher’s most interruptible one. SMS turns an inbound-call-driven operation into a status-notified one. Different pace entirely.
Driver-arrival SMS cuts “where is my truck” calls by 71%.
Operators who switch from phone-only status to Twilio SMS see inbound dispatch calls drop sharply inside the first week. The dispatcher stops repeating the same ETA across three callers.
MMS pre-tow condition photos cut damage-claim disputes by 44%.
Owner sees the Civic at hook, bent fender already bent. When they claim later that we did it, the MMS timestamp sits in their own Messages app. Insurers accept it as proof.
10DLC with your area code reads as local, not spam.
Shortcodes and shared pools get filtered by Verizon and T-Mobile at the carrier level. Dedicated 10DLC with proper Campaign Registry registration delivers at 98 percent plus. We’ve measured.
Nora picks up the 2 a.m. reply so the dispatcher doesn’t.
Owner texts “When does the lot open?” at 3:11 a.m. Nora answers in 9 seconds, pulled from your dispatch CRM. If the owner asks a scene-timing question Nora can’t handle, the on-call dispatcher gets paged. Everything else, Nora closes.
What dispatchers ask before signing.
Why Twilio and not another SMS tool?
Twilio runs on dedicated 10DLC numbers with real deliverability, carrier reputation we can track, and MMS without carrier filtering. We standardized on Twilio across every Collision Bureau client. Shared pools and gray-market gateways get your messages dropped by carriers at the worst time.
Does the owner see our number or a shortcode?
A dedicated 10DLC long code with your area code when available. Owners reply, dispatchers see it in a shared inbox, same number every time. Shortcodes don’t allow replies and read like spam.
What are the standard use cases?
Driver dispatch, scene arrival, hooked, lot arrival, release ready, lien expiry, payment confirmation, Google review request. Each with a template the dispatcher edits once at onboarding, never again.
Can we send MMS photos of the hooked vehicle?
Yes. The driver sends a photo from the Collision Bureau mobile app; it attaches to the SMS thread so the owner sees the exact condition of the vehicle at hook. Reduces damage-claim disputes by about 44 percent.
How is SMS consent captured?
At hook, through the Dispatch Ready consent artifact. Owner signs on the driver’s tablet or texts YES to the first SMS. STOP and HELP replies are auto-handled per TCPA. We log every opt-in and opt-out.
What happens when the owner replies at 3 a.m.?
Replies route to Nora, our AI intake, who answers routine questions (balance, lot hours, pickup process) and escalates to the on-call dispatcher only when it is a real-time scene question. Nothing stays unread until morning.
Services that pair well.
A thread the owner reads. A dispatcher who stops repeating herself.
Pick a plan. Twilio 10DLC provisioned inside a week, templates live by day 10, first delivery report at day 21.