Skip to main content
Use resolved cases to explain a repeatable symptom, diagnosis, correction, and verification. A customer saying something worked is useful evidence for that case, but it does not prove the same fix applies to every version or platform.

​
Start here

Select a resolved case and its latest thread replies. Identify the product version, affected platform, actual corrective step, and the evidence that the issue was resolved.

​
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

Have someone unfamiliar with the case follow the article using a test scenario. Verify current UI labels and remove any step whose only support is an AI-generated answer inside the original conversation.
Cluster cases by the same underlying failure, not merely the same keyword. Missing audio, a failed transcription job, and an empty summary can look similar but need different instructions.Keep customer-specific evidence in a private ledger. The public article should stand on reproducible behavior and current documentation. Add links to existing setup pages instead of duplicating their instructions and allowing them to drift.

​
Continue

Missing recordings · scheduled task debugging · meeting transcription