What this review is
Verified documentation, not invented hands-on experience
We reviewed the current WebChat website, Microsoft Marketplace entry, setup guide, native-Teams explanation and release notes. Product claims are attributed to those sources and separated from our scenario-based conclusions.
We have not yet completed an independently recorded production load test, security assessment or billing checkout. Accordingly, there are no fabricated performance scores, star ratings or user-experience claims.
Core strength
The agent works in the Teams channel thread
The vendor describes each incoming request as a post in the assigned Teams channel and the agent response as a reply in that thread. Channels can represent a site, language, department, product or campaign.
That is materially different from a product that merely sends a notification to Teams or embeds an external inbox as a tab. It can reduce context switching, but only if channel volume, permissions and notification practices remain manageable.
Documented scope
Widget, social messaging, SSO and automation
| Area | Documented capability | Buyer check |
|---|---|---|
| Website chat | Configurable widget using a channel-specific script | CSP, consent, accessibility, offline state |
| Social messaging | WhatsApp, Instagram and TikTok named by the vendor | Platform prerequisites and third-party charges |
| Identity | Microsoft Entra SSO and Teams membership model | Admin roles and least privilege |
| Automation | Power Platform triggers/actions and a Foundry AI pattern | Premium licences, Azure usage and governance |
| Licensing | Per channel with unlimited users per channel | Current numeric price and channel count |
| Reporting | Operational history exists in the workflow | Exact dashboards, exports and KPIs not yet verified |
Best and weaker fit
Who should test WebChat first?
- Strong fit: Microsoft 365 organisation, Teams channels are the operational workspace, many potential agents share a limited number of routes.
- Strong fit: different sites, languages or campaigns need explicit Teams channel routing.
- Potential fit: own Power Platform and Foundry automation is preferred over a closed built-in bot.
- Weaker fit: Slack and Google Chat must be supported alongside Teams.
- Weaker fit: voice, complex queues, workforce management or full contact-centre reporting are mandatory.
- Weaker fit: self-hosting and public source-code control are hard requirements.
Before procurement
Questions the public material does not yet answer sufficiently
- current numeric plans, billing intervals, taxes and exact trial/POC conditions
- DPA, subprocessors, concrete hosting regions, retention and deletion mechanics
- SLA, support hours, escalation and service-credit terms
- reporting dashboards, export formats and operational analytics depth
- high-volume channel behaviour and practical notification governance
- independent accessibility, security and performance test results