20 guides covering everything from first setup to advanced configuration.
A full helpdesk inside your WordPress admin: tickets, contacts, knowledge base and Claude powered triage. Here is the path every ticket takes from arrival to reply.
Read →Upload, activate, then enter the key from your purchase email. Until the key validates, the plugin shows only the activation screen.
Read →Every AI feature runs on your own Anthropic key, stored on your site. Set three models, a confidence threshold and a monthly spend cap in Settings, AI.
Read →Three shortcodes give customers a contact form, a place to look up their own tickets and a public knowledge base. Point the plugin at those pages in Settings, General.
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 →The Inbox lists every ticket with status counts, search 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 reply box that can draft for you.
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 →Macros are reusable reply templates with placeholders. Create them on the Macros screen and insert them into any reply from the picker on the ticket page.
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 →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 →Pull your existing contacts, tickets with their conversations, and solution articles straight out of Freshdesk over its API, in pages you control.
Read →Eight tiles plus two breakdowns, all counted from your own tickets and your own AI call log. Nothing here is an estimate except the spend figure.
Read →Two independent safety nets: a Slack ping the moment a ticket is classified as upset, and an hourly check that emails you about tickets breaching your SLA.
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.