Website
A website chatbot that hands over instead of stalling
One script on your site. An AI agent that answers from your own documents, a real person one tap away, and every conversation landing in the same inbox as your Instagram DMs.
Start free for 7 daysMost website chat tools are priced per conversation, which quietly makes success expensive: the better your marketing works, the more you pay to answer the people it brought. That model comes from the support-desk world, where a conversation is a cost. On a site that is trying to sell something, a conversation is the point.
Here the web chat is part of the same plan as everything else and nothing counts it. What is metered is not conversations, contacts or replies — it is the accounts you connect.
The other difference is where the conversation goes. A dedicated chat widget puts website questions in one tool and your Instagram DMs in another, so the same customer arrives twice and nobody has the whole picture. This one lands in the same inbox as your social messages, comments and reviews.
Where the bubble goes, and where it does not
A chat widget is only welcome when it stays out of the way. These are settings, not support tickets — and the reason they exist is that every one of them came up on a real site.
Either corner, at any distance
Left or right, and up to 200 pixels in from that side and up from the bottom — enough to clear a sticky cookie bar, a fixed sidebar or another floating button without shoving the chat into the other corner.
Off on the pages that matter
Hide it by path, with wildcards. Keeping it off your checkout is the usual one: a chat bubble over a payment button costs more than it earns.
Off on phones, if you want
Do not load it at all under 640 pixels wide. Not hidden with CSS — not loaded, so it costs a mobile visitor nothing.
Your own button instead of ours
Hide the bubble entirely and open the chat from a link or a button you already have, by calling Ignix.open() from your own page.
Foldable, not closable
Visitors can fold it into a tab at the edge. It does not close: it comes back on the next page, and reopens on its own if someone answers them.
It answers from your business, not from a script
The agent reads what you give it — your website, your documents, the answers your team has already written — and replies from that. There is no decision tree to draw first and no list of questions to anticipate, which is the part that usually turns a chatbot project into a month of work that nobody finishes.
It is also the same agent that answers your Instagram DMs, your Facebook comments and your WhatsApp. You teach it once. A customer who asks the same question on your site and in a DM gets the same answer, which sounds obvious and is exactly what two separate tools cannot do.
The handover is the feature
The moment that decides whether a website chatbot helped or annoyed is not a good answer — it is the bad one. Someone asks something specific, the bot guesses, and the visitor leaves knowing your company is a machine that does not listen.
So the handover is built in rather than added later. A conversation can be flagged for a human, and while it is flagged the AI says nothing on that thread. The inbox has a filter for exactly those, so the ones waiting on a person are a list rather than something to go looking for.
And when an operator answers by hand, the AI stops on that conversation on its own — no one has to mute it first. When the thread is marked handled, it picks back up.
What a customer care chatbot is genuinely good at
Opening hours, prices, what is included, where an order is, whether you ship somewhere, what the difference between two plans is. These are most of the volume on almost every site, they have exact answers, and a person retyping them all day is a waste of a person.
What it is not good at is the conversation where somebody is upset, or the one where the answer costs money to get wrong. Those are the ones worth routing to a human quickly, and the reason to measure a chatbot by how cleanly it escalates rather than by how much it deflects.
Which is also why this is not sold as a way to reduce headcount. It answers the repetitive half so the person you already have gets to the half that matters while the visitor is still on the page.
One script, and a guide for the usual places
Installation is a single snippet before the closing body tag. There are step-by-step instructions for Shopify and WooCommerce, because those are where most people are and because both hide the right file in a slightly different place.
If your site is something else, the generic instructions are the same one line. And if you would rather not touch the theme at all, a tag manager works fine.
Questions people ask
Is there a per-conversation charge?
No. Conversations, contacts and messages are not counted here — from the Blaze plan they are unlimited, and the Spark plan includes 1,000 automated replies a month. What the price follows is how many social accounts you connect. A busy month costs the same as a quiet one.
What does a web chatbot need from me before it is useful?
Your website and whatever you have already written — a price list, an FAQ, a policy document, past answers. It reads those. You do not draw a flowchart first, which is the step that kills most chatbot projects before they launch.
Can I keep it off my checkout page?
Yes, by path, with wildcards — so “/checkout*” covers every step of it. You can also keep it off phones entirely, in which case it is not loaded rather than hidden, so it costs a mobile visitor nothing.
Do the website conversations mix with my Instagram DMs?
They land in the same inbox, which is the point, but each conversation shows which channel it came from. Someone who asked on your site and then messaged you on Instagram is two conversations from one person, not two strangers in two different tools.
How do I know when a real person is needed?
The conversation gets flagged and the AI goes quiet on it, and the inbox has a filter that shows only those. You are looking at a short list of people waiting, not scanning everything for the one that went wrong.
Are help bots actually good enough now?
For the repetitive half, yes — opening hours, prices, where an order is, what a plan includes. For the half that decides whether someone buys, the useful measure is not how good the bot is but how fast it gets out of the way. That is why the handover is built in here rather than bolted on.
Is this an AI chatbot service or software I run myself?
Software. There is no agency engagement, no scoping call and no implementation fee — you connect it, point it at your material and it answers. If you want somebody to set it up for you, that is a normal thing to want, but it is not what this is.
Put it on your site, keep everything in one inbox
The web chat comes with the same plan as the scheduling, the automations and the social inbox. One script, one agent to teach, and no counter running while people talk to you.
Start free for 7 daysPlans start at $19 a month. Cancel in two clicks.