Technology · Messaging
One text has
four ledgers.
SMS feels like the simplest technology at the curb because every guest already knows how to use it. Behind that familiar screen sit carrier registration, a declared use case, a consent record, and usage priced by message segments.
The real cost
The provider invoice is only one line of the calculation.
A valet operator should know why a text was sent, who asked for it, how the recipient can stop it, and how much content traveled. That is not paperwork surrounding the message. It is the system that keeps the channel useful.
CTIA describes its Messaging Principles and Best Practices as voluntary industry best practices. They are not a federal regulation. Carriers and messaging providers still use industry programs and network policies to govern application-to-person traffic.
The four ledgers
What sits behind send
Registration and purpose come before volume
Identity
Who is sending
Business messaging programs associate traffic with a sender rather than treating every number as an anonymous pipe.
Purpose
Why it is sending
A retrieval update, a receipt, and a promotion are different conversations. Declare the actual one instead of borrowing a broader label.
Permission
Why this guest receives it
Record the action or relationship that supports the message and keep the copy aligned with that context.
Control
How the guest stops it
Opt-out handling must reach the sending system, not end as an unread reply at the stand.
→Primary source: CTIA Messaging Principles & Best Practices, reviewed August 23, 2026.
A message is not always one segment
Billing units depend on encoding and length. A long message or a character outside the basic alphabet can change how the text is divided by the network.
→Do not strip clarity to save a segment. First remove repeated greetings, legal filler that belongs behind a link, and status words the guest cannot act on. Message length and the characters used can affect how a message is split and charged. Confirm the applicable rates with your provider.
Price the conversation, not the outbound message
One retrieval can create several messages: confirmation, progress, ready status, receipt, and replies. The useful unit is the completed guest journey.
Count
Segments per journey
Measure the whole exchange, including automated replies and error paths, not only the first outbound text.
Watch
Delivery outcomes
A sent event is not proof the handset received the message. Keep delivery status separate from dispatch.
Review
Consent and opt-outs
Audit whether the content still matches the purpose the guest encountered when they supplied a number.
The operator's question
Can you explain any text after the shift ends?
A useful messaging log connects the guest action, message purpose, template version, segment count, provider outcome, and any opt-out. It makes both cost and guest experience reviewable without turning the valet into a compliance clerk.
The takeaway: SMS stays simple for the guest only when the operation takes the complicated parts seriously.
