Docs
SMS Opt-In Evidence

SMS Opt-In Evidence

How Plotwise records and demonstrates end-user consent for text messaging compliance.

Overview

Twilio requires a documented opt-in path for every recipient who receives text messages from Plotwise. This page aggregates the user experience, language, and database records that demonstrate compliant consent collection. It can be shared directly with Twilio reviewers.

Opt-In Surfaces

1. Marketing Contact Form

  • Location: /contact
  • Audience: Prospective customers requesting demos or updates
  • Consent capture:
    • Visitors provide name, email, optional phone number, and message
    • An explicit checkbox labeled "I agree to receive SMS updates from Plotwise" sits directly above the submit button
    • Supporting language states message frequency, STOP/HELP instructions, rate disclosures, and clarifies that consent is not a purchase condition
  • Validation rules:
    • Phone number becomes required when the box is checked
    • Submission records whether consent was granted (even when no SMS is requested)

2. Customer Dashboard Settings

  • Location: Organizations › Settings › Account › Notifications › SMS alerts
  • Audience: Authenticated Plotwise users who will receive operational texts
  • Consent capture:
    • Users toggle a dedicated checkbox labeled "Receive SMS alerts about account activity"
    • The description repeats compliance language (STOP/HELP, rates, and consent disclaimer)
    • When enabled, we record the exact timestamp and mark the source as account settings
    • Disabling the toggle removes the consent timestamp and source to ensure messages stop immediately
  • Guardrails:
    • Users must store a phone number in profile settings before the toggle can be enabled
    • The settings card displays the last consent update so support teams can verify the change

Data Retention

Consent is persisted in the primary application database (user table):

ColumnPurpose
enabledSmsNotificationsBoolean flag reflecting the current opt-in state
smsConsentAtTimestamp of the most recent affirmative consent
smsConsentSourceText label identifying where the consent was captured (e.g., account settings)

These fields allow support or compliance teams to export an audit trail when Twilio requests evidence.

Producing Evidence for Twilio

  1. Capture a screenshot of either opt-in surface showing the consent checkbox and disclosure language
  2. Provide this document link (/docs/sms-opt-in) with your Twilio compliance submission
  3. Include a sample record from the database containing enabledSmsNotifications = true with matching smsConsentAt timestamp
  4. Reference STOP and HELP keywords in automated messaging templates to complete the compliance checklist

Ongoing Maintenance

  • Re-confirm consent if a user changes their phone number
  • Monitor support tickets for STOP requests and apply the toggle immediately
  • Update this page whenever the consent language or flow changes so Twilio reviewers always see the current experience