Website Chat Widget That Connects WhatsApp, Instagram, Messenger and RCS

The complete guide

Website Chat Widget That Connects WhatsApp, Instagram, Messenger and RCS: everything you need to know

What is a website chat widget and how does it work on Com.Bot

Short answer: A website chat widget is the small chat box on your site that lets visitors ask questions without leaving the page. On Com.Bot, it connects to the same platform running your WhatsApp Business API, Instagram DMs, Facebook Messenger and Google RCS conversations, so every chat lands in one unified shared team inbox.

A website chat widget is the small chat box that appears on your site so visitors can ask questions without leaving the page. On Com.Bot, that widget is not a standalone tool. It connects to the same platform that runs your WhatsApp Business API, Instagram DMs, Facebook Messenger and Google RCS conversations. When someone types in the widget, the message appears in your unified shared team inbox alongside every other channel.

That means a visitor can start a chat on your pricing page, and your team can continue the same conversation on WhatsApp later if the customer prefers. The contact record, chat history and any files or order details stay attached. You are not running two systems or asking people to repeat themselves.

The widget also works with Com.Bot's automation builder. You can trigger a bot flow when a visitor opens the widget, asks about shipping or clicks a suggested reply. The bot can collect an email, share a catalog link or hand the chat to a human agent based on rules you set.

• Widget sits on your website and feeds into the same inbox as WhatsApp, Instagram, Messenger and RCS
• Visitors become contacts you can message on any connected channel
• Bot flows can answer first, then pass to a human agent
• Role-based access controls what each team member can see and do
• Works with the Com.Bot contacts CRM and automation builder

Who should use a website chat widget

Short answer: A website chat widget suits small and growing businesses, D2C brands, service businesses and agencies that want to answer questions before a visitor leaves. Ecommerce teams use it to recover carts and answer delivery questions, support teams use bots to deflect common questions, and because Com.Bot also covers WhatsApp, Instagram, Messenger and RCS, you can meet customers on the channel they already use.

Small and growing businesses use the widget when they want to answer questions before a visitor leaves. A D2C brand can catch a sizing question on a product page. A service business can collect project details from a contact form replacement. An agency can qualify leads before booking a call. The widget lowers the effort for the visitor and gives your team a real conversation instead of an abandoned form.

Ecommerce teams use it to recover carts and answer delivery questions. A skincare brand might get a question about ingredients, reply in the widget, then send a WhatsApp order update later. A coaching institute can answer course questions on the website and send appointment reminders on WhatsApp. The channel changes, but the conversation stays in Com.Bot.

Support teams use the widget as a first line of defense. Common questions about returns, hours or order status can be handled by a bot. Complex issues go to an agent with the full chat history. Because Com.Bot also supports WhatsApp, Instagram, Messenger and RCS, you are not limited to website visitors. You can meet customers on the channel they already use.

• D2C brands answering product and shipping questions
• Service businesses qualifying leads before a call
• Agencies managing multiple client conversations
• Support teams deflecting common questions with bots
• Any business that wants website chats and messaging channels in one place

How to set up the website chat widget in Com.Bot

Short answer: Setting up the website chat widget in Com.Bot starts in your account, where you create the widget, choose its appearance and pick connected channels. You then set a welcome message, office hours and routing rules, build bot flows with the visual drag-and-drop builder, add API calls or webhooks, and install the embed code so all chats appear in the shared inbox.

Setup starts in your Com.Bot account. You create the widget, choose its appearance and decide which channels it should connect to. If you already use WhatsApp Business API, Instagram or Messenger through Com.Bot, those channels can appear as options in the same widget. You can also keep the widget as a standalone chat that routes into the shared inbox.

Next, you set the rules. Choose a welcome message, office hours and which team members or bots handle incoming chats. The visual drag-and-drop bot builder lets you create a flow without code. For example, a first message can ask what the visitor needs, then branch to order status, pricing or a human agent. You can add external actions like an API call to check an order or a webhook to update your CRM.

Finally, you install the widget on your website. Com.Bot provides the embed code. Once live, every chat appears in the unified inbox. You can assign conversations, add internal notes and move a chat to WhatsApp if the customer agrees. The same contact record follows the conversation across channels, so your team is not starting over.

• Create the widget in Com.Bot and choose connected channels
• Set welcome message, hours and routing rules
• Build bot flows with the drag-and-drop builder
• Add API calls or webhooks for order lookups and CRM updates
• Install the embed code and manage all chats in the shared inbox

Website chat widget rules and compliance across channels

Short answer: The website chat widget itself is on your site, but once a conversation moves to WhatsApp, Instagram, Messenger or RCS, platform rules apply. WhatsApp business-initiated messages need Meta-approved templates and opt-in, customer replies open a 24-hour service window, template categories must be applied correctly, Instagram and Messenger use Meta's official APIs, and Google RCS requires agent verification.

