A knowledge base, an FAQ and a support desk — so people find the answer, and reach you when they cannot.
The complete list — what each part does and what it is there for.
Articles in topics, ordered the way you arranged them rather than by date, with a table of contents built from the article's own headings and related reading at the end.
WordPress search demands every word appear, so "how do I get a refund on my order" finds nothing. Ours matches on the words that matter and ranks a title above a passing mention in paragraph nine.
Readers answer in one click, and the dashboard lists the articles they said no to. It is the fastest way to find the page that is quietly failing everyone who reads it.
Questions grouped and shown as an accordion that opens without JavaScript, with FAQPage markup so a question can win its own result in search.
Every request gets a reference, a status and a thread. Work a queue that defaults to what still needs a reply, rather than scrolling a mailbox.
Customers write with an email address and get a private link back to their own conversation. Signed-in customers see all of theirs in one list.
Matching articles appear under the subject line while someone types their question. Many people find what they needed and never send it.
Leave a note on a request for whoever picks it up next. Never emailed, never shown to the customer.
Give a request to a colleague, set its priority, and see the median time it takes your team to reply first.
Everything inherits your theme's typography and reads from colour variables you can override in one line. No jQuery, no fonts fetched from anywhere, and dark mode if the visitor's browser asks for it.
Every screen in the plugin arrives without a page load, and every save happens where you are standing. WordPress fetches the whole of wp-admin's CSS and JavaScript again to change one panel; this fetches the panel. The screen you are on is still there while the next one is on its way, and the one you are heading for is usually already in hand — a pointer takes a moment to reach a menu item, and that moment is spent fetching.
A save answers in the corner of the screen, bordered in the colour of what it is telling you and saying what was saved rather than just "Saved". Four seconds, and hovering holds it open. No reload, and no scrolling back to find a notice above the header three hundred pixels from the button you just pressed.
A WordPress admin request spends about a second in its own bootstrap before a plugin gets a word in, and fetching when your pointer arrives only buys back a fraction of it. So the plugin's other screens are fetched quietly while you read the first one — one at a time, only while the browser is idle, and never on a metered connection. By the time you click a tab the answer has been in memory for seconds.