How can I manage WhatsApp user consent (opt-in) and avoid spam issues using Pushwoosh Journeys?

To ensure your WhatsApp campaigns are successful and comply with Meta's policies, it's crucial to get explicit user consent (opt-in) and manage how you communicate. Pushwoosh Journeys are the perfect tool for automating this process.

Creating a WhatsApp Opt-In Journey

Here is a recommended best practice for building an automated opt-in flow:

1. Start the Journey: Use an Audience-based entry element to target your desired users (e.g., new users).
2. Send the Consent Request: Add a WhatsApp channel element and use an approved Meta template that includes Quick Reply buttons. For example: > "Would you like to receive marketing updates and special offers from us? Please choose an option below." > - Button 1: "Yes, I agree" > - Button 2: "No, thanks"
3. Tag Users Based on Their Reply: Split the flow on the Quick Reply buttons and connect each branch to an Update user profile element (this is the element that assigns Tag values — there is no separate "Set Tags" element).
   • For "Yes, I agree": use Update user profile to set a tag such as whatsapp_opt_in: true.
   • For "No, thanks": use Update user profile to set whatsapp_opt_out: true, or simply end the flow with an Exit from journey element.
4. Target Future Campaigns: For all future marketing Journeys, use the Audience-based entry element with a segment of users having whatsapp_opt_in: true.

Best Practices for Avoiding Spam Flags

• Use Approved Templates: All business-initiated conversations must start with a pre-approved message template from your WhatsApp Business Manager.
• Respect the 24-Hour Window: Once a user replies, you have a 24-hour window to send free-form (non-template) messages. After it closes, you must use an approved template to re-initiate the conversation.
• Control Message Frequency: Frequency capping is available for WhatsApp. In the WhatsApp element you can use your project-wide Global frequency capping settings, ignore them, or set a custom cap for that message. Note that custom capping does not isolate the message from the global cap. Frequency capping applies only to messages marked as Marketing; Transactional messages bypass it. You can also add a Time delay element between messages.
• Segment Your Audience: Use precise targeting with tags and the Condition split element (formerly called "Segment split") to keep messages relevant.