Enterprise · Part of Team Chat
Customer conversations
The same chat engine, extended to the people your clients serve: every conversation is bound to a client account and line of business, with each message attributed to the customer, agent, bot, or supervisor who sent it.
For the operator
You work customer conversations in a dedicated console, not your internal chat page, and you only get one if you're the right person to take it. An assignment gate checks that the conversation is in your client scope, then your shift eligibility if the tenant turns that on, then that you're present and available, then that you're under your concurrency limit, so a conversation never lands with someone out of scope or already at capacity. The customer never sees any of this: they reach you through a branded, embeddable widget on the client's site, authenticated only by a widget key and a per-conversation token, with the greeting, pre-chat form, and allowed origins set per client.
Business impact
Your clients get a real support channel for their own customers without leaving FrontLine, and each conversation stays scoped to the right client and answered only by an agent who is in-scope, available, and not overloaded.