The web widget is a chat box your customer embeds on their website. Behind it sits either an AI agent built in Agent Builder or a WhatsApp workflow, so the same logic serves their site visitors and their messaging channels.
It is a paid module.
Why it matters commercially
Most of your customers already pay someone for website chat. This folds it into the messaging platform they are already buying, and the conversation uses the same agent, knowledge base and escalation rules as their WhatsApp and RCS traffic. One place to update, one set of analytics.
It is also the easiest channel to demo. There is no carrier, no template approval and no sender ID to wait for.
What the widget gives the visitor
- The customer’s own branding and avatars.
- Formatted replies rather than plain text blocks.
- Quick suggestion chips so visitors can tap instead of typing.
- A typing indicator, so the conversation feels live.
- A “Powered By” footer, which is worth checking against your white label expectations before a reseller launches it.
Security worth mentioning to buyers
The widget sits behind login, with CSRF validation and rate limits, and it shows a friendly fallback message when the provider behind it is unavailable rather than breaking the page. That last part matters: a chat box that errors in public looks worse than no chat box.
Where it fits next to the other channels
| Channel | Who starts the conversation | Needs carrier or platform approval |
|---|---|---|
| Web widget | The website visitor | No |
| Either side, within WhatsApp’s rules | Yes, templates and a number | |
| RCS | Either side | Yes, brand, bot and template approval |
| Telegram | The user must message the bot first | No, but the bot must exist |
| SMS | Either side | Sender ID, and DLT where it applies |
Use this when a customer asks where to start. The widget gets them live the same week, while the regulated channels are still in approval.
Practical advice for onboarding
- Put the widget on pages with intent, such as pricing and support, not just the home page.
- Ground it before launch. An agent with the customer’s real help content answers properly from day one.
- Decide escalation before launch too. Where does a conversation go when the agent cannot help, and who is watching that queue during business hours.
- Agree who owns the model cost when the widget runs an AI agent, since that is separate from your messaging charges.
Related articles
- AI Agent Builder: What It Is and What It Is Not
- Journey Builder: Cross-Channel Journeys
- Telegram Chat Plugin and Telegram Notifications: Two Different Things
- WhatsApp chat agent settings