SMS Marketing Consent - Proof of Opt-In Collection

Last updated: January 16, 2026

Purpose of This Page

This page demonstrates to regulatory authorities (including Twilio, CTIA, and FCC) how TableTalk obtains express written consent for SMS marketing messages in compliance with TCPA regulations. All consent methods shown below are actively used in our production systems.

How We Collect SMS Consent

TableTalk and our restaurant partners collect SMS marketing consent through three compliant methods. All methods include required TCPA disclosures and opt-out instructions.

Method 1: Verbal Consent During Phone Reservations

When customers call to make a reservation using our Retell.ai voice AI agent, they are asked if they would like to receive promotional text messages. Consent is only recorded when the customer verbally agrees.

AI Agent Script (Verbatim)

Agent Question:

“Would you like to receive exclusive offers and updates from [Restaurant Name] via text message? You can unsubscribe at any time by replying STOP.”

Customer Response (Affirmative):

“Yes” / “Sure” / “Okay” / “Yeah”

Agent Confirmation:

“Great! You'll receive promotional texts at this number. Standard message and data rates apply.”

Consent Record Stored in Database

{
  "phone_number": "+14075551234",
  "restaurant_id": "jazz-tastings",
  "marketing_consent": true,
  "consent_method": "verbal_during_call",
  "consent_date": "2026-01-16T15:30:00Z",
  "consent_call_id": "call_abc123",
  "consent_source": "reservation_call",
  "consent_agent": "Retell AI Agent"
}

All verbal consent records include the Retell.ai call ID for audit trail purposes. Call recordings are retained for 90 days.

Method 2: Website Widget Opt-In Checkbox

Our reservation widget (embedded on restaurant websites) includes an optional checkbox for SMS marketing consent. The checkbox is unchecked by default and includes all required TCPA disclosures.

Visual Example of Opt-In Checkbox

Complete Your Reservation

Screenshot: TableTalk reservation widget with SMS consent checkbox (highlighted in yellow)

Exact HTML Implementation

<label class="flex items-start gap-3">
  <input
    type="checkbox"
    name="sms_consent"
    value="yes"
  />
  <span>
    I agree to receive promotional text messages from
    [Restaurant Name]. Message frequency varies.
    Message and data rates may apply. Reply STOP to opt out.
    Reply HELP for help.
    <a href="/legal/sms-terms">SMS Terms</a>
  </span>
</label>

Consent Record Stored in Database

{
  "phone_number": "+14075551234",
  "restaurant_id": "jazz-tastings",
  "marketing_consent": true,
  "consent_method": "web_checkbox",
  "consent_date": "2026-01-16T15:30:00Z",
  "consent_ip_address": "192.168.1.1",
  "consent_source": "reservation_widget",
  "consent_user_agent": "Mozilla/5.0..."
}

Method 3: Double Opt-In (Enhanced Security)

For customers who opt in via web checkbox, we optionally send a confirmation SMS requiring a “YES” reply to activate marketing messages. This provides the highest level of consent verification.

Three-Step Confirmation Flow

1

Customer checks consent box on website

Checkbox checked → Phone number submitted
2

System sends confirmation SMS

Jazz Tastings: Reply YES to confirm you want to receive exclusive offers & updates via text. Msg & data rates may apply. Reply STOP to cancel.

3

Customer replies “YES” → Consent confirmed

Welcome to Jazz Tastings VIP texts! Get exclusive offers, event updates & birthday perks. Reply STOP anytime to opt out. HELP for help.

Required TCPA Disclosures

Every consent method includes the following disclosures as required by TCPA regulations:

✓ Message Frequency

“Message frequency varies” or specific frequency stated

✓ Cost Disclosure

“Message and data rates may apply”

✓ Opt-Out Instructions

“Reply STOP to opt out”

✓ Help Instructions

“Reply HELP for help”

✓ Terms Link

Link to full SMS Terms & Conditions

✓ Business Identification

Restaurant name in every message

Opt-Out Mechanism

Customers can opt out at any time by texting STOP (or UNSUBSCRIBE, CANCEL, END, QUIT) to any message. Opt-outs are processed immediately and automatically.

Supported STOP Keywords

STOPSTOPALLUNSUBSCRIBECANCELENDQUIT

Automated Opt-Out Process

  1. Customer texts “STOP” to any TableTalk message
  2. Twilio forwards message to our webhook endpoint
  3. Backend immediately creates opt-out record with timestamp
  4. All future marketing messages are blocked
  5. Twilio sends automatic confirmation: “You have successfully been unsubscribed...”
  6. Opt-out is logged in consent audit trail

Processing time: < 1 second. Transactional reservation messages (confirmations/reminders) continue as they are not affected by marketing opt-outs.

Consent Record Retention

All consent records are stored in Google Cloud Firestore with the following data retention policy:

  • Consent records: Retained for 7 years (TCPA requirement)
  • Opt-out records: Retained indefinitely (to prevent future messaging)
  • Call recordings (verbal consent): Retained for 90 days
  • Audit trail: All consent changes logged with timestamps

Compliance Summary

✓ TCPA Compliant

  • • Express written consent obtained
  • • Clear opt-out mechanism (STOP)
  • • Consent records maintained
  • • No auto-dialers used

✓ CTIA Best Practices

  • • Business identified in all messages
  • • Messages sent 8 AM - 9 PM only
  • • HELP keyword supported
  • • Cost disclosure included

✓ A2P 10DLC Registered

  • • Brand registered with TCR
  • • Campaign approved by carriers
  • • Using Twilio platform

✓ Privacy Compliant

  • • Phone numbers not sold/shared
  • • Data encrypted at rest & in transit
  • • GDPR/CCPA rights honored

Contact & Support

Business Contact

TableTalk

Phone: (833) 408-7149

Email: hello@tabletalk.restaurant

Website: tabletalk.restaurant

Compliance Contact

For regulatory inquiries:

Email: compliance@tabletalk.restaurant

Phone: (833) 408-7149

For Regulatory Review: This page serves as public documentation of TableTalk's SMS consent collection methods for review by Twilio, wireless carriers, and regulatory authorities. All methods shown are implemented in production and actively collect consent. For verification questions or to request additional documentation, contact compliance@tabletalk.restaurant.