Tezlo Arrival Texts

Consent starts inside the app, with this confirmation. No one texts Tezlo first, and there is no keyword to join: Tezlo never sends a message that a customer did not request and confirm in the app.

Sender. The Tezlo platform (Altrooz, Inc. dba Tezlo), on behalf of the Tezlo user who asked for the message. Recipient. A person the user names from their own phone contacts, for example a family member expecting them. Why. A one-time, transactional arrival notification: the user’s first name and estimated arrival time, generated by the Tezlo software from the car’s live route. The message is not a conversation between individuals and is not a subscription: there is no recurring schedule, and each message requires a new request.

1. Step 1. SMS consent is optional and separate from sign-up.
   Creating a Tezlo account does not ask for, and does not require, consent to text messages. A customer can use every part of Tezlo without ever agreeing to receive a text. No form, checkbox or keyword collects SMS consent. The program itself is described in section 17 of the Terms of Service and the Privacy Policy; consent is given later, per message, in step 3.
2. Step 2. The user asks for a specific message.
   Inside the app’s hands-free assistant the user says, for example, “text Rob my ETA”. Nothing is sent at this point.
3. Step 3. The app reads the exact message back, with the program disclosure, and asks for consent.
   The app shows and speaks the message it is about to send and asks “Send it?”. The first time a customer requests an arrival text, the app speaks and displays this disclosure (the verbal opt-in script) before the question:

   “Tezlo will send Rob one arrival text from the Tezlo number: Rob is on the way, arriving around 5:40. You get up to 10 arrival texts a day, only when you ask. Message and data rates may apply. Rob can reply STOP to cancel or HELP for help. Send it?”

   The message is sent only if the user answers with an explicit “yes”; “no”, silence, or any other reply leaves it unsent. After the first yes, later requests show the short read-back: “Text Rob: Rob is on the way, arriving around 5:40. Send it?” The screen below, captured from the Tezlo iOS app, is that read-back step; on first use the disclosure quoted above is spoken and shown in the same place.
4. Step 4. One message is delivered.
   The recipient receives the message shown, from the Tezlo number, ending with the brand name and the opt-out instruction. The user can send at most ten arrival texts per day.

Captured from the Tezlo iOS app (version 1.1) while the app reads the message back and waits for the user’s yes:

🔊

Speaking…

Text Rob: Rob is on the way, arriving around 5:40. Send it?

Stop

Not affiliated with Tesla, Inc.

Left: the screenshot. Right: the same screen reproduced in text. The arrival time appears when the car has an active route; otherwise the message reads “Rob is on the way.”

• “Rob is on the way, arriving around 5:40. Sent via Tezlo. Reply STOP to opt out.”
• “Rob is on the way, arriving around 12:15 (running late). Sent via Tezlo. Reply STOP to opt out.”
• “Rob is on the way. Sent via Tezlo. Reply STOP to opt out.”
• “Rob is on the way, arriving around 5:40 (I’m bringing a bottle of wine). Sent via Tezlo. Reply STOP to opt out.” - a short note the user dictated
• “Rob is on the way, with a charging stop first. Sent via Tezlo. Reply STOP to opt out.”

No links, phone numbers, prices, or promotions are ever included.

A recipient can stop receiving Tezlo texts at any time by replying STOP to any message; Tezlo sends one confirmation and nothing further, and the number is blocked for every future request from any Tezlo user. Reply HELP for assistance, or contact support@tezlo.app. Message frequency varies with the user’s requests, up to 10 per day; Msg & data rates may apply.

Mobile phone numbers and text-messaging consent are used only to deliver the message the user requested. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties. See the Privacy Policy and Terms of Service, section 17.