x-talk
Microsoft TeamsNEW

Service desk, HR and office admin in the chat your staff already use.

Employees message the X⁠-⁠TALK agent in Microsoft Teams like a colleague. The agent knows who is writing, answers from company knowledge, opens a ticket with the right requester and, when needed, hands the case to a consultant.

check_circle
No new app for employees
check_circle
Identity from Microsoft Entra ID
check_circle
The same agent as chat and phone
IT Service DeskApp · private chat ChatAbout
Anna Kowalska · 9:12 My VPN hasn't connected since this morning, I get an authentication error.
confirmation_number
IT Service Desk · 9:12 Hi Anna. VPN passwords changed on Monday. Sign out of the VPN client, sign in with your new company password and try again.
confirmation_number
Type a message
badge
Recognised: Anna Kowalska · anna.kowalska@company.com (Entra ID)
The agent knows who's writing

No “who are you?”. Microsoft provides the identity.

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.

check_circle
Tickets with the right requester. Nobody retypes names or e-mail addresses.
check_circle
“My tickets” from the first message. The agent checks the employee's cases without extra verification.
check_circle
Contact matched by e-mail. If the employee or site is in X⁠-⁠TALK contacts, the agent knows their context, such as their store or branch.
check_circle
Only your employees. The agent accepts messages only from your Microsoft 365 organisation.
confirmation_number
Ticket #4812 from Microsoft Teams
RequesterAnna Kowalska
E-mailanna.kowalska@company.com
ChannelMicrosoft Teams
CategoryNetwork · VPN
Steps takenSigned in again, new password
SummaryVPN authentication error since this morning
Sample data. The ticket goes to the ticketing system connected to the agent, such as ManageEngine.
For internal departments

One channel for the whole company. Different agents for different departments.

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.

computer
IT service desk Procedures, passwords, hardware and access. The agent walks through the fix and, if it doesn't help, opens a ticket with a description. „My VPN doesn't work” „How do I add a printer?” „What's happening with my ticket?”
badge
HR and people Leave, benefits, policies, onboarding. Answers from the department's documents; individual cases go to the HR team. „How do I request leave?” „When do I get my gym card?” „Where's the remote-work policy?”
apartment
Office admin Access cards, rooms, fleet, office supplies. Requests reach the right person. „My access card doesn't work” „How do I book a company car?” „The coffee machine is broken”
account_balance
Finance, safety and more Any department that answers repeat questions from staff can have its own agent. „How do I claim travel expenses?” „Where's the safety manual?” „When are October invoices due?”
smart_toy
The agent identifies the case Answers from knowledge or walks through a procedure.
alt_route
Hands over to a queue When the case needs a person or the employee asks for one.
support_agent
Consultant in the console Sees who's writing, the whole conversation and a summary.
chat
Reply in Teams The employee gets it in the same chat.
Handover to a consultant

When a person is needed, the employee stays in Teams.

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 →
Security

The bot lives in your Azure. Conversations only with your employees.

cloud
Your bot, your tenant The bot is created in your Azure subscription as a single-tenant app. You choose the region, such as West Europe.
verified_user
Every message verified We check the Microsoft signature, the Teams channel and your company's tenant. Messages from other organisations are rejected.
key
Bot key encrypted You enter the key only in the panel. It's never given in the Copilot chat and isn't visible in the API or MCP.
history
History and analytics Teams conversations appear in conversation history and analytics as a separate channel, with a summary and score.
Setup

A few steps for IT. Employees install nothing.

The X⁠-⁠TALK panel guides the admin step by step, checks the connection and generates a ready Teams app package.

cloud
01
Bot in Azure An Azure Bot resource (single-tenant) with the messaging endpoint copied from the panel. AZURE ADMIN
link
02
Connection in the panel App ID, tenant ID and key. “Check connection” shows at once whether the details are right. X⁠-⁠TALK ADMIN
download
03
App package The panel generates a ready .zip package with the agent's icons and name. X⁠-⁠TALK ADMIN
groups
04
Teams Admin Center Upload the app and pin it for chosen employee groups. TEAMS ADMIN
auto_awesome
The agent's Copilot knows the Teams channel status: it suggests next steps, switches the agent on or off in Teams and renames it. It doesn't accept bot credentials in the chat; they are entered only in the channel tab.
One agent, many channels

Teams is another channel of the same agent. Not a separate project.

Knowledge, tools, tickets, tests and analytics are shared across channels. Teams messages are billed like chat messages.

Questions about the agent in Teams

Do employees need to install anything?

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.

How does the agent know who's writing?

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.

Does the agent work in channels and group chats?

Today the agent chats in private 1:1 conversations. In a group chat or channel it asks for a private message.

Can employees talk to the agent by voice in Teams?

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.

Can employees send screenshots?

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.

What does the company need?

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.

When does a new conversation start?

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.

How much does it cost?

Teams messages are billed like chat messages, from the same credit pool. See pricing for details.

Your employees are already in Teams. Let the service desk be there too.

In a PoC we'll connect the agent to your Teams for a test group and show tickets with real employee identity.