Truly native in Microsoft Teams—not just embedded

Inquiries are routed to the correct channel—and responses are provided directly from the thread

WebChat / Your Own AI Chatbots in Microsoft Teams—Without Vendor Lock-in / Truly native in Microsoft Teams—not just embedded
Native vs. embedded

Truly native in Microsoft Teams — not just a menu item with someone else's interface

Many providers merely add an entry to the Microsoft Teams sidebar and show their own interface behind it — an external system, framed inside Microsoft Teams. WebChat works with the conversations themselves: every request lands in the right Microsoft Teams channel, and your reply goes straight from the channel thread back to the customer.

The difference at a glance

Embedded tool vs. native conversation

Other providers
Embedded in Microsoft Teams
Microsoft Teams Microsoft Teams
Chat
Calendar
A Provider
Microsoft Teams
Support
Sales
HR
no new messages
app.anbieter-tool.com/inbox
Inbox Contacts Reports Settings
Replies happen here — in the external system, separate from Microsoft Teams.
External system
A menu item on the left in Microsoft Teams — behind it just the external interface. The Microsoft Teams channels stay out of the loop; every reply happens in the external tool.
WebChat
Truly native
Microsoft Teams Microsoft Teams
Chat
Calendar
WebChat
Microsoft Teams
S Support 1
V Sales
H HR
Support Posts Files
MK WhatsApp
Maria Kleinvia WhatsApp · 13:37
Hi, my invoice for March is wrong — could you please check it?
JS
JensSupport · 13:38
Sure, Maria — I'll look into it right away and get back to you shortly.
@webchat Reply to the customer…
WhatsApp Reply goes back to WhatsApp in real time
The conversation lives in the Microsoft Teams channel. You reply in the thread with @webchat — and the answer goes straight back into the incoming channel, with no second interface.
Microsoft Teams
Conversation in the channel
Every request appears as a post in the right Microsoft Teams channel — not in some external inbox. Intelligent routing automatically brings it to the right department.
WhatsApp
Reply in the thread
You reply with @webchat right in the channel thread. The answer goes back in real time to WhatsApp, Instagram, TikTok or the website chat.
WebChat
No second interface
No embedded tool, no second login. Identities, permissions and roles come entirely from Microsoft Teams and Microsoft Entra ID.
Compared directly

What an embedded tool can't do

Embedded tool WebChat
Visible in Microsoft Teams asMenu item / tabNative channels
Incoming message appearsin the external interfacein the Microsoft Teams channel
You send the replyin the external toolin the channel thread
Reply goes back into the incoming channel
Intelligent routing to the right department
Identity & permissions from Microsoft Entra ID
Human & AI in the same thread (human-in-the-loop)
No second inbox, no second login
How WebChat replies

One conversation — one path, back into the incoming channel

WhatsApp
Customer writes
Message via WhatsApp, Instagram, TikTok or website chat.
Microsoft Teams
Right Microsoft Teams channel
Routing places the request as a post in the matching channel.
JS
Reply in the thread
A human or AI replies with @webchat right in the channel.
WhatsApp
Back to the customer
The answer goes back into the incoming channel in real time.

your chat, your team, your decision

See for yourself how a conversation lands in the right Microsoft Teams channel and goes back to the customer. 7-day POC with 25 channels, no SaaS contract.

WhatsApp

All WhatsApp messages from your customers flow centrally into Microsoft Teams. Your team sees and processes the requests like normal Teams chats, without a separate WhatsApp account or additional software. Everything stays in one system, the overview is maintained and nobody has to switch between apps.