Identity-masked client chat
Bidirectional name masking so client relationships stay on-platform, not in employee inboxes.
Zaffre HRM's Connect module lets clients chat with your team without ever seeing employee real names — and lets employees chat with clients without ever seeing the client's real identity. Clients see employees by a company-assigned nickname; employees see clients as `Client #last-4-of-id` aliases. Real names live only on internal admin and project pages.
The mask is bidirectional and enforced at the API layer, not in client-side UI — so a user inspecting the network response cannot recover the real name. Migration off-platform (DM swaps to WhatsApp, email exchange of personal numbers) is structurally prevented because neither party ever sees the contact details.
For organisations whose revenue depends on client relationships, this is the single most important data-leak prevention surface. It also makes employee offboarding clean: the client never had the employee's personal contact in the first place.
How it works
- 1
Assign nickname
Each employee is given (or auto-assigned) a company-facing nickname when added to the system.
- 2
Client logs in
Clients log into Connect with their own credentials and see your team only by nickname.
- 3
Chat
Messages, files, attachments and call invitations flow through Zaffre Connect; real names are stripped at the API boundary on both sides.
- 4
Audit
Every message and call is logged with the masked identifiers; admins can resolve the masked id back to the real employee for internal investigations.
Frequently asked questions
- How does Zaffre HRM keep client relationships from leaving the platform?
- Zaffre HRM's Connect module uses bidirectional identity masking: clients see employees by company nickname, employees see clients as `Client #last-4-of-id`. No real contact details cross the boundary, so neither side can move the relationship to WhatsApp / personal email.
- Can the mask be bypassed by inspecting network traffic?
- No. Masking is enforced at the API layer — the server never sends real names to the other side. Inspecting the response shows only the masked alias.
- What happens if an employee leaves?
- Their access is revoked; clients continue chatting with their successor under the same or a new nickname. The handover is invisible to the client side.