Skip to content
All guides

Business tools

How Many Zalo Accounts a Customer Team Should Buy

Teams buying Zalo accounts tend to buy too few and share a login, or buy too many for volume. This guide sets the quantity by counting accountable people, using Zalo's own rules on account limits and login codes.

Contents

The quantity question comes before the listing question

When a team decides to handle customer conversations on Zalo, the first instinct is to look at listings. A better first step is to settle how many accounts you actually need, because the answer changes which listings are worth comparing and how much you spend.

Two mistakes are common. One is buying a single account and sharing its login among several people. The other is buying more accounts than there are people to run them, in the hope that more accounts means more reach. Zalo's own rules make both of those poor choices, and the reasoning gives you a cleaner way to count.

Why one shared login does not hold up

Zalo's two-layer security, once turned on, asks for the password plus a one-time code sent to the linked email whenever someone signs in on a new device. A shared login means that code has to travel from whoever reads the email to whoever is signing in. Zalo's terms advise users to protect their PINs and one-time codes and not to share them or the devices that store them. A team that passes codes around in a chat is working against the account's own protection.

There is an accountability problem too. When a customer complains about a reply, a shared account cannot tell you who wrote it. And when one person leaves, everyone's access has to change at once.

Why extra accounts are not extra reach

Zalo's terms say it limits how many accounts a user may register, and its community policy says the same about personal accounts each user can create. The same policy treats high-frequency posting or interaction, whether manual or automated, as spam. An account with no person behind it tends to drift toward exactly that pattern, or sits unused until it becomes a problem of its own.

So the honest unit of purchase is not a device or a block of contacts. It is a person who will use the account by hand, in their own name or a clearly named role, within Zalo's rules.

A counting method you can apply in ten minutes

List every person who will answer customers on Zalo. Mark those who need to reply under a name customers will recognize. Mark those who can receive their own login codes at an email address they control. Finally, check which roles genuinely overlap in time: two people on different shifts may be able to share one role account if the role, not the person, is what customers see, but only if each handover includes a fresh device check.

The accounts worth buying equal the number of people, or role-with-shift pairs, who pass all of those marks. Anyone who does not need to talk to customers on Zalo does not need an account at all.

Count for the team you have now, not the team you might have next year. Buying ahead leaves accounts sitting idle with nobody responsible for them, and Zalo's terms allow it to stop service to accounts left unused for a long stretch. When someone joins, buy for that person then. When someone leaves, the account stays with the role: move its number and email to the next holder's details and review the logged-in devices, rather than buying a replacement and abandoning the old one.

A worked example: four staff, three accounts

A hypothetical bicycle parts seller has four people. Two handle sales during the day, one handles after-sales repairs, and a part-timer covers weekends.

Applying the method: both sales staff reply under their own names and receive their own codes, so they get one account each. The repair technician also replies directly to customers, so that is a third account. The weekend part-timer covers the sales role on days when neither salesperson works, so the team considers letting the part-timer use one of the sales accounts. They decide against it, because both salespeople sometimes answer messages on weekends from home, and two people signed in to one account at once is exactly the confusion they want to avoid. Instead, the part-timer takes over the repair account on weekends, when the technician is never working, with a device check at each handover.

The total is three accounts. Not one shared login, and not five.

Zalo's terms apply to every one of them

Each account you buy carries the same platform position. Zalo's community policy says it does not allow buying, selling or exchanging accounts, and Zalo can act on accounts that break its rules. Zalo is not affiliated with rStock, and a listing here is not an offer from Zalo or a promise about how Zalo will treat the account. Follow Zalo's terms for each account, and factor in that Zalo could restrict any of them.

Buying the quantity you counted

On rStock, an order is one product with the quantity you choose, paid from your rStock balance, so buying three accounts from one listing is a single order. Each delivered item is a separate stock entry, and the same item cannot be sold to two buyers. Before choosing the quantity, make sure the listing describes the login, profile and recovery details in a way that works for every account you need, because you cannot raise questions with the store before paying. After delivery, assign each account to its person on the day it arrives, move the number and email to ones that person controls, and turn on two-layer security.

Frequently asked questions: How Many Zalo Accounts a Customer Team Should Buy

Keep reading