Features
Six modules. One admin menu.
A knowledge base, a ticket system, email piping, a 360° dashboard with a copilot, an AI chatbot, and an AI auto-responder — built to work together, and switchable on or off one at a time.
Knowledge base
A searchable help center on your own site, organized the way your customers think about your product.
Support tickets
Every conversation tracked from open to resolved, and handed to whoever is actually free to take it.
Dashboard & copilot
A 360° view of your support — what is at risk, who is unhappy, how fast you reply — plus a copilot you can just ask.
AI chatbot
A chat bubble that answers visitors instantly, using only what you have actually written in your docs.
AI auto-responder
The same AI reads incoming tickets and replies on its own — but only when it is genuinely confident.
Email piping
Connect your support mailbox and every email becomes a tracked ticket — replies thread straight back into the same conversation.
Already running another help desk?
NiroHelp imports articles, topics, tickets and replies from seven other plugins. Your old plugin keeps its data until you choose to clean it up, and the import is safe to run twice.
Everything in the box
The full list, grouped by what you'd be looking for.
Customer-facing
What your customers see
- Searchable help center
- Topics, search, and readable article pages.
- Article feedback
- A helpful / not helpful vote on every article.
- Submit-a-ticket form
- With your own custom fields and required rules.
- My tickets page
- Customers track and reply to their own tickets.
- Three ways to log in
- One-time code, magic link, or a password.
- Live chat bubble
- Answers from your docs, on any site.
Team-facing
What your team gets
- One admin menu
- Docs, tickets, agents and settings in one place.
- Agents screen
- Open and total counts, plus a capacity badge each.
- Automatic assignment
- Random, round-robin, or least-loaded.
- Status automation
- Replies move the ticket to the right stage.
- Roles and permissions
- Manager, Agent, and Customer, mapped properly.
- Notification emails
- Seven templates you can edit and brand.
Under the hood
What keeps it safe
- Works with AI off
- Docs, tickets and email need no outside service.
- No model keys to manage
- No OpenAI account, no API key field.
- Your data stays yours
- Ordinary posts and comments, no custom tables.
- Clean uninstall
- Removing the plugin leaves your content intact.
- Translation-ready
- Every string is translatable.
- Caching built in
- Article lists cached and auto-refreshed on save.
Yours to configure
Run only the parts you need
Docs and tickets are separate modules with their own switches, and almost everything customer-facing is yours to shape.
Modules on or off
Docs and tickets are independent. Run a knowledge base with no ticketing, a ticket desk with no docs, or both — and switch either one off later without losing anything.
- Docs module
- Switch it off and the articles stay in your database, just hidden from the menu.
- Tickets module
- Same again — disabling it never deletes a ticket or a reply. At least one of the two stays active.
- AI, separately
- The chatbot and auto-responder are their own switch on top of the two.
- One settings screen
- Every toggle lives in the same place, not scattered across submenus.
Docs, your way
The knowledge base is built to slot into a site that already has its own URL conventions and its own performance setup.
- Nine permalink structures
- Plain, topic-based, product-based or nested — pick the one your old URLs matched.
- Article ratings
- Helpful / not helpful votes stored as counts, with no visitor tracking.
- Doc list caching
- Redis, Memcached or transients with a configurable TTL, cleared automatically on save.
- Display toggles
- Sidebar, breadcrumbs, prev/next, comments and per-page counts, each independent.
Tickets, your way
Decide what you ask customers for, who can submit, and how work gets divided across the team.
- Customizable form
- Show, hide, reorder and require fields, or add your own text, number, email, long-answer and dropdown fields.
- Guest submission
- Let customers file a ticket with no account at all, then claim it later with a code.
- Assignment logic
- Round-robin, least-loaded or random, with a per-agent open-ticket cap — or turn it off and triage by hand.
- Status automation
- Replies move tickets between stages on their own; switch it off if you prefer manual control.
Emails that look like yours
Seven notification emails cover the whole lifecycle, and every one of them is editable — subject, body and branding.
- Full template control
- Rewrite the header, subject and body of each of the seven emails.
- Your logo and footer
- Set branding once and it applies across every notification that goes out.
- Login emails included
- Verification codes and magic links are templates too, not hardcoded messages.
- Lifecycle coverage
- New ticket to customer and agent, agent reply, customer reply, and resolved.
For developers
Everything is a WordPress object
Articles are posts, tickets are posts, replies are comments. There are no custom database tables to reverse-engineer, and every screen is backed by a documented REST route.
# List help articlesGET /wp-json/nirohelp/v1/docs/# Create a ticketPOST /wp-json/nirohelp/v1/tickets/# Add a reply (auto-updates status)POST /wp-json/nirohelp/v1/tickets/{id}/comments# Push docs to the AI indexPOST /wp-json/nirohelp/v1/ai/sync/