Last updated 2026-10-20
ReputeAI runs two separate, independently-consented SMS programs. This page documents both: how each collects consent, the exact wording used, and what happens on a yes, a no, or an unclear answer. See also SMS Terms & Consent and Privacy Policy.
Appointment, reservation, or takeout-order confirmations — sent to the customer, consented to verbally on the call, one at a time.
New-order alerts sent to the restaurant's own number — consented to once, by the business owner, when they turn the feature on.
Sent to the customer, after ReputeAI's AI phone assistant confirms a booking or a takeout order on a live call. Consent is asked verbally, by voice, on that same call — never assumed from caller ID, and never asked more than once per call.
Spoken right after the appointment or table reservation is confirmed:
"Your appointment at [business name] is confirmed. Would you like ReputeAI, [business name]’s booking assistant, to send a one-time text confirming these details? Message and data rates may apply — reply STOP to opt out, HELP for help. Would you like that confirmation text?"
A deliberately distinct, order-specific wording — spoken right after a takeout order is confirmed, never blended with appointment language:
"Your order at [business name] is confirmed. Would you like ReputeAI, [business name]’s booking assistant, to send a one-time text confirming these details? Message and data rates may apply — reply STOP to opt out, HELP for help. Would you like that confirmation text?"
In both scripts, "[business name]" is replaced with the real business the caller just did business with — the assistant always identifies ReputeAI by name, names that business as who the text is actually from, states this is a one-time text, discloses message/data rates, and gives STOP/HELP instructions, in the consent step itself.
Consent for both scripts above is collected entirely by voice, on the call itself — there is no web page, form, or checkbox involved in collecting it. The caller never leaves the phone call.
A simulated call flow showing the consent step in full context — the moment right before it, the consent question itself, the caller's answer, and what the assistant says next:
Simulated — this reproduces the live system's exact wording to show the full flow clearly, not a recording of one specific call.
Outcome: consent recorded as yes, with a timestamp and the script version spoken — the one-time confirmation text is sent.
For context, not as a substitute for the simulated flow above: this is the consent portion of an actual live call to Sweet Magic Indo-Chinese Restaurant's real phone number (the caller's name and full phone number are not shown here). This call was for a takeout order, so the order-specific script was used:
Outcome: consent recorded as yes, with a timestamp and the script version spoken — the one-time confirmation text was sent to the real number on that call.
(Simulated — reproduces the live system's exact wording to show the no-path clearly.)
Outcome: consent recorded as no. No text is sent. The assistant does not ask again on this call.
(Simulated — reproduces the live system's exact wording to show the unclear-path clearly.)
Outcome: an unclear or off-topic reply is never treated as a yes. The system only records consent — and only ever sends a text — on an explicit, affirmative answer to that specific question. Silence or a dropped call before an answer leaves consent unrecorded, and no text is sent.
The real one-time text sent after the "yes" above:
"You're booked at Sweet Magic Indo-Chinese Restaurant: Paneer Starters x1 (Medium), Hakka Noodles x1 (Medium), Chicken Dum Biryani x1 (Medium) — ready for pickup at [time]. See you then! Reply STOP to opt out, HELP for help."
Each booking or order stores: whether consent was given (yes / no / not yet asked), the exact timestamp of that answer, and which version of the consent script was spoken at the time. A confirmation text is sent only when that record is a real "yes" — enforced server-side, not just in the AI's own instructions.
A separate, simpler program: when a restaurant enables "Send order to your restaurant" → "Text the order to a number" in their ReputeAI dashboard, their own phone receives a text every time a new takeout order comes in. This is a config-time consent, not a per-call one — valid here specifically because the person consenting (the business owner, in their own account settings) is the same person who receives the text. It is never used to text a customer.
This checkbox is strictly optional, the same as every other setting in the dashboard — an owner can run their whole account, including every other workflow step, without ever touching it. It is never a precondition for using ReputeAI. The only thing it gates is this one specific text message program: in Appointments → Setup → Workflow, enabling "Text the order to a number" shows this checkbox, unchecked by default, with this exact text shown directly beneath it:
Leaving it unchecked simply means this one notification program stays off — nothing else about the account is affected. If the owner does check it and save, that single action is the explicit, affirmative consent for this program specifically: the business name, the message purpose, and the disclosures above are all present on this same step, not only on a separate policy page.
Example of what the owner's phone actually receives:
"New order for pickup at [time], [customer name] (no phone): Paneer Starters x1 (Medium), Hakka Noodles x1 (Medium), Chicken Dum Biryani x1 (Medium)"
The business's own workflow settings store: whether consent was given, the exact timestamp, which team member gave it, and which version of the disclosure text was shown. The server re-checks this record before every single send — not just at setup time — so a text is never sent to a number that hasn't given real consent.