End to end
Trace six stages before calling it integrated
- 01
Business account
Confirm ownership, verification and administrator access to Meta/WhatsApp resources.
- 02
Number and provider
Document portability, current use and technical connection.
- 03
Inbound message
Move text, media and minimum contact context into the service.
- 04
Teams routing
Map brand, language and intent to an accountable channel.
- 05
Agent reply
Handle windows, templates, delivery and errors visibly.
- 06
Retention
Map Meta, vendor and Teams copies to export and deletion paths.
Documented candidates
Three Teams-adjacent options with different scope
| Candidate | Publicly documented | Verify in the PoC |
|---|---|---|
| WebChat | WhatsApp input, Teams channel model and setup prerequisites | number, templates, media, status, fees and handoff |
| uWebChat | WhatsApp, Teams/Azure, media and Adaptive Cards | return path, archive, provider and price |
| Captivate Chat | WhatsApp alongside website, social, SMS and email | Teams UI, provider, governance and current support |
Total cost
The product licence is only one cost layer
- Meta/WhatsApp fees and possible provider charges
- product licence by channel, number, agent or conversation
- template creation, verification and number migration
- AI, translation and automation consumption
- implementation, privacy review, support and ongoing changes
Test protocol
Use real media and failure cases
- text, image, document, long message and emoji in both directions
- new contact, known contact and concurrent messages
- reply inside and outside the relevant messaging window
- approved, rejected and edited template
- wrong route, unavailable Teams channel and provider error
- export, deletion request and business-number offboarding