Kobal reads what customers keep asking and what your team keeps telling them. It shows which article or macro is missing, out of date or not landing, with the tickets that prove it, and drafts the fix for its owner’s yes.
Kobal checks each article and macro against what your agents have told customers since it was last changed, not against the date on it. You see the one sentence that’s wrong and every version your team sends instead.
A one-off isn’t a gap. Kobal waits until enough tickets ask before it raises a question, and leaves alone the ones you’ve chosen not to answer.
Kobal drafts the fix from the replies that settled the question, in the style of your own help centre, and every change points at the tickets it came from. You review your team’s best answer, not a guess.
Yours to edit. Every line can be changed before anyone approves it, and its tickets stay attached.
A drafted revision of “Reading your invoice”: the old sentence struck out, two new sentences added, each showing how many replies it was drawn from, and the macro that will be brought in line.
Once the article’s owner says yes, Kobal makes the change in your help centre, where customers already read it. Where a tool won’t take edits, the owner gets it as a task, and it’s checked just the same.
Off until you switch it on. Kobal publishes only where you’ve allowed it, and each change waits for its owner’s yes.
Once enough new tickets have come in, Kobal runs the check that found the gap again and writes the result on the article. If few people opened the new version, it tells you that instead, because it needs a better link, not a rewrite.
A first read isn’t a result. After a week, Kobal shows an early read marked provisional, and waits for enough tickets before it calls it.
Can't find what you're looking for?
Visit our Help Center.
Bring your help centre. We’ll show you where it’s missing, out of date or sending customers back to support.
Get early accessWorks on top of the helpdesk you already use. No migration.
