Written once
Articles get written for launch and never touched again.
The Flaxxa Desk knowledge base is where you publish help articles for customers, organised in categories, with a "was this helpful?" vote on each. The same articles, plus your SOPs and uploaded documents, give the AI Copilot the context it drafts replies from.
S SOP · Refund Policy v3
How refunds are processed end-to-end
Updated 3d ago · Published
1. Customer requests refund via WhatsApp, email, or portal.
2. Eligibility checked against order date + product type.
3. Refunds ≤ ₹5,000 auto-process; larger ones escalate to billing.
4. Customer notified on the original channel.
Used in drafts
412
last 7d
Helpful
94%
last 30d
Suggested replies
298
tickets / 7d
01 / 04
Articles get written for launch and never touched again.
Without feedback, nobody knows which articles help and which confuse.
If only customers read it, the team has little reason to keep it current.
02 / 04
Create categories with an icon and an order, then add articles to them.
Each article has a title, excerpt and body, and goes live when you publish it.
Published articles appear beside the customer portal; readers can say whether each one helped.
Articles are indexed so AI drafts can use them, alongside SOPs and uploaded knowledge sources.
03 / 04
One library, two jobs.
Ordered categories with icons and descriptions.
Title, excerpt and body, saved as draft or published.
"Was this helpful?" on every published article.
The public knowledge base sits beside your customer portal.
Internal procedures with trigger keywords for the AI Copilot.
Upload PDF, Word, Markdown or text files for the Copilot to draw on.
Bring articles and categories over from Zendesk or Freshdesk.
Create and update categories and articles over the REST API.
04 / 04
Every article earns its keep.
Customers who find the article don't need to write in.
A clear article improves every draft that draws on it.
Helpful votes show which articles need a rewrite.
Keep exploring
An AI copilot for support agents: reply drafts from your SOPs and knowledge base, in your tone, and thread summaries. An agent checks and sends each reply.
A support portal with magic-link sign-in: customers open, follow and reply to tickets and read your knowledge base, in your colours, on your own domain.
Save replies to common questions as canned responses, personal or shared, and run scenarios: one-click macros that set status, priority, assignee and tags.

A library of help articles customers can read to solve problems themselves, such as setup steps, policies and troubleshooting, usually organised in categories on a help centre.
Spin up a workspace and put Knowledge Base through its paces.
Free plan · No credit card · Cancel anytime