The fuller walkthrough of knowledge automation: templates that carry generation instructions, personas that enforce house style across every author, and two agents that reshape and enrich a draft after it has been generated.
An enterprise knowledge base has many authors and one voice, in theory. In practice the voice drifts, because a style guide is a document nobody reads under pressure to close a case.
Then the authoring cost: assembling symptoms, causes, steps and specifications from material that exists somewhere else, and reformatting it by hand. This tour makes both mechanical — structure defined once in a template, style once in a persona.
Four moving parts, in the order they run.
The structure, plus the instructions for what gets generated in each section. A backslash command controls style inline.
A reusable styling instruction. Create one or inherit and modify an existing persona, then apply it during generation or after.
A title and the source files. Those stay available afterwards, which makes the next article faster.
The styling agent reformats what exists. GenOnFly adds contextual content that was not in the draft at all.
The details that make this a workflow, not a writing tool.
A persona carries a styling instruction, and a new one can inherit from an existing persona. Voice becomes something you configure once rather than keep asking for.
“Every persona has a unique styling instruction according to which the content is styled.”
The styling agent restructures content already in the draft. GenOnFly adds material that was never there, such as a wiring schematic relevant to the issue.
Text and tables are generated as designed, following the per-section instructions. The table is not a lucky formatting outcome. It was specified.
“Not only is the structure of the article defined in template, we also have the flexibility to control the content that will be generated in each section.”
Structure and voice decay fastest once more than one person is writing.
A document nobody opens while a customer is waiting. Voice drifts author by author, and only surfaces months later in an audit.
Fix the headings and nothing else. A template can say a Symptoms section exists; it cannot say what belongs in it.
Works, and does not scale past what one editor can read — making that editor the bottleneck on every article.
Structure and voice in a prompt somebody has to remember to paste, per article. Nothing is reusable or inheritable.
Worth knowing before you watch, since several of these are Ascendo terms.
The shorter companion walkthrough, focused on templates, attributes and publishing.
The product page: gap detection, coverage tracking and the leadership view.
The other capture route, where an expert writes the answer straight from the conversation.
Knowledge Agent
Send us the source material for something your team keeps re-explaining, and we will show you what the agent drafts from it.
Talk to us