How to build a virtual customer support office without exposing private rooms
Customer-facing space should feel open at reception and private everywhere else.
Separate visitor identity from employee membership
Visitors should verify a lightweight account and provide a display name before entering. That identity must not grant employee features such as private team chat, work status, administrative settings, or unrestricted room access.
Use short-lived visitor membership, auditable entry information, and a defined guest allowance. This prevents a public link from becoming a free substitute for paid employee seats while still allowing real customers to attend meetings.
Design the map around approved destinations
Spawn external visitors at reception. Portals and minimap travel should land only on walkable tiles near an approved destination, never inside a restricted area, on a building, or behind a collision boundary.
A locked destination should look different from a working portal. Explain that access is restricted and provide a request or contact action rather than letting the visitor repeatedly collide with an invisible rule.
Make employee takeover operational
Employees need a queue showing the visitor, purpose, waiting time, conversation summary, and current owner. Two employees must not be able to claim the same call or inquiry at the same time.
After takeover, the employee can continue in chat, accept a browser call, schedule a follow-up, or invite the visitor into a private consultation room. Retention and transcription consent should remain visible throughout that transition.
Sources and further reading
Kiguri product overview, Kiguri pricing, security information, and Kiguri guides.