You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 53ef9b4
Browse filesBrowse the repository at this point in the historyBrowse files
authored
docs: rename Zalo channels — Official and Unofficial (#142)
* docs: rename Zalo channels — Official and Hacked
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* docs: rename Zalo Personal to "Zalo Personal (Unofficial)"
Corrected from "Zalo (Hacked)" to "Zalo Personal (Unofficial)" per
Felix's direction. 46 occurrences across 10 files (EN + ZH).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* docs(zh): translate Zalo Personal (Unofficial) → Zalo 个人版（非官方）
23 occurrences across 5 ZH files.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: zylos <cocoai@cocoai-felix-lin-1b.asia-southeast1-b.c.coco-prd-476606.internal>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/case-studies/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Capability Showcase
2
2
3
-
COCO is not a chatbot — it's your full-time AI employee. Send a message via Telegram, Lark, Microsoft Teams, or Zalo, and it gets to work: writing documents, doing research, coding, processing data. 7x24, no breaks.
3
+
COCO is not a chatbot — it's your full-time AI employee. Send a message via Telegram, Lark, Microsoft Teams, or Zalo (Official), and it gets to work: writing documents, doing research, coding, processing data. 7x24, no breaks.
4
4
5
5
## Core Scenarios
6
6
@@ -142,7 +142,7 @@ COCO is not a chatbot — it's your full-time AI employee. Send a message via Te
142
142
| Cost Savings | 80%+ compared to junior staff |
143
143
| Response Time | Instant response, 7x24 online |
144
144
| Language Support | Bilingual Chinese-English |
145
-
| Channels | Telegram, Lark, Microsoft Teams, Zalo, and more |
145
+
| Channels | Telegram, Lark, Microsoft Teams, Zalo (Official), and more |
146
146
| No Installation | Works directly in your chat tools |
|[Slack](#slack)| Available | European/US enterprise users |
20
20
|[Microsoft Teams](#ms-teams)| Available | Enterprise teams, Microsoft 365 organizations |
21
-
|[Zalo](#zalo)| Available | Vietnam users, personal & business use |
22
-
|[Zalo Personal](#zalo-personal)| Available | Vietnam users, personal Zalo account (unofficial) |
21
+
|[Zalo (Official)](#zalo)| Available | Vietnam users, personal & business use |
22
+
|[Zalo Personal (Unofficial)](#zalo-personal)| Available | Vietnam users, personal Zalo account (unofficial) |
23
23
24
24
> **Tip:** You can connect multiple channels simultaneously. Your AI employee responds across all connected channels. Pro plan supports Telegram + Lark dual-channel access.
25
25
@@ -936,11 +936,11 @@ After installing the app in the previous step, you need to copy its catalog ID:
936
936
937
937
---
938
938
939
-
## Option H: Zalo Deployment {#zalo}
939
+
## Option H: Zalo (Official) Deployment {#zalo}
940
940
941
941
**Estimated time: ~5 minutes**
942
942
943
-
> **Note:** Zalo connects via the official [Zalo Bot Platform](https://bot.zaloplatforms.com) API. Only a personal Zalo account is required — no Official Account (OA) registration, no servers, and no coding skills needed.
943
+
> **Note:** Zalo (Official) connects via the official [Zalo Bot Platform](https://bot.zaloplatforms.com) API. Only a personal Zalo account is required — no Official Account (OA) registration, no servers, and no coding skills needed.
944
944
945
945
One credential is required:
946
946
@@ -962,7 +962,7 @@ One credential is required:
962
962
963
963
1. Log into [COCO Dashboard](https://coco.xyz/dashboard)
964
964
2. Go to the employee instance detail page
965
-
3. Find the **Zalo** card and click **Connect**
965
+
3. Find the **Zalo (Official)** card and click **Connect**
966
966
4. Paste the **Bot Token** from Step 1
967
967
5. Click **Connect** — the system will validate the token and complete the connection
968
968
@@ -975,26 +975,26 @@ One credential is required:
975
975
976
976
> **First message:** The first user to send a DM to the bot becomes the **Owner**. The owner always has full access regardless of policy settings.
977
977
978
-
### Zalo FAQ
978
+
### Zalo (Official) FAQ
979
979
980
980
| Issue | Solution |
981
981
|-------|----------|
982
982
| Bot not responding | Verify the Bot Token is correct. Check the connection status in COCO Dashboard |
983
983
| Cannot send images to bot | Ensure the image is under 10 MB. Supported formats: JPG, PNG |
984
984
| Bot image not displaying | Outbound images must be hosted on a publicly accessible HTTPS URL |
985
985
| Others can't message the bot | By default only the Owner can chat. Enable Allowlist or Open mode to grant access |
986
-
| Want to disconnect | Click the **Disconnect** button on the Zalo card in the employee detail page |
986
+
| Want to disconnect | Click the **Disconnect** button on the Zalo (Official) card in the employee detail page |
987
987
988
988
---
989
989
990
-
## Option I: Zalo Personal Deployment {#zalo-personal}
990
+
## Option I: Zalo Personal (Unofficial) Deployment {#zalo-personal}
991
991
992
992
**Estimated time: ~2 minutes**
993
993
994
-
> **Note:** Zalo Personal uses a real Zalo account via QR code scanning — no bot registration, API keys, or developer accounts needed. It connects through [zca-js](https://github.com/nicenathapong/zca-js), a reverse-engineered protocol library.
994
+
> **Note:** Zalo Personal (Unofficial) uses a real Zalo account via QR code scanning — no bot registration, API keys, or developer accounts needed. It connects through [zca-js](https://github.com/nicenathapong/zca-js), a reverse-engineered protocol library.
995
995
996
996
::: warning Unofficial Protocol
997
-
Zalo Personal uses an unofficial, reverse-engineered protocol (zca-js) that is **not endorsed by Zalo/VNG**. Your account could potentially be restricted or banned by Zalo. **Use at your own risk.** For an official integration, consider [Zalo Bot Platform](#zalo) instead.
997
+
Zalo Personal (Unofficial) uses an unofficial, reverse-engineered protocol (zca-js) that is **not endorsed by Zalo/VNG**. Your account could potentially be restricted or banned by Zalo. **Use at your own risk.** For an official integration, consider [Zalo Bot Platform](#zalo) instead.
998
998
:::
999
999
1000
1000
::: warning Use a Dedicated Zalo Account
@@ -1009,13 +1009,13 @@ No credentials are required. Authentication is done entirely via QR code:
1009
1009
| Dedicated Zalo Account | A phone with Zalo installed and logged in to a **separate account** — not the same account users will use to message your COCO agent |
1010
1010
|~2 minutes | Time to complete deployment |
1011
1011
1012
-
### Step 1: Ask Your AI Employee to Install Zalo Personal
1012
+
### Step 1: Ask Your AI Employee to Install Zalo Personal (Unofficial)
1013
1013
1014
1014
Message your AI employee in any connected channel (Telegram, Lark, WhatsApp, etc.):
1015
1015
1016
-
> "Install the Zalo Personal channel"
1016
+
> "Install the Zalo Personal (Unofficial) channel"
1017
1017
1018
-
Your AI employee will install the Zalo Personal component and generate a QR code, which it sends back to you in the chat.
1018
+
Your AI employee will install the Zalo Personal (Unofficial) component and generate a QR code, which it sends back to you in the chat.
1019
1019
1020
1020
### Step 2: Scan the QR Code with Your Dedicated Zalo Account
1021
1021
@@ -1035,17 +1035,17 @@ Your AI employee will confirm the connection is established. Your dedicated Zalo
1035
1035
1036
1036
> **First message:** The first user to send a DM becomes the **Owner** (administrator). The owner always has full access regardless of policy settings.
1037
1037
1038
-
### Zalo Personal FAQ
1038
+
### Zalo Personal (Unofficial) FAQ
1039
1039
1040
1040
| Issue | Solution |
1041
1041
|-------|----------|
1042
-
| QR code expired before scanning | Ask your AI employee to generate a new QR code (e.g., "Reconnect Zalo Personal") |
1043
-
| Connection lost after some time | Zalo may disconnect long-running sessions. Ask your AI employee to reconnect (e.g., "Reconnect Zalo Personal") |
1042
+
| QR code expired before scanning | Ask your AI employee to generate a new QR code (e.g., "Reconnect Zalo Personal (Unofficial)") |
1043
+
| Connection lost after some time | Zalo may disconnect long-running sessions. Ask your AI employee to reconnect (e.g., "Reconnect Zalo Personal (Unofficial)") |
1044
1044
| Account warning or restriction | This uses an unofficial protocol. If you receive a warning from Zalo, stop using the integration and consider switching to the official [Zalo Bot Platform](#zalo)|
1045
1045
| Others can't message the bot | By default only the Owner can chat. Ask your AI employee to enable Allowlist or Open mode to grant access |
1046
-
| Want to disconnect | Ask your AI employee to disconnect the Zalo Personal channel (e.g., "Disconnect Zalo Personal") |
1046
+
| Want to disconnect | Ask your AI employee to disconnect the Zalo Personal (Unofficial) channel (e.g., "Disconnect Zalo Personal (Unofficial)") |
1047
1047
1048
-
<!-- Commented out: previous dashboard-based setup flow (replaced by agent-based flow above — Zalo Personal is no longer configured through the COCO Dashboard UI)
1048
+
<!-- Commented out: previous dashboard-based setup flow (replaced by agent-based flow above — Zalo Personal (Unofficial) is no longer configured through the COCO Dashboard UI)
1049
1049
1050
1050
No credentials are required. Authentication is done entirely via QR code:
1051
1051
@@ -1055,11 +1055,11 @@ No credentials are required. Authentication is done entirely via QR code:
1055
1055
| Dedicated Zalo Account | A phone with Zalo installed and logged in to a **separate account** — not the same account users will use to message your COCO agent |
1056
1056
| ~2 minutes | Time to complete deployment |
1057
1057
1058
-
### Step 1: Click Connect on the Zalo Personal Card
1058
+
### Step 1: Click Connect on the Zalo Personal (Unofficial) Card
1059
1059
1060
1060
1. Log into [COCO Dashboard](https://coco.xyz/dashboard)
1061
1061
2. Go to the employee instance detail page
1062
-
3. Find the **Zalo Personal** card and click **Connect**
1062
+
3. Find the **Zalo Personal (Unofficial)** card and click **Connect**
1063
1063
4. The system will generate a QR code — this may take a few seconds
1064
1064
1065
1065
### Step 2: Scan the QR Code with Your Dedicated Zalo Account
@@ -1071,7 +1071,7 @@ No credentials are required. Authentication is done entirely via QR code:
1071
1071
1072
1072
### Step 3: Wait for Connection Confirmation
1073
1073
1074
-
1. After scanning, the Dashboard automatically detects the connection — the Zalo Personal card shows **Connected**
1074
+
1. After scanning, the Dashboard automatically detects the connection — the Zalo Personal (Unofficial) card shows **Connected**
1075
1075
2. The connection is established through your dedicated Zalo account
1076
1076
1077
1077
### Step 4: Start Chatting
@@ -1081,14 +1081,14 @@ No credentials are required. Authentication is done entirely via QR code:
1081
1081
1082
1082
> **First message:** The first user to send a DM becomes the **Owner** (administrator). The owner always has full access regardless of policy settings.
1083
1083
1084
-
### Zalo Personal FAQ
1084
+
### Zalo Personal (Unofficial) FAQ
1085
1085
1086
1086
| Issue | Solution |
1087
1087
|-------|----------|
1088
1088
| QR code expired before scanning | QR codes are time-limited. Click **Connect** again to generate a fresh QR code |
1089
1089
| Connection lost after some time | Zalo may disconnect long-running sessions. Return to the Dashboard and scan a new QR code to reconnect |
1090
1090
| Account warning or restriction | This uses an unofficial protocol. If you receive a warning from Zalo, stop using the integration and consider switching to the official [Zalo Bot Platform](#zalo) |
1091
1091
| Others can't message the bot | By default only the Owner can chat. Enable Allowlist or Open mode to grant access |
1092
-
| Want to disconnect | Click the **Disconnect** button on the Zalo Personal card in the employee detail page |
1092
+
| Want to disconnect | Click the **Disconnect** button on the Zalo Personal (Unofficial) card in the employee detail page |
Copy file name to clipboardExpand all lines: docs/index.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ features:
26
26
linkText: See the numbers
27
27
- icon: 💬
28
28
title: "Works Where You Work"
29
-
details: "Telegram, Lark, WhatsApp, Microsoft Teams, Zalo, and more. No new app to install. Just message your AI employee like you'd message a colleague."
29
+
details: "Telegram, Lark, WhatsApp, Microsoft Teams, Zalo (Official), and more. No new app to install. Just message your AI employee like you'd message a colleague."
30
30
link: /channels/
31
31
linkText: View channels
32
32
- icon: 🎯
@@ -76,7 +76,7 @@ Real numbers from real teams — not benchmarks, not demos.
76
76
<divclass="step-card">
77
77
<divclass="step-number">1</div>
78
78
<divclass="step-title">Connect Your Channel</div>
79
-
<divclass="step-desc">Add COCO to Telegram, Lark, WhatsApp, Microsoft Teams, or Zalo. Takes 2 minutes. No API keys, no technical setup.</div>
79
+
<divclass="step-desc">Add COCO to Telegram, Lark, WhatsApp, Microsoft Teams, or Zalo (Official). Takes 2 minutes. No API keys, no technical setup.</div>
80
80
</div>
81
81
<divclass="step-card">
82
82
<divclass="step-number">2</div>
@@ -165,12 +165,12 @@ COCO works in the tools your team already uses. No context switching.
0 commit comments