Operational SMS consent and call-to-action evidence

1. Step 1: During booking, an authenticated Hytch dispatcher speaks with the named passenger and confirms the mobile number that passenger controls.
2. Step 2: The dispatcher reads the exact verbal disclosure below and asks the passenger for a clear yes or no.
3. Step 3: Only after the passenger says yes may the dispatcher select the separate recording control, which is unchecked by default.
4. Step 4: Creating the order stores the consent timestamp, disclosure version, and booking-scoped evidence reference. Declining SMS never prevents the ride from being scheduled.

Opt-in method: verbal. Control state: optional-unchecked. The authenticated dispatcher may check the recording control only after the named passenger who controls the mobile number says yes.

If the passenger says no or cannot personally consent, the ride can still be scheduled without the consent record and no SMS is sent.

Hytch Ride would like to send you operational text messages about this scheduled ride, including a secure Hytch Rider app link and necessary confirmation, schedule, pickup, vehicle, driver, or cancellation updates. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. Consent is not a condition of purchase. Do you agree to receive these messages?

Review the direct Terms of Service and Privacy Policy.

Authenticated Hytch Admin example. This public example collects no data and cannot create a booking; it mirrors the private recording fields used after the passenger answers verbally.

Submit the mobile number in rider.phone and the consent record in rider.operational_sms_consent. The consent record must include:

• consented: true
• captured_at: ISO-8601 timestamp
• disclosure_version: hytch-operational-sms-v1
• evidence_reference: Unique booking-scoped consent evidence reference

Representative nested request payload:

{
  "rider": {
    "phone": "+12025550123",
    "operational_sms_consent": {
      "consented": true,
      "captured_at": "2026-08-13T12:00:00Z",
      "disclosure_version": "hytch-operational-sms-v1",
      "evidence_reference": "booking-consent-example-123"
    }
  }
}

After the named passenger verbally agrees, the authenticated dispatcher may record consent for this scheduled ride. The internal control is separate and unchecked by default:

Send this passenger operational text messages about this scheduled ride, including a secure Hytch Rider app link. Message and data rates may apply. Reply STOP to opt out.

Scheduled ride invitations contain one link on the Hytch-owned hytchride.com domain. The link reveals no ride details and requires sign-in with the invited mobile number.

Representative operational messages:

• Hytch Ride: Your organization-arranged ride booking is confirmed. Reply STOP to unsubscribe.
• Hytch Ride: Your organization-arranged ride booking pickup has changed. Reply STOP to unsubscribe.
• Hytch Ride: A ride is scheduled for Sep 25 at 2:30 PM. View securely: https://hytchride.com/i/EXAMPLE Reply STOP to unsubscribe.

Before an integration is enabled for operational SMS, Hytch must store the booking-scoped evidence reference and consent details with the applicable ride booking.

For every enabled integration, Hytch must check the recorded consent and suppression status again at delivery before sending an operational SMS.

Consent to operational ride updates never authorizes marketing or promotional messages.

For operational SMS support, email contact@hytchride.com.