Talk to us

Knowledge base on the portal, the app and tickets

Write the questions people ask and their answers once. They are offered while someone raises a ticket, on the portal's Help articles page and in the app. They are suggested to your team on each ticket, and sent to the requester in one click. A solved ticket can become a new article.
PLANSScale only

The problem it solves

  • Half your tickets ask how to reset the same password or where the same form is.
  • Each agent answers the same question in a different way.
  • A technician finds the fix for an odd fault, and the next person starts from zero.
  • You cannot tell which help pages help and which nobody reads.

How it works

  1. A technician or team lead opens Helpdesk > Knowledge Base and clicks New. They type the Question as people ask it, a Short Answer, Keywords and the Issue Types it belongs to.
  2. They choose the Audience (Everyone Who Can Raise Tickets, Customers, Internal Requesters, or Service Team Only), write the full Answer and click Publish.
  3. While a requester types the title of a new ticket on the portal or in the app, articles appear. Matching ones show under "These may answer it right away:". Yes, no ticket needed closes the form and counts a ticket avoided.
  4. On each ticket, the Articles button lists the articles that match it. Send (or Send to the Requester inside an article) posts a link with the short answer to the requester.
  5. On a solved or closed ticket, Write an Article starts a new one from the ticket's title and resolution. The article keeps the ticket in Written From Ticket.
  6. The Use tab shows Views, Helped, Did Not Help and Tickets Avoided; the filter More Unhelpful Than Helpful finds articles to rewrite.

Everything it does

An article

  • Question, Short Answer (shown in suggestions, up to 240 characters), Answer, Keywords, Issue Types
  • Audience: Everyone Who Can Raise Tickets (to start with), Customers, Internal Requesters, or Service Team Only
  • Published or not; only published articles are shown outside the service team
  • Entity: empty for every Entity, or one
  • Can be translated into your other languages

Search

  • Words of the question count most, then the keywords, then the answer
  • Articles of the ticket's issue type, or its parent type, come first
  • Up to 12 words of a search are used; small common words are skipped

Who reads what

  • Customers' people read published articles for Everyone and for Customers
  • Employees, students, parents and residents read those for Everyone and for Internal Requesters
  • The service team reads every article, published or not
  • Send to the Requester is refused when the article is not published for that requester

Where it shows

  • Portal: Help articles in the menu, with search, topics and "Did this answer it?"; suggestions on the raise form
  • The SmartMy Desk app: suggestions while raising a ticket, with Did this answer it?
  • Back office: Helpdesk > Knowledge Base, and the Articles button on a ticket
  • With AI on tickets, a suggested reply also uses the matching articles

Who uses it

TechnicianWrites and edits articles, sends them to requesters, and turns solved tickets into articles.
Team leadPublishes, rewrites the unhelpful ones and deletes old articles.
Customer, employee, student or residentReads the answers on the portal or in the app before raising a ticket, and says whether they helped.

Where you use it

  • Web: Helpdesk > Knowledge Base; the Articles button on a ticket
  • Customer portal: Help articles, and suggestions on the New ticket form
  • The SmartMy Desk app: suggestions while raising a ticket (built and in testing, not in the app stores yet)
  • Not offered: a public help site for people who are not signed in

What you control

Settings

  • Audience per article: Everyone Who Can Raise Tickets
  • Published: off for a new article
  • Entity per article: empty, meaning every Entity

Notifications

  • Send to the Requester posts a public message on the ticket, so the requester gets it like any reply

Questions

Can customers read articles without signing in?

No. Articles are shown to people signed in to the portal or the app, by their audience.

Can we keep some answers for our team only?

Yes. Set the Audience to Service Team Only. Those articles are never shown on the portal or to requesters.

How do we know an article works?

Each article counts Views, Helped, Did Not Help and Tickets Avoided. Filter More Unhelpful Than Helpful to find the ones to rewrite.

Can an article be written from a ticket?

Yes. On a solved or closed ticket, Write an Article starts one from the title and the resolution. Check it before you publish it.

Which plan has the knowledge base?

Scale.

Related features

See one of your own jobs run through it.

Tell us how a complaint reaches you today and what you bill for. We will show you the same job in SmartMy Desk.