The Salesive chat widget is included automatically in every Salesive storefront, with no install step. It runs in a Shadow DOM so your theme styles cannot break it, and it exposes a global SalesiveWidget API for the parts you want to control. Under the surface it is several widgets in one: live support chat, push notifications, PWA installation, pending reviews, a WhatsApp launcher option and voice calls.

What is on the storefront by default?

Every Salesive storefront ships with the widget already attached. You do not add a script tag, and you do not need a third-party chat subscription to get a support channel. That is the first thing to understand: the default is presence, not absence.

The widget bundles several pieces. Live support chat is the one shoppers notice. Push notifications let you reach a shopper who has opted in. PWA installation gives the storefront an install prompt on a phone. Pending reviews surface a review request without a separate tool.

Because it is included, the question is not whether to have a chat widget. The question is how to configure the one you already have so it helps instead of hovering over every page.

How does shopper sign-in work?

A shopper can sign in with Google or with an email OTP. The OTP path matters in Nigeria, where not every shopper wants to hand over a Google account to ask about an order. Both paths create a session the widget can use.

History is preserved across navigation. A shopper who moves from a product page to the cart and then to checkout does not lose the conversation. The session survives the page changes, and cross-subdomain cookie auth keeps the same shopper recognised when your store uses more than one subdomain.

That continuity is the quiet feature. Most chat tools treat every page load as a new visitor. A widget that remembers the conversation is the difference between support and a repeated introduction.

How do you control where it appears?

Visibility can be set by route. You can show the widget on product and order pages and hide it on checkout, or keep it off a landing page where it would compete with the main call to action. Route-based visibility is the control that stops the widget from becoming wallpaper.

Dark mode is supported, so the widget can match a dark storefront instead of glowing white in the corner. If your theme switches modes, test the widget in both. A chat bubble that disappears against the background is worse than no bubble.

Start with fewer pages, not more. Turn it on where a shopper is likely to have a question, then widen the scope once you know the team can answer what arrives.

What else can the widget do?

There is a WhatsApp launcher option for stores that prefer to move the conversation to WhatsApp. There are voice calls, with a voice-call API for stores that want to wire calling into their own flow. These are options, not defaults, so you can leave them off if your team cannot cover them.

Push notifications and PWA installation work together. A shopper who installs the storefront to their home screen and opts into push is easier to bring back than a shopper who has to find the site again. The widget is where both prompts live.

Pending reviews are the fourth piece. The widget can surface a review request to a shopper who has bought, which keeps the ask close to the purchase instead of sending it from a separate system later.

Enabling every option at once is a common mistake. A storefront with chat, a WhatsApp launcher, voice calling and a push prompt is asking the shopper to make four decisions before they have looked at a product. Turn on the channel you can staff, and add the next one when the first is working.

How do you customise it?

The global SalesiveWidget API is the supported surface. You can use it to control the widget from your theme without reaching into its internals. The Shadow DOM is the reason that works: your CSS stays outside, and the widget's CSS stays inside.

That separation is a feature for theme builders. You can restyle your storefront aggressively and still trust the widget to render correctly. It also means you cannot fix a widget style by adding a global CSS rule. Use the API and the supported options.

If you are building a custom theme, read the theme documentation before you touch the widget. The API is small on purpose, and the supported path is shorter than reverse-engineering the Shadow DOM.

A chat widget is not a support strategy. It is a door. Someone still has to be on the other side.

What does the widget not do?

It does not appear on a site that is not a Salesive storefront unless you add the embed script. The automatic inclusion is a Salesive platform feature, not a general-purpose script you can drop on any website.

It does not answer questions by itself. Ola can handle conversations elsewhere in the platform, but the widget is a channel, and a channel without cover is a missed message with a nicer interface.

It also does not replace your order pages. A shopper should be able to track an order without opening chat. The widget is for the questions the page cannot answer.

The widget is not a substitute for clear delivery and return information either. Most support questions are answered by a good product page. Every question the page answers is a conversation the widget does not have to carry.

Frequently asked questions

Do I need to install the chat widget?

No. It is included automatically in every Salesive storefront.

Can I hide the widget on some pages?

Yes. Visibility can be set by route, so you can show it on product and order pages and hide it elsewhere.

How do shoppers sign in to chat?

With Google or an email OTP. Sessions and history are preserved across navigation and across subdomains.

Does the widget support voice calls?

Yes, there is a voice-call option and a voice-call API. It is an option you can leave off.

Can I use the widget on a non-Salesive site?

Not automatically. Outside a Salesive storefront you need the embed script.

The widget is already on your storefront, so the useful work is configuration: choose the routes, match the mode, decide whether WhatsApp or voice belongs in the flow, and make sure someone answers. The features page covers the storefront tools, integrations covers what connects to them, and pricing shows what each plan includes. For the automation behind the conversation, read how Ola replies to WhatsApp, Instagram and Telegram DMs, and for a theme that hosts the widget, see building a custom Salesive theme.