Live chat on your own website

Install it

Open Integrations → Website Chat in your dashboard and create a widget. You will get a snippet that looks like this:

<script>
  (function(w,d,s,k){w.SixrshWidget=w.SixrshWidget||{};w.SixrshWidget.key=k;
  var f=d.getElementsByTagName(s)[0],j=d.createElement(s);j.async=1;
  j.src='https://www.6rsh.com/webchat/v1/6rsh.js?v=1.8.5';f.parentNode.insertBefore(j,f);})
  (window,document,'script','YOUR_WIDGET_KEY');
</script>

Paste it just before the closing </body> tag. Settings are read live, so changing the colour or greeting in the dashboard applies immediately — you never re-embed.

WordPress and WooCommerce

Do not paste anything. Install the 6rsh plugin (v1.8.0 or later), open 6rsh → Website Chat, tick Show Web Chat on my store and paste only your widget key. The plugin adds the script for you and can also recognise signed-in customers and share cart and product context.

Shopify

Online Store → Themes → Edit code → theme.liquid, and paste the snippet before </body>.

Wix

Settings → Custom Code → Add Custom Code, paste the snippet, apply it to All pages and load it in the Body — end position.

Any other site

If you can add a script tag before </body>, it works. There are no dependencies and no build step.

Allowed domains — read this one

The widget only runs on domains you list. This is what stops someone copying your key out of your page source and running your chat, and your AI quota, on their own site.

• shop.example — that exact domain, on http or https, any port.
• *.shop.example — any subdomain. It does not match a lookalike such as evilshop.example.

An empty list allows nothing. That is deliberate: a public endpoint that defaults to "any origin" is how someone else's traffic ends up on your bill.

Language

The widget reads the lang attribute on your page. An Arabic page gets the Arabic widget with a fully mirrored layout — the panel and launcher move to the other side, text aligns right and the icons flip. It is not a translation layer over an English layout. If your page declares no language, the widget uses the default you set.

Business hours

Business hours change wording only. Outside them the header says you are away rather than implying someone is watching. Your AI agent still answers, and a visitor can always send a message. Leave hours unset and the widget never says you are closed.

Proactive messages

You can invite a visitor to chat based on the page they are on, how long they have been idle, scroll depth, exit intent, cart value, or whether they are returning. Three limits are enforced and cannot be raised:

• at most one message per visitor per 30 minutes;
• at most three per session;
• never after the visitor has said anything.

A widget that nags costs you more than no widget at all, so when a rule is ambiguous it stays quiet.

Continuing on WhatsApp

When you have a WhatsApp number connected you can offer Continue on WhatsApp. The visitor's WhatsApp opens with a short reference code prefilled; when that message arrives we attach it to the same contact, so the conversation carries on with its history instead of starting again. If you have no number connected the offer is hidden entirely — we do not advertise a channel you cannot answer on.

Troubleshooting

The widget does not appear

1. Open your browser console and look for a request to /api/webchat/…/config.
2. 403 origin_not_allowed — the domain is not in your allowed list. Add it exactly as it appears in the address bar.
3. 404 — the widget key is wrong, or the widget is switched off.
4. No request at all — the snippet is not on the page. Check it is before </body> and that a caching plugin has not stripped it.

Content Security Policy

If your site sets a CSP you must allow our script and its calls:

script-src  https://www.6rsh.com;
connect-src https://www.6rsh.com;

The widget loads no external fonts or images, so nothing else needs allowing.

It shows on checkout and I do not want that

The WooCommerce plugin already hides it on checkout. On a custom site, load the snippet conditionally on the pages you want.

Public API

All widget endpoints are under /api/webchat/{public_key}. Your public key identifies a widget and authorises nothing else — it cannot read contacts, list conversations, or reach anything belonging to another visitor.

• GET /config — widget appearance and state.
• POST /session — start or resume a visitor; returns the visitor token and recent messages.
• POST /message — send a message.
• GET /messages?after= — poll for new messages.
• POST /event — behavioural signal (page view, idle, exit intent, cart).
• POST /identify — supply a name, email or phone.

Rate limits are 20 messages per minute and 200 per hour per visitor, and 2,000 per hour per widget. Exceeding one returns 429 with a Retry-After header.

Driving the widget from your page

SixrshWidget.open();
SixrshWidget.identify({ name: 'Sara', email: 'sara@example.com' });
SixrshWidget.track('cart_update', { count: 2, value: 420, currency: 'AED' });

Calls made before the widget finishes loading are queued, so you do not need to wait for it.

A note on identity

Anything sent from a browser is treated as an unverified claim: it is recorded against that visitor and never used to attach them to an existing customer record. Attaching to an existing contact requires a signature produced by your own server, which is what the WooCommerce plugin does for signed-in customers. Without that rule, anyone could type a customer's email into a widget and inherit their conversation history.

Looking for the WhatsApp button?

The older click-to-chat button — a floating link that opens WhatsApp, with no AI reply and no transcript — is still supported and documented at Chat Widget. Web Chat does everything it does and more, so we recommend it for new sites. If you enable both, they will overlap in the same corner.