How to prepare a bug-report draft from an Intercom conversation
A support conversation can contain the evidence needed for an engineering report, but it often lacks a formal structure. This tool turns the selected material into a draft with clear gaps.
Start with the right material.
- What you provide
- selected Intercom messages describing a product issue.
- The intended result
- A draft with observed behavior and missing reproduction details.
How the workflow works.
Separate expected and actual behavior, reproduction information and environment details. Retain source references and exact errors while marking anything that still needs confirmation.
What to check in the result.
Review the evidence before creating or escalating an issue. The draft should not invent steps, diagnose a cause or claim a fix has been tested.
Preview the Markdown to check headings, lists and links as well as the words. Keep source references with the document so a reviewer can trace important statements back to the material you supplied.
Learn from the worked example.
The downloadable Markdown example shows one possible organization of the result. Read it alongside the source example and notice which statements are recorded facts, proposed wording or questions still needing an answer.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.