When Staff Leave with Zalo Customers: 5 Ways to Keep Your Clients in Vietnam

If you run a business in Vietnam, your customers are on Zalo. It is the country's most used messaging app, and it is where clients, distributors and suppliers expect to reach your sales team, ask for a quote, send a photo or confirm an order. That works well until someone resigns. When staff leave with Zalo customers, the client list, the conversation history and the relationship often walk out of the door with them. This guide gives five practical ways to keep those customers with your company, from phone numbers and handover routines to central history, access rights and employment contracts.

Why staff leave with Zalo customers in the first place

Most foreign-owned and FDI companies arrive in Vietnam with a CRM, a shared mailbox and clear rules for email. Then they find that customers simply do not use email for day-to-day business. They message the salesperson on Zalo, usually on that person's own phone number.

The result is a blind spot. Everything sits on an employee's personal device:

• The customer list: who is interested, who is about to reorder, who just complained.
• The history: which price was quoted, which delivery date was promised, which terms were agreed.
• The relationship: the customer knows "Minh from sales", not your company.

Usually there is no bad intent. There is just no process, no shared record, and customers keep messaging the number they know. So the best way to protect customer data when employees leave is to prepare on their first day, not their last.

1. Use company-owned Zalo numbers, not personal ones

This is the structural fix. If customers message a number the company owns, the number stays when the person handling it moves on.

• A company SIM for every work number, bought and kept by the company and used on a company phone.
• Tie each number to a role, not a person: one for enquiries, one for after-sales, one for the southern region. People can change; the number does not.
• Keep personal and work life apart. Staff keep their own Zalo for friends and family. The work number is for customers only.

Moving existing customers takes time because they are used to the old number. Start with new customers, then move existing ones over with a short introduction message. A dedicated work number is also a good habit if you want to use Zalo for sales safely.

2. Run a handover checklist the day someone resigns

The weeks between a resignation and the last working day are your best chance. Do not wait for the last afternoon; start the handover as soon as the resignation is in, and follow the same list every time:

1. Active customers and where each one stands: in discussion, waiting for a quote, ordered, due for a follow-up.
2. Open conversations: customers waiting for an answer, deliveries in progress, unresolved complaints.
3. Commitments: special prices, deadlines, small favours promised. This is the part that gets lost most often.
4. A personal introduction of the new contact to each key customer, sent while the leaver is still there.
5. Devices, SIMs and access returned or closed on the last day, once the handover is done.

The introduction works best when it comes from the person leaving, in their usual tone:

Hello, from next week I am moving to a new role. Lan will take care of your account from now on. She has the full picture of your orders and the prices we discussed. Thank you for working with me.

This checklist helps whatever tools you use. But if the history only lives on the leaver's phone, steps 1 to 3 depend entirely on their goodwill. That is why the third way matters most.

3. Keep customer history in one central place

When every customer message is stored somewhere the company controls, the new contact just opens the conversation and reads what happened. No asking the customer to repeat themselves, no screenshots from a former colleague.

One way to do this is a Zalo shared inbox such as Hubz, a product by BMS. You connect the personal Zalo numbers your team uses for work to one company workspace by scanning a QR code with the phone. From then on:

• Conversations from every number sit in one shared inbox: text, images, files, stickers, links, contact cards and Zalo groups.
• Chat history belongs to the Zalo number, not to the staff member, so it stays when someone leaves.
• Each customer has a profile. You find conversations with search, or filter them by Zalo number and by status, open or closed.
• Staff leave internal notes on a conversation (customers never see them) and tag customers, so the next person understands the context.

If your company runs Odoo, the Odoo Zalo integration is open to early customers: it links a Zalo customer to an Odoo contact by phone number and logs Zalo messages in that contact's chatter.

To be clear about the trade-off: Hubz connects personal Zalo accounts through an unofficial connection, so a number can still be restricted by Zalo. Hubz does not send bulk messages, does not add friends automatically, and alerts you when a number disconnects. Its Terms of use explain the risk and recommend a dedicated work number. Even so, nobody can rule the risk out.

4. Manage employee Zalo accounts with clear access rights

Central storage is half of the answer. The other half is deciding who can see what, who can reply, and what happens when someone leaves. In Hubz, access is based on roles, teams and rights per number:

• Four roles: business owner, supervisor, team lead and staff member.
• Teams with rights per number: on each Zalo number, a team can reply or only view.
• A personal login for everyone, used in the browser on a computer, phone or tablet. Staff never need the phone that holds the number.
• A clear person in charge: staff take a conversation or have it assigned to them, so it is always clear who handles which customer.
• A shared customer pool for the company, instead of one private contact list per salesperson.
• An audit log of actions in the workspace.

When someone leaves, the chat history stays, because it belongs to the Zalo number, not to the person. What remains is the handover: a team lead or supervisor assigns another person in charge to the leaver's conversations, following the handover list from step 2.

The same set-up is how you share one Zalo account with a team while everyone is still on board: who handles which customer, which conversations are still open, which are closed.

Be realistic, though. No tool can stop someone from saving a customer's phone number on their own phone. Access rights make sure the company keeps the data and knows who did what. The rest comes down to culture, and to the fifth way.

5. Cover customer data in employment contracts and internal rules

This section is general guidance, not legal advice. Vietnamese labour law has its own rules on what such clauses may cover and how far they can be enforced, so ask a lawyer or an HR adviser familiar with Vietnam before you rely on them.

Topics companies commonly consider for the employment contract, a confidentiality agreement or the internal labour rules:

• Confidentiality of customer information: customer lists, prices and transaction history belong to the company.
• Company property: SIMs, phones, work Zalo numbers and the data on them are returned when the employee leaves.
• Handover duties: the checklist from step 2 and how long the handover takes.
• Contact with customers after leaving: the most sensitive point, and the one where local legal advice matters most.

Clauses work best when people understand them from day one. Explain the reasons at signing, rather than only mentioning them when someone resigns.

Putting the five ways together

You do not have to do all five this week. If you pick one thing, move customers onto company Zalo numbers and keep the history somewhere the company controls. Then a resignation becomes a handover, not a lost account.

Frequently asked questions

Can an employee take Zalo customers when they leave?

Yes, if customers message the employee's personal Zalo number, because the contacts and history live on that person's phone. Company-owned numbers, central history and a handover checklist reduce the risk.

How do I protect customer data when employees leave?

Start the handover as soon as someone resigns: list active customers, open conversations and promises made. Have the leaver introduce the new contact to key customers. Over time, move customers onto company Zalo numbers stored in a system the company controls.

When an employee leaves, do their Zalo conversations in Hubz disappear?

No. In Hubz the chat history belongs to the Zalo number, not to the staff member, so it stays when they leave. You hand their customers over by assigning another person in charge to those conversations.

Should customer data be covered in employment contracts in Vietnam?

Many companies add confidentiality, return of company property and handover duties to the contract or internal labour rules. What such clauses may cover depends on Vietnamese law, so ask a local lawyer before relying on them.

Hubz is not affiliated with Zalo or VNG. Zalo is a trademark of its respective owner.