OleonYour existing bots work on it.
Menus, buttons, lists and media all render in a browser, which is the one place they need no translation at all. A flow built for WhatsApp runs on the website without being rebuilt for it.
Web widget · Answer them
BetaThe chat on your website, answered where everything else is.
A visitor reading your pricing page should be able to ask, without finding a phone number first. The widget puts that conversation in the same inbox as WhatsApp, with the same agent behind it.
This one is in beta. Not every part described here is switched on yet, so read it as what it will do and tell us where it is wrong.
One snippet, and the page stays fast.
The loader and the per-site settings are published as static files that a visitor gets from the edge. Only an actual conversation reaches us, which is the only traffic we should be paying to serve.
A visitor is identified honestly.
Somebody who has not signed in anywhere is a browser, and the product treats them as one. What a visitor can claim about who they are is checked rather than believed, which is not true of the version that exists today.
It is the channel that already half exists.
Web chat is already in the inbox, with its own icon and its own conversations. What is missing is the sending half, which is what this builds rather than a new channel beside it.
Included
What this one holds.
- A snippet for your site
- Text, images, documents and voice
- Menus, buttons and lists
- Your brand colour and greeting
- Conversations in the shared inbox
- Scout answers the widget too
- Flows run without being rebuilt
- Loaded from the edge, not from us
- A visitor identity that is checked
Questions
Before you ask.
The ones we hear most about Web widget. If yours is not here, the answer is a message away.
Will it slow our site down?
The loader is small and cached at the edge, and the settings it reads are a published file rather than a request to us. The heavy part loads when somebody opens the chat.
Can a visitor carry on the conversation on WhatsApp?
That is the point of one inbox. How a browser visitor is matched to a phone number is one of the decisions the plan still lists.
Does it work with the bots we already built?
Yes, and that is the reason to build it this way. The engine already produces what a browser can render natively.
Keep exploring.
More of what Oleon does.
All productsIt starts with one conversation.
Bring the channels you already answer on into one place, and see what the rest of the week looks like.
Not ready to sign up? Join the waitlist and we will come to you.
