Zalo Group Chat
View as Markdown
Team Inbox displays and lets you participate in **Zalo Group** and **Community** conversations alongside 1-1 customer threads.
:::note[Platform scope & permissions]
- Group chat is currently supported on **Zalo** only (Facebook, WhatsApp, and Webchat support 1-1 conversations only).
- Viewing group threads requires **`inbox:read:all`**; sending messages or performing message actions requires **`inbox:reply`**.
:::
## Identifying Groups & Communities
In a Zalo account's conversation list:
- **Group Avatar**: shows the group's custom avatar, or automatically renders a composite avatar from up to **4 member avatars** when no custom image is set.
- **Community Badge**: Zalo Communities (`isCommunity`) display a **Community** badge in both the conversation list and the thread header.
- **Member Count**: the thread header displays the group's current member count.
## Messaging & Member `@mentions`
Inbound messages in group threads display each sender's **name and avatar**, and the typing indicator identifies which specific member is typing.
To mention members in a group:
1. Type **`@`** in the composer to open the member picker.
2. Continue typing to filter members (group **Owner** and **Deputy** roles are labeled inline).
3. Select a specific member, or choose **`@All`** to notify everyone in the group.
Standard messaging features — quote reply, reactions, recall, forward, images/videos/files, stickers, contact cards, locations, quick replies, pinned messages (up to 3), in-thread search, and team **Takeover** locks — work the same way as in [1-1 conversations](/inbox/conversations/).
## Composer Lock States
The group message composer automatically locks in three situations:
| Lock State | Cause | Resolution |
| :--- | :--- | :--- |
| **Join Pending Approval** | The Zalo account's request to join the group is awaiting admin approval. | Wait for a group admin to approve the request; the composer unlocks once membership becomes active. |
| **Admin-Only Messaging** | The group restricts messaging to Owner/Deputies and this Zalo account is a regular member. | Only a group Owner or Deputy can send messages in this group. |
| **Claimed by Teammate** | Another workspace member clicked **Takeover** on this group thread. | Wait for them to click **Release**, or click **Takeover** to claim control yourself. |
## Differences from 1-1 Conversations
- **No AI Auto-Reply or Copilot**: AI auto-reply, the AI Draft bar, and the AI Copilot tab are intentionally disabled on group threads (1-1 only).
- **No Read Receipts**: the **Seen** receipt marker is only shown on 1-1 threads.
:::note[Advanced group management]
Backend APIs exist for Zalo group management (creating groups, joining via invite link, renaming/changing avatars, adding/removing members, managing deputies and invite links, revealing hidden members, and leaving groups), but the right-side group info and management panel is not yet exposed in the Team Inbox UI.
:::
Team Inbox displays and lets you participate in Zalo Group and Community conversations alongside 1-1 customer threads.
Identifying Groups & Communities
Section titled “Identifying Groups & Communities”In a Zalo account’s conversation list:
- Group Avatar: shows the group’s custom avatar, or automatically renders a composite avatar from up to 4 member avatars when no custom image is set.
- Community Badge: Zalo Communities (
isCommunity) display a Community badge in both the conversation list and the thread header. - Member Count: the thread header displays the group’s current member count.
Messaging & Member @mentions
Section titled “Messaging & Member @mentions”Inbound messages in group threads display each sender’s name and avatar, and the typing indicator identifies which specific member is typing.
To mention members in a group:
- Type
@in the composer to open the member picker. - Continue typing to filter members (group Owner and Deputy roles are labeled inline).
- Select a specific member, or choose
@Allto notify everyone in the group.
Standard messaging features — quote reply, reactions, recall, forward, images/videos/files, stickers, contact cards, locations, quick replies, pinned messages (up to 3), in-thread search, and team Takeover locks — work the same way as in 1-1 conversations.
Composer Lock States
Section titled “Composer Lock States”The group message composer automatically locks in three situations:
| Lock State | Cause | Resolution |
|---|---|---|
| Join Pending Approval | The Zalo account’s request to join the group is awaiting admin approval. | Wait for a group admin to approve the request; the composer unlocks once membership becomes active. |
| Admin-Only Messaging | The group restricts messaging to Owner/Deputies and this Zalo account is a regular member. | Only a group Owner or Deputy can send messages in this group. |
| Claimed by Teammate | Another workspace member clicked Takeover on this group thread. | Wait for them to click Release, or click Takeover to claim control yourself. |
Differences from 1-1 Conversations
Section titled “Differences from 1-1 Conversations”- No AI Auto-Reply or Copilot: AI auto-reply, the AI Draft bar, and the AI Copilot tab are intentionally disabled on group threads (1-1 only).
- No Read Receipts: the Seen receipt marker is only shown on 1-1 threads.