Web Chat Widget
A fast chat SDK for your website and your app — arriving with your customer already identified.
Most website chat is a stranger typing into a box. This one is not. The widget embeds in your site or inside your native app, loads fast enough that it is never the reason a page feels slow, and starts the conversation already holding what your product knows — the page, the plan, the order, the signed-in account. The AI agent can then do something about it on the page, and every message lands in the same team inbox as WhatsApp, Instagram, Messenger and TikTok.
Nadia Home
Replies in seconds
Context passed in by the page · answered in the shared team inbox
Your product knows everything. Your chat box knows nothing.
A customer is signed in. Your application knows their name, their plan, their last three orders and the exact screen they are stuck on. Then they open the chat bubble and the first thing it says is "how can I help?" — and the second thing it asks for is their email address. Two minutes of a paying customer's time goes on re-establishing facts you already had on screen. Worse, the answer usually ends in "go to Settings, then Billing, then click Change plan" — instructions, when the agent was standing on the very page that could have done it.
What you get
One embed, website or native app
Put the widget on a marketing site, inside a signed-in web application, or inside your iOS or Android app. It is built to load quickly and stay out of the way of your page, and it works on a phone screen as well as a desktop one.
Context and profile passed in by the host
Your page or app hands the conversation whatever it already knows — the page in view, the customer's identity, their plan, their cart, their account state — so the bot and the agent both open on a briefing instead of a blank.
Events and page actions
The conversation is two-way with the page around it. The widget reports what happened in the chat, and the AI agent can trigger an action back in your interface instead of describing the steps.
Your design, one shared inbox
Colour, greeting, position, launcher and language are yours to set. Behind it, web chats sit in the same queue, on the same contact record, with the same routing, notes, tags and reports as every other channel.
Your chat widget
One embed · one agent · one inbox
Website
Anonymous visitors on your public pages.
Mobile app
Embedded inside your iOS or Android app.
In your product
Docked in the signed-in experience.
Same conversation, same contact, wherever it was opened.
One widget, wherever your customers already are
A marketing site, a signed-in dashboard and a mobile app are three different places with the same customers in them, and most tools make you pick one. This is a single embed that runs in all three, backed by one agent definition, one inbox and one contact record — so a conversation that starts in the app and continues on the website is still one conversation.
- Public website, signed-in web application, or a native iOS or Android app
- Built to load fast and stay light on the pages it sits on
- The same bots, AI agents and human team answer all of them
Passed in by the page
During the chat
chat openedon /pricing
agent answeredbilling cycle question
handover requestedasked for a person
contact updatedemail captured
The conversation opens with what the page already knows
Web chat has an advantage no messaging app can offer: you own the surface it runs on. The widget takes what your page or app hands it — where the visitor is, how they got there, what language they read in, and any values of your own — and the conversation starts from there rather than from "how can I help?".
- Page, referrer, language and device handed over as the chat opens
- Your own values passed in — plan, cart, account state, anything you name
- Written to the contact record, so the next conversation starts ahead too
Signed-in session
your app says who this is
Profile passed in
plan · account · order
What they tell the bot
captured mid-conversation
Contact record
One record. A later WhatsApp message continues the same history.
Signed in? Then it already knows who they are
On a public page the widget deals with a visitor. Inside your logged-in product it deals with a named customer, because your application tells it who is on the other side. The profile comes in with the conversation — so nobody is asked for an email address they typed into your signup form months ago, and the agent can answer about this account rather than in general.
- Your app identifies the signed-in customer to the widget
- The profile your product holds is attached to the conversation
- Anonymous visitors still work — identity is what you choose to pass
Open a screen
take them there
Prefill a form
with what was said
Apply a discount
on the live cart
Start a checkout
in the same tab
Highlight a section
scroll and mark it
Fire an event
back to your app
agent → page action · open plan settings (annual)The action list is yours: the agent can only trigger what you allow.
The agent can act on the page, not just describe it
This is the part most website chat cannot do. The widget and the page talk to each other in both directions: the chat reports events out to your application, and the AI agent can trigger an action back inside your interface. "Go to Settings, then Billing, then Change plan" becomes the page opening on the plan screen while the agent is still explaining it.
- The agent triggers actions you define in your own interface
- The widget fires events your application can react to
- You decide exactly which actions the agent is allowed to take
Modes in the widget
Text chat
Bots, AI agents and your team.
Voice agent
Talk instead of typing.
Live avatar
An agent that answers on camera.
The widget is text chat. Voice and avatar are add-ons on top of it.
Typed, spoken, or with a face — the last two are add-ons
The widget on its own is text chat, answered by your chatbot flows, your AI agents and your team. On top of that, two paid add-ons change how the agent shows up: a voice-only agent the visitor can talk to instead of typing, and a live avatar agent that answers on camera. Both are separate from the widget and switched on deliberately, not bundled in.
- Text chat is what the widget does out of the box
- Voice-only agent: the visitor speaks, the agent speaks back — add-on
- Live avatar agent: the same agent with a face on screen — add-on
Live on site
Pricing question
/pricingCheckout failed
SupportArabic visitor
GCCRules
Pricing → Sales
Checkout → Support
Arabic → GCC team
Available
Handover to a person, in the same window
The moment a visitor needs a human is where most website chat falls over: a ticket is raised, an email goes out, and the person who was ready to buy has gone. Here the bot hands the live conversation to a queue, the rules pick an owner, and the visitor keeps typing in the window they already have open — with everything they said, and everything the page passed in, still attached.
- Route by page, language, plan or whatever the bot found out
- Round-robin inside a team, or straight to a named owner
- Assignment, notes, tags, SLAs and reports, same as every channel
Design
Preview
Nadia Home
Hi Layla — still looking at the Growth plan?
Change it in the panel; the widget on your site follows.
It should look like your product, not like a chat tool
A widget that arrives in somebody else's colours reads as bolted on, and customers notice. Brand colour, the greeting, the launcher, which corner it sits in, whether it opens by itself and what language it speaks are all yours to set — so it looks like a part of the page it is on rather than a visitor from another company.
- Your colour, your name, your greeting and your launcher
- Position, corner and open-on-load behaviour under your control
- Right-to-left and left-to-right, matching the page it sits on
Web chat widget vs WhatsApp button
Web chat widget
Conversation stays in your page or app
WhatsApp button
Opens WhatsApp with a prefilled message
Both feed one inbox and one contact record — the difference is what they can carry.
A widget on your page, or a button into WhatsApp
These are two different products and most sites want both. Our free WhatsApp chat widget builder makes a click-to-chat button: it hands the visitor over to WhatsApp, which suits people who already live there and do not mind you having their number. The web chat widget keeps the conversation on your page — and it is the only one of the two that can be handed your page context or a signed-in profile.
- Run both: the button for WhatsApp users, the widget for everyone else
- Only the widget receives context, profile and page actions
- Either way the conversation lands in the same shared inbox
How it works
- 1
Embed it
Add the widget to your site, your web application or your mobile app, and set the brand, the greeting, the position and the languages it should offer.
- 2
Hand it your context
Pass in the page and, where the visitor is signed in, the customer profile your product already holds. Choose which events matter to you and which actions the agent is allowed to trigger.
- 3
Decide who answers
Point it at a chatbot flow, an AI agent or straight at a team, set the handover moment, and work the conversations in the shared inbox beside every other channel.
Frequently asked questions
Related features
Keep reading — these work closely with this one.
Put a real conversation inside your product
Embed the widget on your site or in your app, hand it the context you already have, and let the agents you already built answer.