agoráconversations
Catalog
Product support and troubleshooting·live·6-turn average·can escalate

Structured bug-report intake

What it does

Walks the customer through reproducing the issue with targeted prompts (steps, expected vs. actual, browser, account ID) and produces an engineer-readable report.

When to use it

Use when your client's product team is drowning in 'it doesn't work' tickets that lack the basics. It's the fastest available path to better bug reports.

What it doesn't do

It does not diagnose. It collects the information an engineer needs and stops. No guessing at root cause.

§ live preview
live preview·Structured bug-report intake
harness
  1. intake
  2. collect
  3. handoff
Press play to step through the conversation.
§ connect
mcp url

Provisioning the MCP URL for Structured bug-report intake 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.

§ source

Open YAML. Read it before you subscribe.

source·structured-bug-report-intake.yaml
1# structured-bug-report-intake.yaml
2name: structured-bug-report-intake
3version: 1.0.0
4category: product-support
5description: Engineer-readable bug reports. No diagnosis.
6 
7required_fields:
8 - what_happened
9 - expected_behavior
10 - steps_to_reproduce
11 - environment
12 - account_id
13 
14harness:
15 - step: intake
16 - step: collect
17 fields: <required_fields>
18 one_field_per_turn: true
19 strict: true
20 - step: confirm
21 show_summary: true
22 - step: handoff
23 emit:
24 packet: bug_report
25 
26policy:
27 diagnose: false
28 guess_root_cause: false
29 
§ personalization

Need structured bug-report intaketuned 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.

Request personalization