The assistant can double as your bug tracker and feedback box during a beta. Testers report a bug or leave feedback in the same widget they ask questions in, and each one arrives with the page, device and wallet already attached. Nobody fills in a form.
Turning it on
Open Dashboard, then Beta programme. The page walks a short readiness checklist, then gives you two independent switches:
Bug reports
Adds a Bug button to the widget. A report captures what went wrong and where, then files the whole conversation.
Feedback
Adds a Feedback button. It records an opinion in one line and never argues back.
They are separate on purpose: you can collect feedback without inviting bug reports, or the other way round. Whichever you turn on, the widget shows a Support, Bug and Feedback row, with only the pills you enabled.
What a bug report asks
A bug report asks at most two things: what happened, and where. It never asks for the browser, wallet, network or transaction hash, because the report already carries all of that. When the tester is done, the assistant closes out with 'anything else?', so it is clear the report was filed.
Feedback never gets a reply
Feedback is an opinion, not a support request. The assistant acknowledges it, asks only what the tester expected to happen, and records it. It never promises someone will get back to them, because during a beta nobody can answer every tester individually.
Opening a report at the moment it breaks
From your own code you can open the widget straight into a bug report, so the report starts at the moment of failure rather than whenever the tester thinks to look for a button:
// e.g. in your transaction-failure handler
window.txid.open({ mode: "bug" });The page the tester was on and their wallet are attached automatically. Testers also get a gentle one-time prompt from the assistant itself while a beta is running, so they know the channel is there.
Where reports land
Everything testers record shows up under Dashboard, then Bugs & Feedback: the report itself, the full conversation it came from, and a case record with the page, device, region and wallet. Findings are kept out of your support ticket inbox, so a suggestions box never buries a real escalation.
Read them by screen
The Analytics page ranks bugs and feedback by the page the tester was on when it happened, which is something most support tools never capture. It is the fastest way to see which screen is causing the most trouble.