Why this matters
Keeping one issue in one conversation preserves the investigation history.
Step by step
- Find the original ticket by subject or reference and read the latest response before replying.
- Add requested evidence and explain what changed since the previous message; avoid opening duplicate tickets just to repeat the same question.
- The conversation should contain one coherent timeline and a clear pending action.
Keep the result of the final check and any unresolved question with your project records.
Availability depends on the product, permissions and management agreement. Use the existing support conversation for the same issue.
