Feed it your handbook, your price list, your policies. It answers visitors from those pages only — quoting where it found the answer, and saying plainly when there isn't one.
Midnight, holidays, the middle of a rush. The questions get answered whether or not anyone is at the desk.
The five questions you're asked every day get handled by rules and cache — instantly, and for nothing.
Every reply is pulled from a document you uploaded, and the widget names which one. Nothing borrowed off the web.
One script tag, or the WordPress plugin generated for your bot. No developer, no deploy, no build step.
The passage is found before the sentence is written. Visitors see the answer and the file it came from, so your team can audit any reply in one click — and correct it by editing a document, not a prompt.
Pick a theme and the whole thing changes — layout, corners, colour, the full-screen panel. Preview any look live before you commit, including the ones your plan hasn't unlocked yet. It renders in a Shadow DOM, so your CSS and ours never collide.
Write a rule in plain language and the widget answers before the model ever wakes up. Opening hours, delivery zones, refunds, “get me a human” — matched, answered in milliseconds, and billed at nothing.
Every conversation is logged, rated and searchable. You get a satisfaction score, the replies people marked unhelpful, and — the one owners actually act on — a running list of questions your documents don't answer yet.
That list is a content backlog written by your own customers. Close a gap by editing a document, not a prompt, and the next visitor gets the right answer.
Four steps, no build pipeline, nothing to install on a server. If you can upload a file and paste a line of HTML, you can finish this before the kettle does.
Give it a name and a personality. It exists in seconds — yours to test privately for free.
Upload PDFs, paste text, point it at a page. Everything is chunked and indexed automatically.
Theme, colours, avatar, greeting, quick questions — all with a live preview beside you.
Copy one script tag, or download the WordPress plugin generated for that bot. Done.
Every bot ships as its own installable plugin. Upload, activate, and keep managing it from here.
Font scaling, high contrast, dyslexia-friendly type, text-to-speech and full keyboard control.
The widget asks for contact details mid-conversation. Pull them as CSV or over REST.
Visitors can pop the bubble out into a proper panel — sidebar, quick questions, your business card.
Layered rate limits throttle bot traffic before it reaches the model. Blocked requests cost nothing.
Frequently asked questions come back from cache in milliseconds, so the common path feels instant.
One credit is one reply to a real visitor. A 1,000-credit pack answers a thousand customer messages. Testing your own bot never costs a credit, and there is no subscription to cancel.
Credit packs, bought when you need them. Start on the free grant, top up later, stop whenever — nothing renews behind your back.
No. You create the bot, add your content, and paste one script tag where you'd paste an analytics snippet. On WordPress you don't even do that — download the plugin generated for your bot, upload it in WP Admin, activate.
Only from the documents you upload. The most relevant passages are retrieved first, and the model is constrained to answer from those passages and name the source. When your content doesn't cover the question, the bot says so rather than filling the gap with something plausible.
It can't. The widget renders inside a Shadow DOM, so styles don't leak in either direction. We test it against deliberately aggressive themes — the kind with global resets and !important everywhere.
You buy message credits. One credit is one reply to a visitor. There's no subscription and no monthly minimum — when a pack runs low you top up, and if you stop, nothing keeps charging. Testing your own bot from the dashboard is free.
The platform is self-hosted with strict per-company isolation. Widgets are locked to the domains you name, requests are rate-limited in layers, and team access is controlled by roles you set. Your documents are never used to train anything.
Layered rate limits throttle bot-like traffic before it reaches the model, so blocked requests never spend a credit — and you're alerted when it happens. Domain validation stops your widget being lifted onto somebody else's site.
WONS Chatbot
