36 guides covering everything from first setup to advanced configuration.
A full helpdesk inside your WordPress admin: tickets, contacts, knowledge base, a customer chat and Claude powered triage. Here is the path every ticket takes from arrival to replβ¦
Read βUpload, activate, then enter the key from your purchase email. Until the key validates, the plugin shows only the activation screen.
Read βThe home screen says who is waiting, which replies are already drafted, what needs you first and how the last 14 days went. The setup wizard can be run again from Settings.
Read βFive short steps from install to a working desk, and a status board that shows what is already connected so you are never asked to set up something you already have.
Read βEvery AI feature runs on your own Anthropic key. Pick your models from Anthropic's live list, set how sure the AI must be as a percentage, and cap the month's spend, worked out peβ¦
Read βThree pages for your customers: a contact page that answers first, a My Tickets page opened by a private link, and a help centre. Let the desk create them, pick pages you already β¦
Read βCustomers ask in their own words and get answers from your help centre, sign in with one click for a chat that knows their account, and reach a person with one press.
Read βPut a sales chat on your sales pages, a members helper in your members area and extra sales chats for your other sites or brands, on any of your sites, set up in a five-step wizarβ¦
Read βA short message with a button, on the pages and for the people you pick, between two dates, shown once to each person.
Read βGive the Members Helper your training library as a members only source and it gives members real business help, with buttons to your lessons, courses and AI bots.
Read βEvery conversation kept, who it was, and the sales that followed it, tied to the chat by tracked link, email or visitor, with your own tests kept apart.
Read βA full-page Support Centre for your contact page and designed help article pages at /kb/, with your own header, footer and an ask box on every article.
Read βTurn your support mailbox into the inbox. The plugin polls IMAP every five minutes, threads replies by ticket reference and skips anything it has already seen.
Read βSend through your own mail service, put your logo and colour on every email, add your own closing message, and choose which alerts reach you and how often.
Read βConnect your support mailbox, Gmail and Google Workspace included, and one click on any ticket lists the customer's earlier emails to read right there. Strictly read-only.
Read βThe Inbox opens on what is still to do, with status counts, search, a date picker and AI badges, so you can see at a glance what the AI already handled and what still needs you.
Read βThe ticket screen puts the whole conversation, the customer's purchase history and the AI verdict on one page, with a full editor for your reply and files you can attach.
Read βTriage is one cheap model call that labels the ticket with a category, sentiment, priority, product and confidence. Everything downstream keys off those labels.
Read βThe resolver only acts on categories it can evidence: license lookups from your sales and license data, and how-to answers from your knowledge base. Everything else goes to a humaβ¦
Read βFor everything the resolver will not answer, the drafter writes a reply for a human to approve. It reads the whole thread, your knowledge base and that customer's history.
Read βArticles are ordinary WordPress content with their own index. The better the articles, the more the AI can answer, because the resolver is only allowed to use what they say.
Read βAdd what you know in four ways: upload files (Word included), link a web address that refreshes itself, paste text, or tick pages already on your site. One index then answers visiβ¦
Read βFor owners with many products or a big help centre: one JSON file covers them all. What the file looks like, the field names the desk understands, and a prompt that makes your AI β¦
Read βSave the replies you send every week. Twelve starters come built in, the AI writes one from a sentence or improves yours, and on a ticket the picker fills in the name, product andβ¦
Read βTell the desk what you sell, what it costs and where to read about it, so support answers questions about your products and never invents a price.
Read βThree notification receivers record every sale into your own sales table, so the ticket screen and the AI both know what a customer bought before you reply.
Read βPoint the desk at your own plugin license servers and it queries them live when a customer says their key does not work, pulling their real keys into the reply.
Read βHow the desk auto-detects the other ResultsAiX plugins on your site, connects Commerce and the License Server, and builds one customer profile that the ticket sidebar and the AI bβ¦
Read βYour sales tracking or email list live on a different WordPress site from your desk? Connect that site with a key and its data joins every customer profile, ticket and AI reply.
Read βCreate a read key and your membership site, mailer or dashboard can ask the desk how many tickets a customer has and how many are open. Message text is never sent.
Read βEvery ticket is attached to a contact record keyed on the email address, which is what lets the desk show purchases and past tickets beside a new question.
Read βBring your whole history across from Freshdesk, Zendesk, Help Scout, LiveAgent, or a CSV export from anything else. Original dates kept, nobody emailed, safe to stop and carry on,β¦
Read βHow your desk is doing in the dates you pick: six numbers, every ticket on the desk right now, and where the load comes from, all counted from your own tickets and your own AI log.
Read βSafety nets so nothing sits unnoticed: a Slack ping and an email when a ticket comes in upset, an hourly check for tickets past your targets, and a quiet ticket solved by itself.
Read βEvery setting on the five Settings tabs, what it controls and what it defaults to, so you can set the desk up once and know why each value is what it is.
Read βThe questions that come up most: no AI output, email not arriving, notifications rejected, and what to do when knowledge base search returns the wrong article.
Read βEvery plugin documented here works alongside the others, managed from one ResultsAiX Hub.