Welcome to Agentic Knowledge Base & Self-Service thatfinds the question the ticket stream keeps asking.
Most knowledge bases are a graveyard with a search box. Risely reads the ticket stream for the question that keeps repeating, drafts the article from real resolutions, and retires what nobody opens.
The knowledge loop · this term
reading the stream
Tickets, as they were written
cant connect to eduroam on my phone
wifi asks for a certificate and then fails
eduroam worked yesterday, not today
phone updated and now no campus wifi
wifi keeps saying authentication problem
One question: eduroam on Android 15
43 tickets this term · no article
The draft, from what actually worked
Forget the saved network first
Choose the certificate the campus issues
Set the identity to the campus address rather than the alias
"authentication problem" is in the title
the exact words people paste into search
Tickets on this topic
43 and holding
The answer reaches the person before the ticket does.
Someone pastes the error text into search and the article comes back first, because Risely's agents titled it in those words. The steps match the screen, so nothing gets filed.
Self-service works
searching
The error text goes into search
pasted, exactly as the screen said it
The article comes back first
because the title carries those words
The steps match the screen
written from what the technicians did
No ticket gets filed
and the queue never hears about it
Having an answer and being findable are different problems, and only one of them empties a queue.
An article ranks once its dead cousins are gone.
Risely's agents retire the 31 articles with no views and stale steps, and merge the three VPN guides that disagree into the one that is current. The living answer stops competing with its own history.
What search returns
pruning
31 articles with no views
retiredstale steps, screens that no longer exist
Three VPN guides that disagree
retiredmerged into the one that is current
The living article
ranks firstnow the first result for its own question
A knowledge base competes with its own history, and the obsolete cousin usually wins on search.
The ticket stream says when an article stopped being true.
Campus software changes every term. Risely's agents compare the published steps against what technicians did this week, flag the article that drifted, and put both versions in front of the writer.
An article going out of date
comparing
The published steps
written for the screens that existed last term
What technicians did this week
a different setting, a renamed menu
The article gets flagged
the resolutions stopped matching it
An updated draft goes to the writer
with both versions side by side
Campus software changes every term, so an article is only true until the next update ships.
Nothing publishes until the writer says so.
Risely's agents draft the article and cite the tickets that asked for it. The technical writer publishes, edits, or sends it back, and the campus keeps reading one house voice.
Waiting on the technical writer
nothing publishes until this yes
New: eduroam on Android 15
drafted from the resolutions that worked
Update: the VPN guide
one guide replacing three that disagreed
Risely's agents write the draft and cite the tickets behind it. The writer owns the voice, and the campus reads one house style.
One thing moves. The loop re-runs.
An operating system update, a vendor that renames a menu, a policy that changes over the summer. Any of them dates an article, and every one runs the same way.
An update changes the steps
the screens in the article are gone
The same tickets come back
one question, five new wordings
Risely flags the article
the resolutions stopped matching it
The draft rewrites itself
from what technicians did this week
The writer publishes the new one
and the count falls again
Agentic Knowledge Base & Self-Service never works alone.
What changes, and how it runs.
The repeat question gets an article
Risely drafts it from the resolutions that worked.
The right answer ranks first
Retired cousins stop competing with it in search.
The base tracks reality
An article that drifts gets flagged by the stream.
The technical read
Connects read-only to your ticketing system, knowledge base, and portal search to start
A technical writer approves every article before it publishes
Every action lands on an append-only log
Runs alongside what you have. Nothing rips out.