Skip to content
R.ai
Legal · Messaging & SMS Consent

Messaging & SMS Consent Policy

This policy describes the text-messaging (SMS) program operated by REVAAI LLC (d/b/a R.ai), a New Jersey limited liability company doing business as “R.ai” (“R.ai,” “we,” “us”). It documents the complete opt-in experience — who sends the messages, who receives them, why, exactly how consent is obtained on every path, and how to opt out at any time. It is published so that anyone — including a customer, a restaurant, or a carrier / messaging reviewer — can verify our consent flow.

Effective date: July 16, 2026. Applies to: all SMS text messages sent by R.ai on behalf of the restaurants that use the Service, and all operational-alert text messages sent to restaurant owners and staff.

1. Who sends, who receives, and why

1.1 Who sends.Messages are sent by R.ai (REVAAI LLC) through its telephony subprocessor, Twilio, on behalf of the individual restaurant a person contacted or ordered from. The restaurant is the business the customer is doing business with; R.ai is the technology provider that operates the phone agent and the messaging on the restaurant's behalf.

1.2 Who receives. There are two audiences:

1.3 Why we send (message categories). All messages are transactional and relate to a specific order, reservation, or the operation of the restaurant:

1.4 What we never do. R.ai does not send marketing or promotional text messages without separate, explicit opt-in. Mobile phone numbers collected for messaging are never sold, and are never shared with third parties or affiliates for their own marketing purposes. A number is shared only with our messaging subprocessor (Twilio) for the sole purpose of delivering the messages described above. See our Privacy Policy.

2. How consent is obtained — every opt-in path

Consent to receive text messages is captured in exactly two ways, depending on whether the person is a customer of the restaurant or an operator of it. Both paths are described in full below, and there are no others.

We do not use keyword opt-in.R.ai never publishes, advertises, or instructs anyone to text a keyword to a number in order to subscribe. No call-to-action to “text JOIN” or any similar keyword appears in our product, on our website, or in any restaurant material. Inbound keywords are honored only in the outbound direction — STOP to revoke and HELP for help, as carriers require — never as a way to join.

2.1 Verbal opt-in (customer places a phone order with the AI)

A customer calls the restaurant and places an order or books a reservation with the R.ai phone agent. During the call, the customer provides their mobile number and agrees, out loud, to receive text updates about that order or reservation (for example, the order confirmation, a payment link, and the pickup-ready notice). The agent captures the mobile number and the customer's spoken agreement, and R.ai logs the consent with a timestamp. Only numbers that have affirmatively agreed on the call are texted.

2.2 Web opt-in (restaurant owners and staff)

This path is for the business users who operate the restaurant, not for its customers. It sits behind authentication: a restaurant owner creates an account at joinrai.com/sign-up, verifies their email, and signs in. Only after they are logged in does the setup flow present the opt-in, at joinrai.com/setup/2(“Owner & staff”). The step-by-step sequence is:

  1. Create an account and verify email at joinrai.com/sign-up.
  2. Sign in. Unauthenticated visits to /setup/2 are redirected to /sign-in.
  3. On the “Owner & staff” step, enter the owner mobile number in the Owner cell field.
  4. Tick the separate SMS consent checkbox, which is unchecked by default.
  5. Continue. The choice is stored against the authenticated account.

The checkbox agrees to operational alerts about their own restaurant (new orders, callback requests, and daily summaries). Entering a phone number alone never opts anyone in — only checking the box does, and the box is optional: the form submits and the account is fully usable if it is left unchecked. The checkbox presents the full disclosure (message frequency varies; message and data rates may apply; reply STOP to opt out, HELP for help) with links to the Privacy Policy and Terms of Service. Owners and staff can opt out at any time by replying STOP.

Because this page is behind a login tied to a paying restaurant account, it cannot be reached by a reviewer without credentials. Screenshots of the authenticated flow are provided with our campaign submission, and we will supply reviewer test credentials on request.

3. Opt-in evidence — what each flow looks like

The figures below document the two opt-in paths described in Section 2 exactly as they appear in the product, using the production message copy from our codebase. They are published so a carrier or messaging reviewer can see the complete consent experience without placing a live order.

Figure 1 — Verbal opt-in on a recorded call. The agent asks the consent question out loud before any text is promised; the answer is logged with a timestamp on the same opt-out flag that gates every customer SMS. A decline means no texts are sent. Schematic of the live product flow; exact production copy and field names shown, timestamps shown as placeholders.
Figure 2 — Web opt-in (restaurant owners & staff). A separate consent checkbox, unchecked by default, sits next to the phone field in the signup form; submitting a phone number alone never opts anyone in. Illustration of the live product flow; exact production copy shown.

4. Required disclosures

These disclosures apply to every message program described above:

5. Sample messages

The following are representative of the transactional messages R.ai sends. Restaurant name, totals, and times are filled in per order or reservation.

6. How to opt out (STOP)

You can opt out of R.ai text messages at any time by replying STOP to any message you receive. Your opt-out is honored immediately: it stops future messages to your number, and no further messages will be sent unless you opt in again (for example, by texting or placing a new order). You may also reply UNSUBSCRIBE, CANCEL, END, or QUIT.

7. How to get help (HELP)

For help, reply HELP to any message, or email ezra@joinrai.com. Replying HELP returns a short description of the program and a way to reach support. If your question is about a specific order or reservation, you can also contact the restaurant directly.

8. Privacy and terms

Mobile information — including any phone number collected for messaging — is handled as described in our Privacy Policy, and use of the Service is governed by our Terms of Service. In short: mobile opt-in information and phone numbers are never sold and are never shared with third parties or affiliates for their marketing; numbers are shared only with our messaging subprocessor (Twilio) to deliver the messages described here.

9. Contact

Questions about this Messaging & SMS Consent Policy can be sent to ezra@joinrai.com, or by mail to REVAAI LLC, 459 Warwick Avenue, Teaneck, New Jersey 07666.

© 2026 REVAAI LLC d/b/a R.ai. Message and data rates may apply. Message frequency varies. Reply STOP to opt out, HELP for help.