SMS opt-in & consent flow

Odomotive collects SMS consent through two distinct paths. Both are described in full below.

1. Account owner web opt-in. The fleet owner who signs up at odomotive.com opts in by checking an unchecked-by-default consent box during onboarding.
2. Driver SMS double opt-in.When the account owner adds a driver’s mobile number to a vehicle, the driver receives one prompt and must reply YES before any further messages are sent.

No third party can add a phone number on someone else’s behalf, and we send no messages to unconfirmed numbers other than the single double opt-in prompt above. No marketing or promotional messages are sent on this campaign — ever.

Where it lives: https://odomotive.com/onboarding/alerts (authenticated; reached after sign-up and connecting a telematics provider). The same checkbox is also available, with identical wording, at https://odomotive.com/dashboard/settings so a user can opt back in after a STOP.

Mechanism: the user enters a U.S. mobile number in E.164 format, picks a timezone, and must check a consent box that is unchecked by default. The “Save and finish” button is disabled until the box is checked — there is no path to enrollment that doesn’t pass through this affirmative click.

Audit trail: the opt-in timestamp, the version identifier of the disclosure shown, and the authenticated user ID are written to our users table (sms_opted_in_at, sms_consent_version). Twilio’s opt-in confirmation message is sent automatically on the same request.

What the user sees

Below is the exact UI rendered on the Alerts step, reproduced with the same component the live form uses (the disclosure text is imported from the same source file — it cannot drift).

Verbatim consent text

Opt-in confirmation SMS

Immediately after the user checks the box and submits, this SMS is sent to the number provided:

Why this path exists:a fleet owner may add a driver’s mobile number so the driver receives only the limited operational alerts that apply to the truck they drive (booking heads-ups, ready-for-pickup confirmations). The driver has not personally interacted with our website at that point, so we never message them without first obtaining their own affirmative consent over SMS.

The one consent prompt

The first — and only — message we send to a newly added driver number is this prompt. No marketing message, no promotional message, nothing else precedes or accompanies it:

What we do based on the reply

• Driver replies “YES”→ we store the timestamp, the verbatim reply text, and the Twilio message SID to driver_consents, and the driver becomes eligible for operational alerts. We send a confirmation:
  Odo: You're confirmed. We'll text you when your truck is booked and when it's ready. Reply STOP anytime to opt out.
• Driver replies “STOP” (or STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT) → the number is permanently opted out. No further messages are sent.
• Driver does not reply→ the number stays in a pending state and receives no further messages. We do not retry, follow up, or send anything else until and unless the driver replies YES on their own initiative.

Audit trail

Every driver consent event is logged with: the phone number, the fleet that initiated the prompt, the timestamp the prompt was sent, the version of the disclosure shown, the Twilio message SID, and (if applicable) the timestamp and verbatim text of the YES reply, or the timestamp and reason of any opt-out. Records are retained for the life of the account and for at least four years thereafter, consistent with TCPA defense practice.

Once a recipient has opted in, these are the kinds of messages we send. They’re always tied to a specific telematics-driven event (a fault code firing, a booking being made on the account’s behalf, a vehicle returning from the shop) or to a reply the recipient sent us. No marketing or promotional content is ever sent on this campaign.

Urgent fault alert (account owner)

Sent the moment a critical fault code fires on a connected vehicle. The recipient replies YES to authorize Odo to book service, or SKIP to dismiss.

Booking heads-up (driver)

Sent to a previously confirmed driver after the fleet owner books service on the vehicle they drive. Transactional — no further action required.

Recipients can opt out at any time by replying STOP. STOP is honored deterministically by the inbound webhook ahead of any AI processing — it always succeeds even if the agent backend is offline. See the next section for the verbatim HELP and STOP replies.

HELP and STOP are handled deterministically at the entry point of our inbound webhook, ahead of any AI processing, so they always succeed regardless of the state of the rest of the system.

HELP reply (verbatim)

STOP acknowledgment (verbatim)

In addition to STOP, we honor the standard variants: STOPALL, UNSUBSCRIBE, CANCEL, END, and QUIT. A user who has opted out can opt back in by replying START or UNSTOP, or by re-checking the consent box in their dashboard settings page.

• Message frequency varies— stated in the opt-in disclosure, the welcome SMS, the HELP reply, and Terms §6.
• Message and data rates may apply— same surfaces as above.
• Reply STOP to opt out, HELP for help— same surfaces as above, and the keywords are honored deterministically by the inbound webhook.
• Mobile information is not shared with third parties or affiliates for marketing or promotional purposes — Privacy Policy §4 (verbatim CTIA-required block).
• Carriers are not liable for undelivered or delayed messages — Terms §6.

For any question about Odomotive’s SMS program, opt-in evidence, or carrier compliance:

PathMarkr LLC (d/b/a Odomotive)
Franklin, Tennessee, USA
justin@odomotive.com