Documented four-step dispatcher workflow used to capture verbal authorization and confirm ARK TMS system compliance before any driver receives SMS messages.
Dispatcher script → Broker checkbox → Consent logging → First SMS disclosures
ARK TMS operates under a B2B2C (Business-to-Business-to-Consumer) model where dispatchers act as authorized agents for their drivers. We enforce the four-step workflow below to confirm verbal authorization before any SMS is sent through Twilio.
1. Dispatcher Script & Driver Approval
During load assignment, the dispatcher reads the ARK-provided script verbatim and records the driver's audible confirmation. Consent is collected verbally—no SMS keywords or web forms are used.
Verbatim Script Dispatchers Must Read
"This load will use ARK TMS for tracking and communication. You will receive text messages to [driver phone number] including:"
"Standard message and data rates will apply. You can opt-out anytime by replying STOP to any message. Do you agree to receive these text messages for this load?"
Dispatcher must hear a clear "Yes" (or similar affirmative response) before proceeding.
Document immediately:
2. Broker Checkbox Attestation
Inside ARK TMS, the broker/dispatcher must check the consent checkbox that reads: "I confirm the driver approved ARK TMS SMS communications for this load." The checkbox is mandatory—SMS invitations cannot be sent until it is selected, and the attesting user ID is stored with the record.
3. Consent Logging & Audit Data
When the form is submitted, ARK TMS automatically logs: timestamp, dispatcher/broker user ID, driver phone number, carrier/organization ID, load reference, consent method (verbal), and script version.
These logs are stored in Supabase with encryption at rest and are exportable for auditors and carriers within minutes.
4. First SMS with Authorization Statement
After consent is logged, the first SMS reiterates that the carrier authorized the outreach and provides all required disclosures, including STOP instructions, terms, privacy, and support details.
FROM: ARK TMS
"ARK TMS: Carrier ABC confirmed you for load #12345. Login code: 458932 (expires in 10 min). Reply STOP to opt out. Terms: arktms.com/terms Privacy: arktms.com/legal/privacy-policy Support: support@arktms.com"
Every first message references the authorizing carrier/dispatcher, STOP instructions, a link to terms and privacy, and a support contact path.
A dedicated consent ledger preserves verbal authorizations for compliance.
Important Disclosures (Required by TCPA & Twilio):
Message Types You May Receive:
No marketing messages are ever sent. All communications are operational and directly related to your work with the freight carrier.
ARK TMS is a transportation management system used by freight brokers to manage loads and communicate with their contracted drivers. We operate under a B2B2C (Business-to-Business-to-Consumer) model where carriers and dispatchers act as authorized agents for their drivers. This page explains how verbal authorization is obtained through authorized agents before sending SMS messages to drivers and documents our compliance with TCPA and CTIA messaging standards.
Our verbal authorization process follows standard logistics industry practices where carriers and dispatchers act as authorized agents for their drivers:
When a carrier accepts a load assignment from a broker using ARK TMS, the dispatcher verbally confirms with their driver:
Verbal Confirmation Script:
"This load will use ARK TMS for tracking and communication. You will receive text messages to [driver phone number] including login verification codes, app download instructions, and load pickup/delivery confirmations."
"Standard message and data rates will apply. You can opt-out anytime by replying STOP to any message. Do you agree to receive these text messages for this load?"
Key Point: Dispatcher must hear an affirmative "Yes" before entering the driver into ARK TMS.
Immediately record driver name, confirmed phone number, consent time, and load reference.
The broker/dispatcher checks a required consent confirmation box in ARK TMS:
I confirm the driver has agreed to receive SMS communications for this load
Required Action: This checkbox cannot be bypassed. The system will not allow SMS sending without this confirmation.
ARK TMS automatically logs the consent with the following information:
Audit Compliance: These records are maintained in our database and available for audit upon request.
Only after verbal authorization is confirmed and logged, the driver receives their first SMS message:
FROM: ARK TMS
"ARK TMS: Carrier ABC confirmed you for load #12345. Login code: 458932 (expires in 10 min). Reply STOP to opt out. Terms: arktms.com/terms Privacy: arktms.com/legal/privacy-policy Support: support@arktms.com"
First Message Includes: Carrier authorization reference, STOP instructions, terms + privacy links, and live support contact details.
When obtaining verbal authorization from drivers, dispatchers and brokers should use clear, straightforward language. Below is our recommended script:
Recommended Script:
"This load will use ARK TMS for tracking and communication. You will receive text messages to [driver phone number] including:"
"Standard message and data rates will apply. You can opt-out anytime by replying STOP to any message. Do you agree to receive these text messages for this load?"
What to Cover:
Important Compliance Notes:
VERBAL CONSENT SCRIPT: Dispatchers inform drivers: "You'll receive text messages from ARK TMS with login codes for the driver app and updates for this load. These messages will go to [confirm phone number]. Standard message rates apply. You can opt-out by replying STOP. Do you agree to receive these messages?"
Driver must verbally confirm YES (or similar) before the number is added to ARK TMS. The broker/dispatcher then records the consent in ARK TMS, creating a timestamped audit record tied to that user ID.
Document the following immediately after consent:
Only after verbal confirmation is obtained and documented should the dispatcher add the driver's number to ARK TMS. This procedure aligns with logistics industry standards where carriers act as authorized agents for their drivers under DOT regulations and carrier agreements. No marketing messages are ever sent—only operational updates necessary for the load.
The following diagram illustrates the complete end-to-end consent collection and SMS delivery process:
1. Carrier Accepts Load Assignment
Business relationship established
2. Dispatcher Obtains Verbal Consent
Uses approved load-specific script covering phone, message types, STOP instructions, and confirmation of consent.
3. Dispatcher Opens ARK TMS
Navigates to "Add Driver" or "Invite to App"
4. System Shows Consent Checkbox
Required field: "I confirm verbal consent was obtained"
5. Validation Check
Is consent checkbox checked?
Error Message
Form blocked
Proceed
Continue to next step
6. System Logs Consent to Database
Timestamp, User ID, Phone, Load #, Consent Method
7. First SMS Sent to Driver
Includes carrier reference, OTP code, STOP instructions, terms/privacy, and support contact
8. Consent Record Stored
Available for audit (4+ year retention)
Key Compliance Points:
Our system includes a built-in consent confirmation mechanism that ensures dispatchers cannot send SMS messages without first confirming that verbal authorization has been obtained from the driver.
Screenshot of actual ARK TMS consent collection interface
Once verbal authorization is obtained, drivers may receive the following types of SMS messages:
Security codes for logging into the mobile app (e.g., "Your verification code is: 123456") - Most common message type
Initial message with app download link and setup instructions (sent after verbal authorization)
Critical operational notifications related to assigned loads and shipments
Support messages and assistance from the freight broker or ARK TMS support team
Note: No marketing messages are ever sent. All communications are strictly operational and directly related to the driver's work with the freight carrier.
Below are anonymized examples of actual SMS messages sent after verbal authorization is obtained:
Sent after dispatcher obtains verbal consent and confirms in ARK TMS
FROM: ARK TMS
"ARK TMS: Carrier ABC confirmed you for load #12345. Login code: 458932 (expires in 10 min). Reply STOP to opt out. Terms: arktms.com/terms Privacy: arktms.com/legal/privacy-policy Support: support@arktms.com"
10:15 AM
Note: First message references carrier authorization, OTP code, STOP instructions, terms, privacy, and a live support contact.
FROM: ARK TMS
"ARK TMS: Download the driver app: https://ark.app/download Login with your phone number to access your loads. Reply STOP to opt-out. Help: support@arktms.com"
10:20 AM
When driver logs into the app after initial setup
FROM: ARK TMS
"ARK TMS: Your verification code is: 123456. This code expires in 10 minutes."
2:15 PM
Note: OTP messages are user-initiated when the driver attempts to log into the mobile app.
FROM: ARK TMS
"Your verification code is: 789012. This code expires in 60 seconds."
3:20 PM
TO: ARK TMS
"STOP"
3:21 PM
FROM: ARK TMS
"You have been unsubscribed from ARK TMS SMS messages. No more messages will be sent. Reply START to resubscribe."
3:21 PM
ARK TMS maintains comprehensive records of all verbal authorization consents obtained through our platform. These records are available for audit upon request and comply with TCPA recordkeeping requirements.
Timestamp
Exact date and time when consent was confirmed in the system
Authorizing Party
Broker/dispatcher user ID, name, and organization
Driver Phone Number
Phone number authorized to receive SMS communications
Load Reference
Associated load number and shipment details
Below are examples of actual consent records stored in our database:
Note: Personal information has been redacted for privacy. These records are representative samples showing the data structure and fields logged for each consent event.
ARK TMS operates under a B2B2C (Business-to-Business-to-Consumer) model that is standard in the logistics and transportation industry. This model involves three parties:
Provides transportation management software and facilitates SMS communications
Acts as authorized agent, obtaining verbal consent from their drivers
Independent contractor or employee who receives SMS communications
All drivers receiving SMS messages have an established business relationship with the freight broker or carrier using ARK TMS. The carrier/dispatcher acts as an authorized agent with the legal authority to:
Operational Nature of Messages: All SMS communications are strictly operational in nature and directly related to the transportation services being provided. This includes authentication for secure app access, load status updates, and critical account notifications. No marketing or promotional messages are ever sent.
Drivers can opt out of SMS communications at any time by:
Upon receiving STOP, we immediately cease all SMS communications to that phone number. The opt-out is processed automatically and takes effect within seconds.
Drivers who previously opted out can re-subscribe by replying START, UNSTOP, or YES to resume SMS communications. Note that re-subscription requires explicit consent again.
Message frequency may vary.
This includes app setup instructions, OTP codes, account notifications, and customer care communications. Messages are sent only when necessary for account operations and security.
One-time message sent only after verbal authorization is obtained by carrier/dispatcher
Sent each time driver logs into the mobile app (user-initiated, most common message type)
When verbal authorization is obtained for SMS communications, we collect and store:
Your data is NOT shared with third parties for marketing purposes.
Phone numbers and SMS data are used solely for operational purposes (delivering messages, authentication, account management). We do not sell, rent, or share personal information with marketing companies or data brokers. Data is only shared with:
For complete information about our data practices, please review our Privacy Policy.
For complete information about our policies and terms:
Note: SMS consent is separate from our general Terms and Conditions. Verbal authorization is obtained by your carrier/dispatcher before any SMS messages are sent. You retain the right to opt-out at any time by replying STOP.
For questions about SMS consent or to request removal from our SMS communications:
ARK TMS LLC complies with all applicable messaging regulations and industry standards:
Last updated: November 29, 2025
ARK TMS LLC | This page documents our SMS consent process for Twilio verification