# WhatsApp Business Opt-In – Implementation Plan **Status:** Draft for team review **Owner:** Hady ElHady **Stakeholders:** Luke, Legal **Last Updated:** 2026-02-18 --- ## Executive Summary Ordio is introducing WhatsApp Business as a new channel for customer and lead interaction across Sales, Marketing, Customer Success, and Support. Per WhatsApp/Meta policy and GDPR/DSGVO, **explicit opt-in consent is required** before sending any WhatsApp messages. This document outlines what needs to be done across legal, HubSpot, forms, and processes before the channel goes live. It is intended for team review and approval before implementation. **Key requirement:** Contacts must opt in specifically for WhatsApp communication. HubSpot’s “WhatsApp number” field must be populated with a WhatsApp-validated phone number. --- ## 1. Legal & Compliance ### 1.1 Datenschutzrichtlinie (Privacy Policy) Update **Action:** Add a dedicated WhatsApp section to the Datenschutzrichtlinie before launch. **Content to include (German):** - That Ordio uses WhatsApp Business for customer communication - Which data is processed (phone number, message content, metadata) - Legal basis (Art. 6(1)(a) DSGVO – consent) - That consent is voluntary and can be withdrawn at any time - How to opt out (e.g., reply STOP or BEENDEN, or contact Ordio) - Link to Meta/WhatsApp Business privacy policy - Data transfer considerations (Meta servers, EU/US) **Placement:** New subsection under “Drittanbieter” (e.g., after HubSpot, before heyData). **Legal review required before publishing.** --- ### 1.1.1 Recommended Copy for Legal Review The following copy is proposed for legal review and approval. Do not publish until Legal has signed off. --- #### A. Datenschutzrichtlinie – WhatsApp Section (German) **Proposed text for insertion into the Datenschutzrichtlinie:** > **WhatsApp Business** > > Wir nutzen WhatsApp Business, um mit Ihnen per WhatsApp zu kommunizieren (z. B. für Terminbestätigungen, Rückfragen, Support oder Marketing). Anbieter ist Meta Platforms Ireland Limited, 4 Grand Canal Square, Grand Canal Harbour, Dublin 2, Irland. Der Anbieter verarbeitet Kontaktdaten (Telefonnummer), Nachrichteninhalte und Meta-/Kommunikationsdaten (z. B. Zeitstempel, Geräte-Informationen). Die Daten können auch an Server von Meta in den USA übermittelt werden. In diesem Fall gelten Standardvertragsklauseln gemäß Art. 46 Abs. 2 lit. c DSGVO. > > Die Rechtsgrundlage der Verarbeitung ist Art. 6 Abs. 1 S. 1 lit. a DSGVO (Einwilligung). Die Einwilligung ist freiwillig und kann jederzeit widerrufen werden. Sie können sich von WhatsApp-Nachrichten abmelden, indem Sie uns „STOP" oder „BEENDEN" per WhatsApp schreiben oder uns unter hallo@ordio.com kontaktieren. > > Weitere Informationen finden Sie in der Datenschutzerklärung von Meta/WhatsApp unter [https://www.whatsapp.com/legal/privacy-policy](https://www.whatsapp.com/legal/privacy-policy). **Key elements covered:** Anbieter, Datenkategorien, mögliche Übermittlung in Drittländer, Rechtsgrundlage (Einwilligung), Widerruf, Opt-out-Möglichkeiten, Link zur Anbieter-Datenschutzerklärung. --- #### B. WhatsApp Opt-In Checkbox Label (Forms) **Proposed label for the optional WhatsApp consent checkbox on all forms that collect phone:** > Ich stimme zu, dass Ordio mich per WhatsApp kontaktieren darf (z. B. für Terminbestätigungen, Rückfragen oder Support). Ich kann mich jederzeit per STOP oder BEENDEN abmelden. **Alternative (shorter):** > Ich stimme zu, dass Ordio mich per WhatsApp kontaktieren darf. Abmeldung jederzeit möglich (STOP oder BEENDEN). --- #### C. Consent Notice – Lead Capture Popup (Existing + WhatsApp) **Current text (keep as-is):** > Mit dem Absenden stimmst du zu, dass wir dich per Telefon kontaktieren. **Additional WhatsApp checkbox label (if separate from phone consent):** > Ich stimme zu, dass Ordio mich zusätzlich per WhatsApp kontaktieren darf (z. B. für Terminbestätigungen). Abmeldung jederzeit per STOP oder BEENDEN möglich. --- #### D. Opt-Out Instruction (for WhatsApp Templates / Auto-Reply) **Proposed footer text for WhatsApp template messages (if space allows):** > Du erhältst diese Nachricht, weil du dich für WhatsApp-Kommunikation von Ordio angemeldet hast. Abmelden: STOP oder BEENDEN schreiben. --- **Legal sign-off checklist:** - [ ] Datenschutzrichtlinie WhatsApp section (A) - [ ] WhatsApp opt-in checkbox label (B) – primary or alternative - [ ] Lead capture WhatsApp checkbox label (C) - [ ] Opt-out instruction for templates (D) --- ### 1.2 WhatsApp Business Policy Compliance **Requirements (from Meta/WhatsApp):** - No pre-checked opt-in boxes - Clear explanation of message types (e.g., meeting confirmations, support, marketing) - Transparency on message frequency - Easy opt-out (keywords: STOP, BEENDEN, UNSUBSCRIBE) - Documented consent (timestamp, source, legal basis) **HubSpot subscription types:** - **WhatsApp Transactional:** Meeting confirmations, booking, support – utility messages - **WhatsApp Marketing:** Lead nurturing, promotional content --- ## 2. HubSpot Configuration ### 2.1 WhatsApp Number Field **Action:** Ensure the HubSpot “WhatsApp number” contact property exists and is used correctly. **Requirements:** - Phone numbers must be in international format (e.g., +491234567890) - Phone numbers from forms should be normalized before syncing - Incoming WhatsApp messages: sync the sender’s number to this field (Luke’s suggestion) --- ### 2.2 Phone Number Sync Strategy **Luke’s proposal:** Sync incoming mobile numbers from WhatsApp conversations to the WhatsApp number field. **Flow:** - When a contact messages Ordio via WhatsApp, the message appears in HubSpot Conversations Inbox - Copy the sender’s phone number to the “WhatsApp number” property - This ensures contacts who initiate WhatsApp chats have a valid, WhatsApp-verified number **Consideration:** Avoid duplicate contacts when the same person uses different phone formats (e.g., +49 vs 0049). Normalize formats before matching. --- ### 2.3 WhatsApp Subscription Management **Actions:** - Configure WhatsApp Marketing and WhatsApp Transactional subscription types in HubSpot - Set up workflows to opt in contacts when they give explicit consent via forms - Document legal basis and “explanation for communication” when manually subscribing contacts - Ensure opt-out keywords (STOP, BEENDEN) are honored and subscription status is updated **Bulk opt-in (BETA):** HubSpot offers bulk WhatsApp consent update on the contacts index page – useful for migrating existing contacts who have given consent elsewhere. --- ## 3. Forms & Channels – Opt-In Implementation ### 3.1 Form Categories (Current Setup) Ordio has two form categories: - **Contact request** (demo, callback, webinar, event): User explicitly requests contact – data always sent to HubSpot - **Lead gen** (template download, calculator export, gated content): Consent required – only send to HubSpot when user consents **WhatsApp opt-in is separate** from general HubSpot/marketing consent. A user can consent to HubSpot but decline WhatsApp. --- ### 3.2 Forms That Collect Phone Numbers | Form Type | Phone Field | Form Category | Usage | |-----------|-------------|---------------|-------| | Lead capture popup | Required | Contact request | 105+ pages | | Demo / callback | Optional | Contact request | Hero, CTA sections | | Add-on pricing | Optional | Contact request | Pricing pages | | Webinar registration | Optional | Contact request | Webinar pages | | Event lead capture | Optional | Contact request | Trade fairs | | Template download | Optional | Lead gen | Template pages | | Tools export | Optional | Lead gen | Calculator pages | | Gated content | Optional | Lead gen | Download pages | | ShiftOps unlock | Optional | Lead gen | ShiftOps report | --- ### 3.3 WhatsApp Opt-In Checkbox – Requirements **For each form that collects phone and creates HubSpot contacts:** 1. **Add optional WhatsApp consent checkbox** - Unchecked by default - Clear label in German – see **Section 1.1.1 B** for approved legal copy - Placement: Above submit button (consistent with existing consent pattern) 2. **Behavior** - When checkbox is checked: Pass consent to HubSpot and set WhatsApp subscription status (Marketing and/or Transactional as needed) - When unchecked: Do not set WhatsApp opt-in; contact can still receive email/phone contact per existing logic 3. **No blocking:** Form submission must always succeed; WhatsApp opt-in is optional. --- ### 3.4 Forms to Update (Checklist) **Contact request forms:** - [ ] Lead capture popup (phone required – high priority) - [ ] Demo / callback forms (hero, CTA sections) - [ ] Add-on pricing form - [ ] Webinar registration (product, payroll, trinkgeld) - [ ] Event lead capture (Internorga, Intergastra, etc.) **Lead gen forms:** - [ ] Template download (Dienstplan, Schichtplan, dynamic templates) - [ ] Tools export modals - [ ] Gated content (whitepaper, onboarding checklist) - [ ] ShiftOps unlock form - [ ] ShiftOps NPS form (if phone collected) **Additional channels:** - [ ] Content, demo, SDR, event, webinar form handlers - [ ] Any embedded HubSpot forms that collect phone --- ### 3.5 Consent Notice for Contact Request Forms **Current text (lead capture):** See **Section 1.1.1 C** for approved copy. **Recommendation:** - Keep existing phone consent text - Add separate WhatsApp checkbox with its own label (see **Section 1.1.1 B** or **C**) - Do not bundle WhatsApp into the general “contact” consent – WhatsApp requires explicit, separate opt-in per Meta policy --- ## 4. Processes & Workflows ### 4.1 Inbound WhatsApp Messages **Flow:** 1. Contact messages Ordio via WhatsApp 2. Message appears in HubSpot Conversations Inbox 3. Sync sender’s phone to “WhatsApp number” property 4. Consider auto-opt-in for Transactional (first message = consent to reply) – verify against Meta policy 5. For Marketing: Require explicit opt-in via form or keyword (LOSLEGEN) --- ### 4.2 Outbound WhatsApp (Template Messages) **Before sending:** - Contact must have WhatsApp number populated - Contact must have WhatsApp Marketing or Transactional subscription = Subscribed - Use only pre-approved templates (Meta requirement) **Use cases (from Luke):** - Sales: Meeting confirmation, booking, lead qualification - Marketing: Lead nurturing - Customer Success: Feedback, onboarding, meeting booking - Support: Chat --- ### 4.3 Opt-Out Handling **Requirements:** - Process opt-outs immediately - Never message opted-out contacts again - HubSpot keywords: STOP, BEENDEN, UNSUBSCRIBE, CANCEL, END, QUIT (German: LOSLEGEN for opt-in, BEENDEN for opt-out) - If Marketing opt-out button in template is clicked, unsubscribe from Marketing only; Transactional can remain for utility messages --- ## 5. Documentation & Training ### 5.1 Internal Documentation **Create/update:** - WhatsApp opt-in implementation guide - Form checklist: which forms have WhatsApp checkbox, which don’t - HubSpot workflow documentation for WhatsApp subscription management - QA checklist for manual testing --- ### 5.2 Team Training **Topics:** - When and how to use the WhatsApp channel - How to manually opt in contacts (with documented consent) - How to handle opt-out requests - Difference between Transactional and Marketing subscription types --- ## 6. Testing & Validation ### 6.1 Pre-Launch Checklist - [ ] All forms with phone have WhatsApp checkbox (or documented exception) - [ ] Checkbox unchecked by default - [ ] Consent passed to HubSpot and subscription status set correctly - [ ] Datenschutzrichtlinie updated and legally reviewed - [ ] HubSpot WhatsApp number field populated for test contacts - [ ] Opt-out keywords tested (STOP, BEENDEN) - [ ] Inbound message sync to WhatsApp number field verified --- ### 6.2 Manual QA Scenarios 1. **Lead capture popup:** Submit with WhatsApp checked → verify HubSpot contact has WhatsApp subscribed 2. **Lead capture popup:** Submit without WhatsApp checked → verify no WhatsApp subscription 3. **Template download:** Same flow for lead gen forms 4. **Opt-out:** Send STOP via WhatsApp → verify subscription status updated in HubSpot --- ## 7. Rollout Phases **Phase 1 – Legal & HubSpot (before any form changes):** - Datenschutzrichtlinie draft and legal review - HubSpot WhatsApp number field and subscription types configured - Inbound sync from WhatsApp to WhatsApp number field **Phase 2 – Forms:** - Add WhatsApp checkbox to lead capture popup (highest volume) - Add to demo/callback, webinar, event forms - Add to lead gen forms (template, tools, gated content, ShiftOps) **Phase 3 – Processes & Documentation:** - Workflows for subscription management - Internal documentation - Team training on when/how to use WhatsApp **Phase 4 – Go-Live:** - Final QA - Launch WhatsApp channel publicly - Monitor opt-in rates and opt-outs --- ## 8. Risks & Mitigations | Risk | Mitigation | |------|-------------| | Legal non-compliance | Legal review of Datenschutzrichtlinie and consent wording | | Missing opt-in on a form | Audit all forms; checklist before launch | | Duplicate contacts (phone format) | Normalize phone formats; use HubSpot deduplication | | User confusion (too many checkboxes) | Keep labels clear; minimal, non-disruptive styling | | Meta policy violation | Follow approved opt-in methods; no pre-checked boxes; easy opt-out | --- ## 9. Open Questions 1. **Transactional vs Marketing:** Which use cases require which subscription type? (Meeting confirmation = Transactional; lead nurturing = Marketing) 2. **Auto-opt-in for inbound:** Does first WhatsApp message from contact count as consent for Transactional replies? (Verify Meta policy) 3. **Existing contacts:** Bulk opt-in for contacts who already gave phone + consent elsewhere? Requires documented consent and legal basis. 4. **Double opt-in:** Germany sometimes recommends double opt-in for marketing – confirm with legal whether single opt-in is sufficient for WhatsApp. --- ## 10. Summary of Deliverables - [ ] Datenschutzrichtlinie: WhatsApp section (legal review) - [ ] HubSpot: WhatsApp number field, subscription types, inbound sync - [ ] Forms: WhatsApp checkbox on all contact-creation forms that collect phone - [ ] Pass WhatsApp consent to HubSpot and set subscription status - [ ] Documentation: Implementation guide, form checklist, QA checklist - [ ] Team training: When and how to use WhatsApp channel --- ## References - [HubSpot: Collect consent for WhatsApp](https://knowledge.hubspot.com/inbox/collect-consent-for-whatsapp-conversations) - [HubSpot: WhatsApp subscription statuses](https://knowledge.hubspot.com/inbox/review-whatsapp-subscription-status) - [Meta: Getting opt-in for WhatsApp](https://developers.facebook.com/docs/whatsapp/overview/getting-opt-in/) - [WhatsApp Business Messaging Policy](https://business.whatsapp.com/policy)