On website chat the agent has to ask for details and verify them. In Teams the employee is already signed in to their company Microsoft account, so from the first message the agent knows their name and e-mail address.
Each agent has its own knowledge, tools and name in Teams. Employees add the ones they need, and the admin can pin them for chosen groups.
A consultant takes over in the X-TALK console, with the history and a summary. Their replies arrive in the same Teams chat, so the employee doesn't switch tools.
Agent console →The X-TALK panel guides the admin step by step, checks the connection and generates a ready Teams app package.
Knowledge, tools, tickets, tests and analytics are shared across channels. Teams messages are billed like chat messages.
No. The Teams admin uploads the agent app in Teams Admin Center and can pin it for chosen groups. Employees see the agent in Teams and simply message it.
From the employee's Microsoft account: Teams passes the name and e-mail from Microsoft Entra ID. The agent doesn't need to ask, and tickets have the right requester.
Today the agent chats in private 1:1 conversations. In a group chat or channel it asks for a private message.
No. In Teams the agent holds a text conversation. Voice conversations are available by phone, on the website and in the X-TALK mobile app.
Today the agent in Teams handles text messages. If a screenshot is needed, the agent can hand over to a consultant or open a ticket the employee can attach a file to in the ticketing system.
An Azure subscription (the F0 bot plan is enough), permission to register apps in Entra ID and the Teams administrator role. The panel guides the rest.
After 8 hours of silence or when the employee types “new conversation” (in Polish: „nowa rozmowa”). The previous one is closed, summarised and saved in history.
Teams messages are billed like chat messages, from the same credit pool. See pricing for details.