--- title: "Sainapse: Knowledge from Resolutions" description: "Every resolved ticket becomes structured knowledge: a close summary at resolution, then drafted articles your content team reviews before publishing." canonical_url: "https://www.sainapse.ai/features/knowledge-from-resolutions" markdown_url: "https://www.sainapse.ai/features/knowledge-from-resolutions.md" text_url: "https://www.sainapse.ai/features/knowledge-from-resolutions.txt" archetype: "feature-leaf-deep" --- # Sainapse: Knowledge from Resolutions Customer Support ## Knowledge from Resolutions Every resolved ticket becomes structured, searchable knowledge the moment it closes. Nobody has to file it as a separate documentation task. Sainapse writes a close summary on every resolution and drafts knowledge-base articles from the patterns underneath them, the way Ford's deployment does today, with your content team approving what publishes. On this page: - [What it is](https://www.sainapse.ai/features/knowledge-from-resolutions#features_knowledge_from_resolutions_03) - [How it works](https://www.sainapse.ai/features/knowledge-from-resolutions#features_knowledge_from_resolutions_04) - [Capability classes](https://www.sainapse.ai/features/knowledge-from-resolutions#features_knowledge_from_resolutions_05) - [What powers it](https://www.sainapse.ai/features/knowledge-from-resolutions#features_knowledge_from_resolutions_06) - [Publishing](https://www.sainapse.ai/features/knowledge-from-resolutions#features_knowledge_from_resolutions_07) - [Questions](https://www.sainapse.ai/features/knowledge-from-resolutions#features_knowledge_from_resolutions_08) Updated August 2026 What it is Every resolved ticket is a fact pattern: what broke, what fixed it, who it happened to. Most helpdesks let that pattern evaporate the moment the ticket closes: the fix lives in one agent's memory, not in anything searchable. Sainapse writes a structured close summary on every resolution instead, turning the ticket itself into retrievable institutional knowledge, available to the next agent, the next ticket, and the published knowledge base. How it works ## From close summary to grounded draft. ### Close summary Step 1: Sainapse writes a structured summary the moment a ticket resolves (the fix, the cause, the steps) without asking an agent to file it separately. ### Retrieval corpus Step 2: Those summaries accumulate into a searchable corpus Sainapse can retrieve from on the next similar ticket, grounding its drafts in what worked before. ### Grounded future drafts Step 3: The next resolution draft cites the pattern instead of guessing. Sainapse drafts knowledge-base articles from that same corpus, live today at Ford. Capability classes ## Three ways a knowledge base handles resolved tickets. Most support stacks fall into one of two classes below, whether or not the vendor calls it a knowledge base. | | Static KB | Suggest-only search | Sainapse | | --- | --- | --- | --- | | Update trigger | Someone remembers to write an article | Someone remembers to write an article | Every ticket resolution, automatically | | What's captured | Whatever an editor has time for | Existing articles, ranked by relevance | Structured cause, fix, and category, every close | | Freshness | Drifts as the product changes | Only as fresh as the KB it searches | As current as the last resolved ticket | | Publishing | Manual, ad hoc, someone's side project | N/A, search only: no new content | Close summaries on every resolution; drafted articles into your KB, reviewed by your team | ## What powers the corpus. - **Runs on**: Your existing helpdesk's ticket history, whatever system you already resolve tickets in. - **Feeds it**: Every resolution Sainapse closes, structured into cause, fix, and category at close time. - **Retrieval**: Search over the accumulated corpus, grounding new drafts in prior resolutions instead of a blank page. - **In production**: Ford's deployment drafts knowledge-base articles from resolution patterns today: the template the rest of the rollout follows. - **Publishing**: Drafts land in your content team's queue, cited to their source tickets; a person approves what publishes. Publishing ## Drafted by Sainapse, published by your team. Sainapse writes a close summary on every resolution, then drafts knowledge-base articles from the patterns those summaries expose: the shape of a recurring issue, the fix that keeps working, the category it belongs in. Ford's deployment drafts KB articles from resolution patterns today. Each draft arrives in your content team's queue citing the tickets it came from, and a person approves what publishes. That review step is deliberate: it is how a knowledge base grows from confirmed outcomes at ticket speed without anyone losing editorial control of what your customers read. ## Common questions ### What stops a bad resolution from becoming bad knowledge? Nothing publishes itself. Close summaries live on the ticket, visible and correctable, before they ever feed a future draft, and every drafted article carries citations back to its source tickets so a reviewer can catch a wrong fix before it goes live. ### Can one mistaken fix contaminate future resolutions? A single close summary is one data point among many. Retrieval weighs it against the wider pattern, not in isolation. Because drafted articles cite their source tickets, a reviewer can trace a bad pattern back to the resolution that caused it and correct it there. ### Who reviews a drafted knowledge-base article before it goes live? Your content team. Drafts land in their queue with the source tickets cited, so a reviewer can trace every claim back to the resolution it came from: proposed by Sainapse, published by a person. Editorial control over what your customers read stays with the people who already own it. ### Does this replace the knowledge base we already have? No, it feeds it. Sainapse writes close summaries inside your existing helpdesk and drafts articles for the knowledge-base tool you already run, so there's no new system to migrate content into and no export step your content team has to run before a draft reaches their queue. ### Is knowledge captured only when a ticket closes, or continuously? At close, not continuously. Sainapse writes the structured summary the moment a ticket resolves, so the corpus grows only from confirmed outcomes: never from a ticket that's still open, abandoned mid-fix, or actively being worked, where the resolution hasn't been proven yet. ### Part of - [Customer Support](https://www.sainapse.ai/workflows/customer-support): The workflow this feature ships inside, end to end. - [All features](https://www.sainapse.ai/features): Every capability, in one index. ### Related - [Autonomous Resolution](https://www.sainapse.ai/features/autonomous-resolution): The graduated-autonomy ladder that produces the resolutions this feature learns from. - [Grounded Response Drafts](https://www.sainapse.ai/features/grounded-response-drafts): The same retrieval corpus, grounding drafts on open tickets instead of closed ones. - [SaaS Technology](https://www.sainapse.ai/resources/solutions/saas-technology): Where accumulated resolution history compounds fastest, at SaaS ticket volume. ## Turn a month of closed tickets into articles. - [Book a demo](https://www.sainapse.ai/book-a-demo) ## Sitemap See the full [Sainapse sitemap](https://www.sainapse.ai/sitemap.md).