Separate the layers
WordPress integration and Teams integration answer different questions
Layer one places a launcher and widget on WordPress through an official plugin, a generic script, tag management or controlled theme code. Layer two determines where an enquiry arrives, who takes ownership and how the answer travels back to the visitor.
A tool can therefore offer a convenient WordPress plugin while requiring its own support inbox. Conversely, a Teams-focused tool can be embedded cleanly by script without a dedicated WordPress plugin. Procurement and acceptance testing should score both layers independently.
Four documented routes
WebChat, Tidio, Lime Connect and Chatwoot on WordPress
| Tool | WordPress delivery | Regular agent work | Microsoft Teams position |
|---|---|---|---|
| WebChat | Generic script; multiple instances and LiveTest documented | Teams channel and thread reply according to the vendor | Direct Teams focus; no dedicated WordPress plugin in the reviewed guide |
| Tidio | Official plugin or JavaScript alternative; do not use both | Tidio Inbox | Plus/Premium integration documented; pilot the exact reply round trip |
| Lime Connect (formerly Userlike) | Install and activate plugin, then enter widget key | Lime Connect Message Center | No Teams entry in reviewed integration catalogue; a bespoke API route is not ruled out |
| Chatwoot | Upload GitHub plugin ZIP; configure installation URL and website token | Chatwoot Inbox, cloud or self-hosted | No native Teams-channel reply path verified in the reviewed sources |
WebChat on WordPress
Create a maintainable installation without duplicate widgets
- 01
Choose channel and owners
Create a dedicated test channel, verify Teams permissions and map website, language and responsible team explicitly.
- 02
Load the script once
Add the asynchronous channel-specific script through one maintainable integration point; do not repeat it in a theme, plugin and tag manager.
- 03
Check consent, CSP and caching
Agree the lawful loading point, allow only required origins, clear page and CDN caches and inspect the frontend in a private window.
- 04
Test a real round trip
Send a visitor message, confirm the intended Teams channel, reply from its thread and verify receipt on desktop and mobile.
- 05
Document rollback
Record the insertion point, channel mapping, plugin or theme owner and rapid disable procedure for incidents or incorrect routing.
Production acceptance
A visible chat button is not an end-to-end test
- Explicitly include or exclude the widget on home, article, landing, checkout and authenticated templates.
- Test theme changes, page builders, cache and optimisation plugins, JavaScript minification and Content Security Policy.
- Review keyboard operation, focus, zoom, contrast, accessible names and mobile overlays.
- Approve privacy notice, DPA, subprocessors, hosting, retention and deletion from current contractual documents.
- Simulate business hours, offline behaviour, notifications, absence cover, simultaneous replies and escalation.