A chat bubble that already read your docs
Add one line of code to any website and visitors get answers pulled from the help articles you've already written.
No AI account to set up · No API key to manage · Works on non-WordPress sites
Luna
Usually replies instantly
SOURCE
📖 Account Settings
Answers from your docs
It reads the help articles you published, so answers match what your product actually does.
Branded to your product
Name, avatar, color, panel size and wording — the widget looks like yours, not ours.
Page targeting
Show it on the pages where questions happen, hide it on checkout, or anywhere else you choose.
Business-hours aware
Set your hours and it greets visitors differently outside them, in their own local time.
Keeps the thread
A visitor can navigate away and come back without starting the conversation over.
Hands over to humans
When it cannot help, it offers your support email and a link into your ticket queue.
Installation
One tag. Any site.
The widget is plain JavaScript with no dependencies, so it works on WordPress, on a static site, or on the marketing page your agency built in something else entirely.
<script src="https://cdn.nirosuite.com/nirohelp/chat.min.js" data-site-key="YOUR_SITE_KEY" data-agent-name="Luna" data-primary-color="#2271b1" data-position="bottom-right" data-show-on="/docs/*, /help/*" data-business-hours="mon-fri:9-17" defer></script>Only the site key is required. Everything else has a sensible default.
Control
You decide where, when and how it appears
A chat widget on every page all day is the fastest way to annoy people. These are the knobs that stop that.
Show and hide rules
List the paths it should appear on, and the ones it never should. Hide rules always win.
Auto-open, if you want
Open after a delay, at a scroll depth, on exit intent — or never. It only fires once per session.
Business hours
Per-day hours in the visitor’s local time. Outside them, show an offline message or hide it entirely.
Suggested questions
Seed the panel with the three questions you get most, so visitors know what to ask.
Panel size
Set the width and height you want; it caps itself sensibly on small screens.
Branding toggle
Keep the small "Powered by NiroHelp" footer, or switch it off on a paid plan.
Setup
Preview it before your visitors ever see it
The configure screen in your dashboard builds the widget as you type. Try wording, colors and positions live, then take the finished snippet away.
Register your site
Enter your name and email on the AI screen and paste in the key we send back.
Sync your articles
One click pushes your published help articles into the AI index.
Style and preview
Set the name, avatar and colors, then hit Preview to see the real widget in place.
Copy the snippet
Take the generated tag — or download the packaged plugin — and add it wherever you need it.
Every setting
All optional except the site key.
| Setting | Default | What it does |
|---|---|---|
| Site key | required | Issued when you register the site. The only setting you must provide. |
| Agent name | Support | The name shown in the chat header and the welcome message. |
| Avatar | generic icon | A square image URL for the assistant. |
| Primary color | #2271b1 | Launcher, header, visitor bubbles and focus rings. |
| Position | bottom-right | Bottom-right or bottom-left of the viewport. |
| Welcome message | auto | The first thing the assistant says when the panel opens. |
| Suggested prompts | none | Starter question chips, hidden after the first visitor message. |
| Auto-open | none | Delay, scroll depth, exit intent, or off. Once per session. |
| Show / hide paths | everywhere | Path patterns with wildcards. Hide rules take priority. |
| Business hours | none | Per-day ranges in the visitor’s local time. |
| Offline behaviour | message | Show an offline greeting, or hide the launcher outside hours. |
| Panel size | 400 × 620 | Width and height in pixels, capped to the viewport on phones. |
Site key
required
Issued when you register the site. The only setting you must provide.
Agent name
Support
The name shown in the chat header and the welcome message.
Avatar
generic icon
A square image URL for the assistant.
Primary color
#2271b1
Launcher, header, visitor bubbles and focus rings.
Position
bottom-right
Bottom-right or bottom-left of the viewport.
Welcome message
auto
The first thing the assistant says when the panel opens.
Suggested prompts
none
Starter question chips, hidden after the first visitor message.
Auto-open
none
Delay, scroll depth, exit intent, or off. Once per session.
Show / hide paths
everywhere
Path patterns with wildcards. Hide rules take priority.
Business hours
none
Per-day ranges in the visitor’s local time.
Offline behaviour
message
Show an offline greeting, or hide the launcher outside hours.
Panel size
400 × 620
Width and height in pixels, capped to the viewport on phones.
Privacy, plainly
What the chatbot does and does not do with your visitors' data.
Conversations are not tied to an identity
Chats are not logged with an IP address or a cross-session identifier — there is no visitor profile being assembled.
The thread lives in the visitor’s browser
Their conversation is kept in their own browser session, which is why it survives a page change but not a new visit.
Requests are authenticated by your site key
The widget talks to the AI service using your site key. There are no third-party model credentials anywhere in your WordPress install.
Turning it off changes nothing else
The chatbot is opt-in. With it off, your docs, tickets and emails run without contacting any outside service at all.
Common questions
No. Pro includes the AI service — you register your site once from the dashboard and paste in the key we email you. There is no model subscription to buy and no API key field to fill in.
It answers from your synced help articles rather than from general knowledge, and when it cannot find a relevant answer it says so and offers your support email or ticket form instead of guessing.
Yes. The widget is a single vanilla-JavaScript tag with no dependencies, so it runs on any site that can include a script — static sites, other CMSes, or a landing page built anywhere.
The script is deferred and renders itself only after the page is interactive, so it does not block your content from loading or painting.
Yes. When the visitor asks for a person, the widget offers your configured support email and ticket link — and on WordPress that link goes straight into your NiroHelp queue.
Run a Sync from the AI screen and the new article joins the index. From that point the chatbot can answer from it.
Put it on your docs page first
That's where visitors already have a question — and where your articles can answer it.