Skip to main content
Turn a reported problem into a ticket that separates the customer’s observation from a verified reproduction. A transcript can preserve the request and impact; it cannot establish the root cause or prove a fix shipped.

Start here

Choose one meeting and check related support replies and existing issues. Confirm the customer’s platform and version where available. Keep unrelated customer details out of the ticket.

Copy this prompt

Use this in Screenpipe chat or an assistant with the required connections. Replace the brackets with your details. If the assistant lacks access, provide a reviewed excerpt; a prompt alone does not connect it to your history.

Check the result

Link each reported observation to a source passage. Have engineering verify a reproduction before labeling the cause. Review the final ticket for private identifiers before publishing it.
One meeting can contain a defect, a requested improvement, and a training question. Keep their acceptance criteria distinct so a documentation clarification does not falsely close a software defect.After a change, verify the current implementation and relevant test result. A merged PR, a released build, and a customer-confirmed resolution are different milestones; report the milestone actually established.

Continue

Meeting follow up · engineering decision log · incident reconstruction