Use the authorized case history
Provide the ticket record, relevant customer replies, allowed diagnostic details, and your escalation rules. Remove credentials and unnecessary personal information. State the period covered and whether any conversation happened outside the supplied record.
The packet should identify the case and product area without copying sensitive content into a Slack channel with a broader audience.
Preserve what was observed
Ask Nema to separate reported symptoms, reproduced behavior, expected behavior, and hypotheses. Include timestamps, environment details, affected scope, and exact error text when appropriate. Link back to the source for each important fact.
If support could not reproduce the issue, say that. A failed reproduction is useful evidence when the packet also records the tested conditions.
Show work already completed
List troubleshooting steps and their outcomes so the receiving team does not repeat them blindly. Note any temporary workaround, whether the customer tried it, and what remains uncertain.
Nema can compare the packet with your required fields and ask for missing logs, versions, or reproduction details. It should not invent a severity or route based only on emotional language in the ticket.
Hand off in the channel
Support reviews the customer summary and confirms visibility. The receiving specialist checks that the evidence is sufficient, then accepts or redirects the escalation. Engineering or the designated incident owner chooses severity and assignment.
The Slack thread can hold clarification without rewriting the original ticket. Nema can update the packet as new facts arrive while preserving what changed.
Start with a resolved escalation
Use a past case to compare Nema's packet with what the receiving team eventually needed. Check whether reproduction details, attempted actions, and impact survived the summary. Refine the checklist before using it on an active case.
Questions from support teams
Can Nema set severity?
It can apply supplied criteria and prepare evidence for review. The authorized support or engineering owner confirms severity.
How are customer details protected?
Use only authorized records and a Slack channel with matching access. Remove fields the receiving team does not need.
Does escalation close the ticket?
No. The packet helps transfer work. The case owner remains responsible for status and customer communication.
When the receiving team resolves the case, compare the final diagnosis with the original packet. Add missing evidence requirements to the escalation checklist, but keep product-specific conclusions out of unrelated future cases.