Legal & Compliance
SMS Consent Policy
How Kurenai collects and records consumer consent before sending text messages.
Effective Date: June 15, 2025 · Applies to all restaurants powered by Kurenai AI
1. Overview
Kurenai powers AI voice receptionists for restaurants. When a caller asks about online ordering or the menu, our AI receptionist Luna may offer to send a text message with a direct link — but only after explicitly asking for and receiving the caller's verbal consent during the call.
No SMS is ever sent to a caller without this consent step. This policy describes exactly how that consent is obtained, what is sent, and how the consent record is stored.
2. The Opt-In Flow
The following sequence occurs on every inbound phone call where an SMS may be sent:
1
Caller Initiates
The caller expresses interest in online ordering, the menu, or a link — e.g., "I'd like to place an order" or "Can you send me your menu?"
2
Luna Asks for Consent
The AI receptionist explicitly requests permission before sending any message:
"I can send you our ordering link by text — would you like me to do that?"
In Spanish calls: "¿Le puedo enviar el enlace de nuestro menú por mensaje de texto?"
3
Caller Responds
The caller's response is captured via Twilio speech recognition. If the caller says yes (or any affirmative equivalent), consent is granted. If the caller says no, the URL is read aloud instead and no SMS is sent.
4
SMS Sent & Consent Logged
Upon affirmative response, the text message is sent and a consent record is written to our database containing the caller's phone number, Twilio Call SID, timestamp of consent, and message type.
No consent = No SMS. If the caller does not explicitly say yes, or if the system cannot determine a clear affirmative response, no message is sent. The URL is provided verbally instead.
3. What We Send
When a caller consents, they receive a single SMS containing only the restaurant's online ordering link. Messages are sent from a Twilio-provisioned number registered to the restaurant.
Example message:
"Here's the ordering link for Mayu Miami: https://mayumiami.com/menu — Reply STOP to opt out."
All messages include opt-out instructions. Callers may reply STOP at any time to be removed from future messages.
4. Consent Records
Every SMS consent event is stored in our database with the following fields:
- Caller phone number — the number that called and consented
- Call SID — Twilio's unique identifier for the call, which ties back to the full call transcript
- SMS type — the category of message sent (e.g.,
ordering_link)
- Consented at — UTC timestamp of the moment affirmative consent was captured
These records are retained for a minimum of 4 years and are available for audit upon request.
5. Message Frequency & Opt-Out
- Message frequency varies per call — typically one message per call session
- Reply STOP to opt out of future messages at any time
- Reply HELP for assistance
- Message and data rates may apply
- Carriers are not liable for delayed or undelivered messages
6. Regulatory Compliance
This consent flow is designed to comply with:
- TCPA (Telephone Consumer Protection Act) — verbal opt-in obtained prior to each message
- CTIA Messaging Guidelines — clear opt-out instructions included in every message
- Twilio A2P 10DLC requirements — consent collected and logged per carrier standards
- Florida Statute § 934.03 — callers are informed they are speaking with an AI system at the start of each call
7. Contact
For questions about this policy, consent records, or to request removal from our systems: