Known-issue lookup
Reads the customer's symptoms, compares them against the list of known open issues your client passes in, and confirms a match (or rules one out) before routing.
Use during incidents and known-bug periods. It prevents the same customer report from being investigated three times.
It does not search the issue tracker. The candidate set of known issues must be supplied by your client's incident or product system.
- intake
- classify
- confirm
- handoff
Provisioning the MCP URL for Known-issue lookup is part of Pro.
Free accounts can read the YAML, run the Live Preview, and provision one starter URL. Pro provisions URLs for the whole catalog.
Open YAML. Read it before you subscribe.
The harness that enforces this YAML is closed and hosted. The YAML is what you can audit, fork, and reason about.
1# known-issue-lookup.yaml2name: known-issue-lookup3version: 1.0.04category: product-support5description: Confirms a customer report against known open issues.6 7inputs:8 - name: symptoms9 type: string10 - name: known_issues11 type: array12 13harness:14 - step: intake15 - step: classify16 match_against: known_issues17 - step: confirm18 show_match_or_none: true19 - step: handoff20 Need known-issue lookuptuned to one client’s voice, escalation logic, and required fields? That’s a $99 personalization.
One-shot fee. Turnaround stated up front. The result is yours, with the deterministic harness already wired.
- Structured bug-report intakeWalks the customer through reproducing a bug and produces a clean, engineer-readable report.
- Feature discoveryHelps the customer find the existing feature that solves their problem, grounded in the product docs you supply.
- Configuration walkthroughStep-by-step setup guidance grounded in your client's documentation.