The widget itself is your website, so you control the first interaction. But when a conversation moves to WhatsApp, Instagram, Messenger or RCS, platform rules apply. On WhatsApp Business API, business-initiated messages must use Meta-approved templates and go only to contacts who opted in. If a customer replies, a 24-hour customer service window opens where you can send free-form replies. Outside that window, you need a template.

Template categories matter. Marketing templates cover offers, abandoned cart reminders, back-in-stock alerts and re-engagement. Utility templates cover order confirmations, shipping updates, payment due for an existing order and appointment reminders. Authentication templates are for one-time passcodes only. Never send a cart reminder as a utility template. Meta reviews templates and can reject or pause them if they are miscategorized.

Instagram DM automation runs through Meta's official messaging API for professional accounts. Automated replies are triggered by user actions like comments, story replies, mentions or DMs, and the 24-hour window applies. Facebook Messenger works on Facebook Pages through the official Messenger API, with the same 24-hour window for promotional follow-ups. Google RCS Business Messaging requires agent verification before launch and supports rich messages with branded sender, images, carousels and suggested replies..

• WhatsApp business-initiated messages need approved templates and opt-in
• Customer replies open a 24-hour service window for free-form replies
• Marketing vs utility vs authentication categories must be applied correctly
• Instagram and Messenger use Meta's official APIs and the 24-hour window
• RCS requires agent verification and reaches customers on supported Android phones and carriers

Common mistakes with website chat widgets

Short answer: The most common website chat widget mistakes are running it as a separate tool from WhatsApp and other channels, hiding it on key pages, over-automating without a human handoff, sending promotional messages outside the 24-hour window on WhatsApp, Instagram or Messenger, and ignoring chat data. Com.Bot puts every channel in one inbox so context is never lost.

The most common mistake is treating the widget as a separate tool. If website chats live in one system and WhatsApp lives in another, your team misses context and customers repeat themselves. Com.Bot avoids that by putting every channel in one inbox. Another mistake is hiding the widget or making it hard to find. A chat widget should be visible on key pages like pricing, product and contact.

A second mistake is automating too much. Bots are useful for first replies and common questions, but a visitor with a complex issue needs a human. Set clear handoff rules. If a bot cannot answer after two tries, route to an agent. Also avoid sending promotional messages outside the 24-hour window on WhatsApp, Instagram or Messenger. That is a compliance issue, not just a preference.

A third mistake is ignoring the data. If you do not track how many chats start, how many convert and where visitors drop off, you cannot improve. Com.Bot's inbox and contact records give you the conversation history. Use it to see which questions come up most and which bot flows need work. Do not guess. Look at the actual chats.

• Do not run website chat and messaging channels in separate tools
• Do not hide the widget on important pages
• Do not over-automate without a human handoff
• Do not send promotional messages outside the 24-hour window
• Do not ignore chat data and bot performance

Measuring results and costs for your website chat widget

Short answer: Measuring a website chat widget means tracking chats started, contacts captured, response time, conversion rate, bot resolution rate and human handoff rate. Com.Bot plans are billed quarterly in USD: Silver $149, Gold $349 and Platinum V1 $2,500. WhatsApp message charges are billed separately from the plan, based on message category and the recipient's country, and there is no monthly conversation cap.

Start with the basics: number of chats started, number of contacts captured, response time and conversion rate. In Com.Bot, you can see conversations in the shared inbox and contacts in the CRM. If a bot handles the first reply, track how often it resolves the question without an agent. If a chat moves to WhatsApp, track whether the customer replies and whether the order completes. The goal is not more chats. It is more resolved questions and more sales.

Costs depend on your plan and how you use messaging. Com.Bot plans are billed quarterly in USD. Silver is $149 and includes 1 WhatsApp API channel, 1M contacts, 5 team members and 1 commerce store. Gold is $349 and is recommended for growing teams, with 10 team members, 2M bot triggers and 40 messages per second. Platinum V1 is $2,500 with 3 WhatsApp API channels, 5M contacts and 25 team members. Add-ons include extra team members, social channels or ecom stores at $10 per month each.

WhatsApp message charges are billed separately from the plan, based on message category and the recipient's country; customers can ask the team for current rates. There is no monthly conversation cap and no FUP limit. Payment methods for plans include cards, UPI, PayPal, crypto and bank transfer. If you need help, expert assistance is available at $49 per hour for WABA, CRM or inbox setup and $99 per hour for ecommerce, bots or automations. You can sign up at https://v3.com.bot/register or message +91 080 6987 1810 on WhatsApp.

• Track chats started, contacts captured, response time and conversion
• See bot resolution rate and human handoff rate
• Silver $149, Gold $349, Platinum V1 $2,500 billed quarterly
• WhatsApp message charges billed separately from the plan, based on message category and the recipient's country
• Expert help at $49 or $99 per hour depending on the task

Frequently asked questions