Start with approved knowledge
Import selected runbooks and resolved tickets with client access boundaries.
In development · IT support knowledge
Make the next support answer easier to verify.
We’re building a support copilot for small managed-service providers. Turn approved runbooks and past ticket resolutions into cited draft answers technicians can review.
Source-linked findings · Human review at each step
REVIEW BRIEF / 001ILLUSTRATIVE EXAMPLE
A reset procedure needs a version check
Fictional documents · sample findingHuman review
What the sample evidence says
A fictional ticket refers to a newer router model than the approved runbook covers.
Planned output: links to supporting passagesA specific next step
Confirm the device and current procedure before recommending a change.
Workflow preview · Illustrative documents and findings
Sources → findings → reviewed actions
DESIGNED FORSmall IT managed-service providers and support desks
The product workflow
Make the evidence easier to use.
Planned inputs: Approved runbooks, knowledge articles, and customer-authorized ticket histories. The first release will focus on one repeatable workflow, with people reviewing the result.
Find the relevant procedure
Claude will retrieve supporting passages, draft troubleshooting steps, and flag missing context or conflicting instructions.
Keep execution with a technician
A technician checks the answer and approves any customer response. Direct ticketing integrations are future work.
Built around evidence
Every finding should be reviewable.
The planned Claude integration will read source documents, reason across relevant passages, and produce structured drafts with references and open questions.
Clear sourcesLink the reasoning to the document passages that support it, and flag missing evidence.
A deliberate review stepTechnicians will approve responses and remain in control of troubleshooting actions and customer-system changes.
A focused first releaseDocument uploads and reviewed exports first. Connected-system integrations will be considered after the core workflow works.
Product development
A focused first release.
What is the product designed for?
Small IT managed-service providers and support desks. The workflow brings relevant documents, source-linked findings, and reviewed next steps into one packet.
What is on the roadmap?
The first release will support approved runbooks, knowledge articles, and customer-authorized ticket histories, structured findings with citations, and reviewed exports. Connected-system integrations will follow the core document workflow.
How can I help shape the workflow?
Share the document review, questions, and handoffs your team repeats. We’re focusing development on a practical workflow that fits how your business operates.
A clearer workflow starts here.
Share the documents, questions, and handoffs that slow your team down.