{"id":3071,"date":"2026-10-09T13:11:07","date_gmt":"2026-10-09T07:41:07","guid":{"rendered":"https:\/\/www.smsgatewaycenter.com\/blog\/?p=3071"},"modified":"2026-10-09T13:11:10","modified_gmt":"2026-10-09T07:41:10","slug":"consent-capture-evidence-sms-whatsapp-rcs-telegram","status":"publish","type":"post","link":"https:\/\/www.smsgatewaycenter.com\/blog\/consent-capture-evidence-sms-whatsapp-rcs-telegram\/","title":{"rendered":"Consent Capture and Evidence for SMS, WhatsApp, RCS and Telegram: Building an Opt-In Record You Can Prove"},"content":{"rendered":"\n

A tick box isn’t proof. Here’s how to capture consent as an append-only event log with the exact notice version, fold it into a per-channel send gate next to your suppression list, keep WhatsApp’s opt-in list in step, read CONSENT_FAILED properly, and produce an evidence pack the day someone complains.<\/p>\n\n\n\n

\"Stacked<\/a>
Consent is a history of events, not a flag. The send gate reads that history every time.<\/figcaption><\/figure>\n\n\n\n

Table of Contents<\/h1>\n\n\n\n
    \n
  1. The Short Answer<\/a><\/li>\n\n\n\n
  2. TL;DR<\/a><\/li>\n\n\n\n
  3. What Counts as Proof of Consent<\/a><\/li>\n\n\n\n
  4. Three Rulebooks, One Record<\/a><\/li>\n\n\n\n
  5. Where Consent Lives on Each Channel<\/a><\/li>\n\n\n\n
  6. The Consent Event Table<\/a><\/li>\n\n\n\n
  7. Versioning the Notice<\/a><\/li>\n\n\n\n
  8. Capture Points: Forms, Keywords, Chat and Counter<\/a><\/li>\n\n\n\n
  9. Double Opt-In Over SMS<\/a><\/li>\n\n\n\n
  10. Folding Events Into Current State<\/a><\/li>\n\n\n\n
  11. The Send Gate: Consent and Suppression Together<\/a><\/li>\n\n\n\n
  12. Withdrawal as Easy as the Grant<\/a><\/li>\n\n\n\n
  13. Keeping the WhatsApp Opt-In List in Step<\/a><\/li>\n\n\n\n
  14. Reading CONSENT_FAILED and Other Signals<\/a><\/li>\n\n\n\n
  15. Evidence Packs: Answering a Complaint<\/a><\/li>\n\n\n\n
  16. Retention and Keeping Only What You Need<\/a><\/li>\n\n\n\n
  17. Four Code Samples, Four Traps<\/a><\/li>\n\n\n\n
  18. Decision Matrix<\/a><\/li>\n\n\n\n
  19. Launch Checklist<\/a><\/li>\n\n\n\n
  20. Unspecified Behaviour and How to Code Around It<\/a><\/li>\n\n\n\n
  21. FAQs<\/a><\/li>\n<\/ol>\n\n\n\n

    The Short Answer<\/h2>\n\n\n\n

    Store consent as an append-only log of events, one row per grant or withdrawal, per phone number, per channel, per purpose. Every grant row points at the exact notice text the person saw (saved once, addressed by its hash), records how they said yes (form tick, keyword, chat button, signed paper) and carries enough context to replay the moment later. Your send gate folds those events into a current answer and checks it next to your suppression list before every send. That’s the whole design.<\/p>\n\n\n\n

    Why go to the trouble? Because the messaging platform doesn’t hold your consent for you. On SMSGatewayCenter<\/strong> there’s a WhatsApp opt-in list in the dashboard and a Blocked Numbers list, but no API to write either, and nothing at all for RCS or Telegram. Indian SMS adds DLT consent templates<\/a><\/strong> and a CONSENT_FAILED<\/code> rejection on top. And India’s Digital Personal Data Protection Act <\/strong>puts the burden on you: where consent is the basis of processing and it’s questioned in a proceeding, you have to prove the notice was given and consent was given. A boolean column can’t do that. An event log with the notice attached can.<\/p>\n\n\n\n

    TL;DR<\/h2>\n\n\n\n