YundaDeskSelling into Vietnam, a support setup that skips Zalo is effectively invisible to most of the market. On top of that, cash-on-delivery (COD) adoption runs noticeably higher than in most regions, which means “can I change my address,” “why was my delivery refused,” and “how do I get my COD payment back” turn into daily recurring tickets. Language, channel, and payment method combine into a set of edge cases that look quite different from what a team dealing with US or European customers is used to.
Zalo is the main channel, not a nice-to-have
On a lot of cross-border channel lists, Zalo gets ranked below WhatsApp or Messenger as a secondary option. In Vietnam it’s the opposite — Zalo is the default everyday messaging app. Once a customer adds a brand’s Zalo, it sits right alongside their conversations with family and friends. That changes a few things:
- Pricing questions, shipping follow-ups, and complaints show up on Zalo more often than on any other channel.
- A slow or stiff reply feels more jarring here than it would in an email thread.
- Push too hard with outbound messages and customers unfollow or report the account faster than on most platforms.
Zalo is one of the long-tail channels many platforms skip entirely or support only superficially. In YundaDesk it connects into the same shared inbox as the website widget, WhatsApp, and email, so agents aren’t stuck babysitting a separate Zalo backend just for Vietnamese customers.
Vietnam Market Customer Support Guide for Cross-Border Sellers: the service baseline to plan around
A Vietnamese knowledge base: direct beats padded
Vietnamese customer service tends to run direct, with minimal small talk. Customers on Zalo ask short questions and expect short, specific answers — an overly polished greeting before the actual answer can come across as distant, even like an ad. Structuring high-frequency questions into the knowledge base is what keeps the AI’s tone consistent:
| Scenario | What the answer should cover |
|---|---|
| Shipping status | Current status plus an estimated delivery window, no filler |
| Changing a COD address | Whether it’s still possible, the cutoff point, hand off anything past that |
| Refused delivery reason | A list of common causes, hand off specific order investigations |
| Delay complaints | Acknowledge first, then explain the reason and next step |
Running Vietnamese support copy through machine translation on the fly carries real risk — word order and idiom differ sharply from Chinese or English, and a stiff literal translation tends to read as obviously machine-generated. The AI automatically replies in whatever language the customer writes in, but tone rules and industry terms are worth reviewing by a human before they go into the knowledge base, rather than leaving translation entirely to the engine in the moment.
ICT time zone: don’t schedule around a fixed offset
Vietnam runs on ICT (UTC+7) year-round with no daylight saving switch, which is simpler than markets like the UK or US. The common mistake for teams based elsewhere is scheduling coverage only around Vietnamese daytime, when a lot of Zalo activity actually spikes in the evening — people checking on a shipment after work. Letting AI customer service cover Vietnamese customers’ active hours around the clock, while routing judgment calls (address changes, refusal disputes, refunds) to agents on shift during those windows, means the team isn’t stretching coverage just to have someone always online.
High COD adoption means address changes and refusals daily
COD adoption in Vietnamese e-commerce runs noticeably higher than in most markets, and that drives two recurring support categories:
- Address changes. Customers changing their delivery address after placing an order is the norm here, not the exception. AI customer service can explain the change window and the process directly, but once an order has entered fulfillment, whether it can still be redirected depends on carrier capacity and costs already incurred — that needs a human to confirm before answering the customer.
- Refused deliveries. COD makes refusing a delivery low-cost for the customer, and the reasons vary widely — changed their mind, thought it was free, wrong address, doubts about the product. AI can collect the order number and stated reason, which helps the team spot patterns in refusal causes over time, but decisions on redelivery or who covers the shipping cost involve money and policy judgment, and always go to a human.
Putting the address-change cutoff and common refusal causes with their handling rules into the knowledge base is what lets AI customer service pull from documented policy when a customer asks, instead of guessing or improvising an answer.
Proactive Zalo messages: guardrails matter more than volume
Zalo supports bulk pushes, and shipping reminders or COD amount confirmations are a natural fit for proactive outreach. But Vietnamese customers don’t tolerate being over-messaged any better than anyone else. Every channel in YundaDesk runs through the same six guardrails, and none of them can be turned off: cooldown periods, frequency caps, quiet hours, no interrupting an active conversation, a permanent do-not-contact list, and mandatory human review for sensitive actions. Start in observe-only mode to see what the AI would send and to whom, then move to review-each-message, and only consider full automation once the timing and copy have held up.
One customer profile, even after an address change
Vietnamese customers often start on Zalo with a pricing question, then follow up on shipping through the website widget or email after placing an order. YundaDesk’s cross-border CRM automatically merges these channel identities into a single customer profile, with country, language, time zone, and social IDs recorded as default fields. If a customer changed an address or refused a delivery before, an agent picking up the conversation sees that history immediately — no need to ask the customer to repeat the order number and reason again.
Sample scripts for common questions
Expand: high-frequency Vietnamese customer questions and suggested response directions
- “Tôi có thể đổi địa chỉ giao hàng không?” (Can I change my delivery address?) — Explain the change window; hand off orders already in fulfillment for human confirmation.
- “Tại sao đơn hàng của tôi bị từ chối nhận?” (Why was my order refused?) — Provide common causes; hand off specific order investigations to a human.
- “COD thì tôi có phải trả phí ship khi từ chối không?” (Do I pay shipping if I refuse a COD delivery?) — Answer per actual policy; hand off anything involving a fee amount.
- “Hàng bị lỗi, tôi muốn hoàn tiền ngay.” (The product is defective, I want a refund now.) — AI acknowledges and collects order details without promising an amount, then hands off immediately with a conversation summary.
Vietnam’s real support challenge isn’t the language barrier — it’s the pileup of edge cases that Zalo as the main channel and COD as the dominant payment method create together. Documenting address-change and refusal policy in the knowledge base, letting AI catch the repeat questions on Zalo, and keeping refunds and disputes with a human is the core of getting this market right.