English
English
English
English
Guide 162 of 1696 min read
One switch lets your Agents answer every chat without ever seeing a customer's full name, phone number, email or username. Owners and Admins still see everything.
Picture your best salesperson resigning on a Friday, and by Monday morning half their customers are chatting with them on their personal WhatsApp. It happens more than anyone admits, and it stings. We hold one belief here: a customer's number is your business's asset, not a perk for whoever happened to answer their first chat. So an Owner can flip one switch, and Agents keep serving every chat without ever seeing a customer's full name, number, email or username.

Only Owners and Admins see the card and can change it. Every change is recorded: who changed it and when. It's off by default, so a workspace that never turns it on works exactly as before.
| Where | What an Agent sees |
|---|---|
| Contacts on the customer's profile and in the ticket panel | A number like ***********90, an email like b***@example.com, a username like b***, with a shield mark. No copy button, no Open in WhatsApp, no remove button |
| The customer's name | Only the first letter of each word: Budi Santoso reads B*** S***, enough to tell two chats apart. A guest name KIRA.id made up stays as it is, because it names no one. The name can't be edited by an Agent |
| The chat itself: the customer's, the AI's and the team's messages | Numbers, emails and the words of the customer's name inside a sentence are masked the same way; every other word stays |
| The customer's form answers, the ticket summary and the next step | Same: the content reads fine, the numbers and emails are masked |
| Reports, Customer feedback, notifications, phone push and the Monday summary email | Customer quotes and sample conversations still show, with names, numbers and emails masked. Searching Customer feedback by a number doesn't find a quote either |
| Search in Customers, Inbox and Search (⌘K) | Codes still work. A name is found only by a whole word of it: "Budi" finds Budi, "Bud" finds nothing, and the result still shows the name masked. A number, part of one, an email or a username finds nobody. The Inbox search box says "Search name, code" |
| Maybe the same person suggestions | Not shown. Owners and Admins decide on merges |
We keep the last two digits of a number and the first letter of each word of a name on purpose: enough to tell two numbers or two customers apart, too few to dial or to look someone up.

The flow is simple. The AI answers product questions. An interested customer fills in their details in a chat form, and the Agent checks the answers (name, city, what they need) and sends the offer in the same chat. A returning customer usually goes back to whoever served them last, and a ticket nobody picks up within your Pick up within limit moves on to the next teammate. Commissions stay clear, and the customer stays with the business.
A salesperson's job is to answer and close the sale, and for that they don't need to know who the customer is outside the chat. We dislike half measures that hide one field while the number can still be searched, copied from a summary, or read in the AI's sentence. So the masking happens on our server, everywhere a number can show up, search included. What you can't see, you can't guess either.
No. Owners and Admins always see full contact details. This switch only applies to the Agent role.
No. Numbers and emails inside messages are masked for Agents, whoever wrote them.
Only the first letter of each word, so Budi Santoso reads B*** S***. A full name is enough to find someone on Instagram or Facebook, so it is hidden like the number. Owners and Admins see the name as usual.
Yes. Agents reply from the console, and the message goes out from your business WhatsApp number. Only the customer's number stays out of sight.
No, neither the full number nor part of it. Search by the customer's code, or by a whole word of their name: part of a word finds nothing.