Inbox security when managed by multiple people is controlling who can access, who can read what, who can do what - so that no one shares the same password, does not reveal customer information, and no one arbitrarily deletes or changes data. This is a big problem when businesses let many employees handle messages at the same time: customer information (phone number, address, orders) is an asset that needs to be protected. Zenify recorded a 21% increase in conversion rate (approved) for standard decentralized businesses.
TL;DR
- Many people manage the inbox → must clearly decentralize who does what.
- Sharing passwords is prohibited — all actions must be traceable.
- Customer information is property — not disclosed, not taken personally.
- Decentralization: admin, reply, read only, report only.
- Employee leaves → revoke permission immediately.
Why is inbox security important?
Customer information is an asset: phone number, address, purchase history — exposure is a big loss.
Many people, many risks: people accidentally, people intentionally, people carelessly reveal.
Untraceable: If anyone can get in, we don't know who is doing what.
Reputation risk: a security error can cause customers to lose trust in the entire business.
Correct way to secure inbox
1. Decentralization by role
Vai trò | Quyền
Administration | Configuration, permissions, view all
Processing staff | Reply to assigned conversations
Read only | View, do not edit, do not reply
Report | Only see data, not enter conversations
Decentralization helps make "who can do what" clear, reducing the risk of accident/misunderstanding.
2. Sharing passwords is prohibited
One account per person — all actions tracked by name.
Do not give each other passwords, do not log in together.
Joint login = don't know who does what when something goes wrong.
3. Protect customer information
Only necessary personnel can view sensitive information.
Do not copy customer lists out.
Do not use guest information for personal purposes.
4. Procedures when employees take leave
Revoke rights immediately when quitting your job — don't wait for "end of the month".
Change the system password if in doubt.
Hand over the processing conversation to another person (see Multi-agent: chia inbox).
Common security mistakes
Sharing common passwords for the whole team — biggest risk.
No decentralization — new employees also see all data.
Do not revoke permissions when leaving — the old person can still access the system.
Save password in a visible place — screen sticker, public file.