Knowledge base
Answers customers find themselves.
Publish help articles your customers can search and read, so the easy questions never become tickets.
Knowledge base in practice.
Write the answer once, publish it to your help center, and link it in replies.
Articles that read well
Write how-tos, FAQs and guides with headings, numbered steps, callouts and tables.
Search that surfaces the answer
Customers type a few words and the help center narrows to the articles that use them, the answer opening right there.
Public, and free to read
The help center is public, so anyone can search and read it without a login and without taking a seat.
The article and the answer are the same library.
What a customer searches in the portal is what your team links to in a reply.
Customers search the help center
Across every published article, with no account.
Agents insert an article into a reply
As a link the customer can open.
A draft stays with your team
It never shows on the help center.
More in Support & Service.
Each one is its own page, on the same records.
Knowledge base, on your own data.
Bring a spreadsheet or an export to a demo and see it there.
Questions, answered
Yes. Leave it as a draft: only your team can see it, in Articles. Publish it when it should be on the public help center.
Not yet. It runs on a Spodus URL and carries our badge — a custom domain and removing our branding are not built.
Yes. The help center is public, so anyone can search and read. No login, and no seat.