ZANUS AI FOR CUSTOMER SERVICE — KNOWLEDGE BASE
KB articles, macros, the escalation matrix, refund policy, release notes, the tribal knowledge in old ticket threads — loaded into curated libraries the AI reads from. Ask in plain language; get the answer with the source cited, at agent speed.
Private tenant or your own server · unlimited agent users · no per-seat pricing, ever

Libraries: current policy outranks the old macro, the signed SLA outranks the draft — you set the order.
KB exports, PDF policies, screenshots of error states, recorded walkthroughs — the ingestion pipeline turns the scattered knowledge into one queryable system.
The customer-facing AI and the agent assistant read the same libraries at different permission levels: update the refund policy once and both answer correctly from that moment.
If the knowledge base does not contain the answer, the AI says so — to the agent and to the customer. Guessing is not a support strategy.
“How did we fix this error code last time?” “What did we tell customers during the March outage?” “Which accounts have the legacy SLA?” The archive answers in seconds with sources attached — instead of asking the one veteran who remembers.

Permissions decide: customers get the public KB libraries; agents get those plus internal policies and escalation guides — enforced server-side, not by prompt hope.
Never. Your tenant is isolated; your knowledge, transcripts and customer records are yours alone — and the on-premises option keeps them physically in your building.
← Previous: Back Office · Sharing with a colleague? 📄 Get the PDF · ✉️ Email this page ·