FAQ: WhatsApp Groups Support Capabilities and Restrictions

Our OAPPS for WhatsApp Support application allows you to handle WhatsApp Group conversations directly inside Zendesk.

⚠️ Important Notice: WhatsApp Groups are supported ONLY via the QR-code connection (linked device mode). Group messaging is not supported via the official Meta WhatsApp Cloud API.

Key Features & Capabilities

• Existing Groups & Numbers: connect existing WhatsApp Business numbers without recreating groups or altering existing group memberships.
• Multi-Agent Management: multiple Zendesk agents can view, respond to, and manage group chats simultaneously without requiring physical access to the phone.
• Group Identification: Group tickets clearly display the group name in the ticket subject line and are tagged with "is_group".
• User Info: individual WA sender details (name and/or phone number) are attached to each message so agents can identify who sent what.
• Standard Zendesk Features: supports triggers, automations, routing, SLA tracking, macros, tags, custom fields, and reporting.
• Supported Media: Text, images, PDFs/documents, voice notes, videos, links, and emojis.

How Ticket Management Works

• Ticket Lifecycle: one active Zendesk ticket corresponds to one WhatsApp group.
• New Ticket Creation: A new ticket is created only after the previous group ticket reaches "Closed" status in Zendesk. Messages received while a ticket is in New, Open, Pending, On-hold, or Solved status will thread into the existing ticket.
• Zendesk User Creation: group participants are not created as individual Zendesk users; the group operates under a unified group ticket structure.
• Organization Mapping: you can map group tickets to Zendesk Organizations using custom Zendesk triggers or tags.

Limitations & Unsupported Features

• No Native Mentions or Replies: Quoted/replied-to messages and @mentions are not preserved as native WhatsApp threading inside Zendesk.
• Format Changes: Unsupported or new message formats introduced by WhatsApp may not display as expected.

Critical Operational & Platform Risks

Because QR connection relies on WhatsApp Web / linked-device functionality and is not an official Meta API:

• No SLA / AS-IS Provision: This feature is provided AS-IS without uptime, availability, or reliability guarantees.
• Disconnections & Re-authentication: Unexpected session invalidations can occur. If auto-reconnect fails, an admin notification is sent, and manual re-scanning of the QR code is required.
• Data Loss During Outages: Messages received while the system is disconnected or experiencing an outage are not guaranteed to sync back upon reconnection.
• Risk of Number Restriction or Ban: WhatsApp enforces strict anti-spam and automated usage policies. Connecting via QR carries an inherent risk of number restriction, suspension, or ban by WhatsApp.
• Business Continuity: Keep the physical device / WhatsApp Business application accessible as a fallback channel for urgent communications.