Group inbox

Groups are not generally available in this release. Live group creation, participant changes and sending remain blocked because Waaru cannot yet verify the required exclusion from Meta's Multi-solution Conversations. Seeing Group inbox or previously recorded groups does not enable these actions. There is no self-service override for an unverified number.

The tasks below apply only to a release where both number eligibility and provider operation have been verified.

Check your number and accessCopy Anchor Link

1. Open Group inbox from the dashboard navigation.
2. Select the permitted WhatsApp number at the top of the page.
3. Select Check eligibility and read the result before preparing an action.

Meta requires an Official Business Account. WhatsApp Business app numbers, coexistence connections and numbers using Multi-solution Conversations are unsupported. A connected Cloud API number alone does not establish Groups eligibility. See Meta's Groups API requirements, checked October 18, 2026.

If Group access needs verification appears, leave group actions blocked. Retrying the eligibility read can recover an unavailable check, but cannot replace missing proof. Existing records may remain readable within your permissions. For a persistent eligibility or access problem, contact Waaru Care with the selected number's name and the displayed reason. Never share access tokens or invitation links in a support message.

Reading and sending group messages require permission to view all Inbox conversations for that number. Assigned-only access does not grant access to group messages. Management actions require additional management permission, and number-level access still applies. Group assignment is not supported, so claiming a private conversation does not grant access to a group.

Find or create a group after activationCopy Anchor Link

For a verified number, Sync provider groups reads its Cloud API groups. Use Continue sync when another provider page remains. This does not import ordinary existing WhatsApp groups or Communities.

To prepare a new group, select Create group, enter its name and description, then choose its joining policy. Review the request before submitting it. A submitted request is not proof that the group exists; check its status and wait for confirmation before repeating the action.

Groups are invitation-only. Waaru currently uses a conservative limit of seven external participants per group. Meta documents a maximum of eight participants and 10,000 groups created per business number, with one Cloud API business per group. These limits do not support migrating a large existing community.

Review invitations and participantsCopy Anchor Link

Open a group, then expand Group settings and participants. Review its status, recorded participants and joining policy. If membership or settings need verification, use Refresh provider details before preparing another change.

Where your permissions and number eligibility allow, you can:

• Edit the group name and description with Edit settings.
• Retrieve an invitation with Show invitation and Copy invitation link. Share it only with intended participants.
• Review join requests and approve or reject individual requests when the group's joining policy requires approval.
• Reset an invitation, remove a confirmed participant or delete a group after reviewing and confirming the selected action.

Do not assume a partial or uncertain response changed every participant. Refresh provider details and check the original request. Keep invitation links private; anyone holding a link can use it to join or request approval under the group's joining policy.

Read and send supported messagesCopy Anchor Link

The group conversation is separate from private contact conversations. Its own inbound group activity opens a 24-hour service window. A private message from a participant does not open or extend the group's window.

For an active, verified group, the composer supports text and eligible image, video, ordinary audio and document files inside that window. Use Use template to choose a supported approved text or media template when needed, including outside the group window. Template eligibility, number state and file checks still apply. An approved private-chat template is not automatically suitable for Groups.

Voice-note recording, calls, interactive or commerce messages, authentication templates, view-once or disappearing messages, editing or deleting sent messages, and sending read receipts are unsupported. Groups do not use private Inbox assignment, automatic replies, Logic Flows, Automation Flows, AI or MCP actions, or Developer API keys for group operations.

Recover an interrupted or uncertain requestCopy Anchor Link

Use the request's status action, Check saved request status, or Check send status to inspect the original request after an interruption. Keep its request ID when asking Waaru Care to investigate. If a request is not visible in the saved list, do not assume it was never submitted.

An uncertain result means the provider may have accepted the action. Do not submit a replacement, change its content or retry it as a new request. Wait for confirmed status or review with Waaru Care. A rejected request can be corrected when the interface permits editing. An accepted send allows a fresh draft, but does not confirm delivery to every participant.

Understand delivery and costCopy Anchor Link

Delivery and read observations count distinct participants with recorded evidence. A group-level status is not proof that every participant received a message. Missing or conflicting pricing evidence remains unknown, and the recipient estimate shown when sending is not a bill.

Meta messaging charges can apply per recipient. The exact monetary amount remains unknown in the Group inbox. Do not treat incomplete observations as zero cost or a final charge. Meta's Groups pricing documentation describes the provider's charging basis.

For private one-to-one conversations, use the shared Inbox guide. Group eligibility does not change those conversations' access or service windows.