Channels

Web Chat Widget

Chat on your own site, in the same inbox as everything else.

Not every visitor wants to hand over a phone number, and in a lot of markets WhatsApp is not the default anyway. The web chat widget puts a conversation on your own pages — answered by the same bots, the same agents and the same customer record that handle WhatsApp, Instagram, Messenger and TikTok.

Web chat in the shared inbox

Web chat

WhatsApp

Instagram

Messenger

Unassigned

Sales

Chats on site today

212

Median first reply

0m 24s

Answered by bot

68%

The visitor who was never going to message you

Somebody reads three pages, opens the pricing table twice, and leaves. They had one question. They were not going to fill in a contact form and wait a day for an email, and they were not going to open WhatsApp and give a business their personal number to ask it. The intent was there for about ninety seconds, on a page you own, and nothing on that page could hold a conversation.

What you get

One snippet, any site or app

Drop the widget into your website, your web app or your customer portal. It carries your colours, your name and your language, and it works on a phone screen as well as a desktop one.

The same bots you already built

Chatbot flows, AI agents, knowledge answers and saved replies run on web chat without being rebuilt. You change the wording in one place and every channel follows.

Visitor context on arrival

The agent sees the page they are on, how they got there and any details your site already knows about them, before typing a word.

One customer record

A visitor who chats on your site today and messages WhatsApp next week is one contact with one history — not two strangers in two systems.

What the agent sees before replying

Visitor context

page/pricing
referrergoogle.com
localeen-AE
deviceMobile · Safari
plan: trialcart: 2 itemsaccount: 8241

During the chat

chat.opened

on /pricing

0s
bot.answered

billing cycle question

12s
handover.requested

asked for a person

48s
contact.updated

email captured

51s
Context is saved to the contact, so the next conversation starts ahead.

The visitor arrives with their context already attached

Web chat has one advantage no messaging app can offer: you own the page. The conversation opens with the page they were reading, how they reached it and whatever your site already knows about them, so neither the bot nor the agent has to start with "how can I help?" and hope.

  • Page, referrer and locale handed over as the chat opens
  • Your own values passed in — plan, cart, account tier, anything
  • Everything written to the contact record, not just shown once
One agent, several runtimes

Support & Sales agent

One definition · steps, tools, guardrails

Web chat

Answers visitors on your own pages.

Messaging

WhatsApp, Instagram, Messenger, TikTok.

Voice

Speaks with callers using the same tools.

Change the agent once and every surface follows.

One definition, every surface it has to run on

A website bot that knows different things from your WhatsApp bot is a maintenance problem waiting to happen. Build the flow or the AI agent once — its steps, its knowledge, its tools, its guardrails — and web chat is simply another place it runs.

  • Web chat, messaging apps and voice share one agent definition
  • Change an answer once and it changes everywhere
  • The same handover rules and the same escalation path
Web chat routing

Live on site

Pricing question

/pricing

Checkout failed

Support

Arabic visitor

GCC

Rules

Pricing → Sales

Checkout → Support

Arabic → GCC team

Available

Hana2 open
Daniel5 open
Faisal3 open

Handover to a person, in the same thread

The moment a visitor needs a human is the moment most website chat falls over — a ticket is raised, an email goes out, and the person who was ready to buy is gone. Here the bot hands the live conversation to a queue, the rules pick an owner, and the visitor keeps typing in the same window.

  • Route by page, language, plan or whatever the bot found out
  • Round-robin inside a team, or straight to a named owner
  • Nothing the visitor already said is repeated back to them
Which one catches whom

Web chat widget vs WhatsApp button

No appAnonymousPage contextSame inbox

Web chat widget

Conversation stays on your page

WhatsApp button

Opens WhatsApp with a message

Both feed one inbox and one contact record — the difference is who they catch.

A widget on the page, or a button into WhatsApp

These are two different jobs and most sites want both. A WhatsApp click-to-chat button suits visitors who already live in WhatsApp and are happy for you to have their number. The web chat widget catches everyone else — the anonymous ones, the desktop ones, and the markets where WhatsApp is not the default.

  • Run both: the button for WhatsApp users, the widget for the rest
  • Either way the conversation lands in the same shared inbox
  • Our free WhatsApp chat widget builder still generates the button

How it works

  1. 1

    Add the widget

    Copy the snippet into your site, or install it in your app, and set the colours, the greeting and the languages it should offer.

  2. 2

    Decide who answers first

    Point web chat at a bot, an AI agent or straight at a team, and set the moment a conversation becomes a person's job.

  3. 3

    Work it like any other channel

    Web chats arrive in the shared inbox with assignment, notes, tags and reports, beside WhatsApp, Instagram, Messenger and TikTok.

Frequently asked questions

Put a conversation on your own pages

Add web chat to your site and let the bots and agents you already have answer it.