LearnGrokLong cases become hard to transfer when the ticket contains repeated explanations, several agents and promises buried in old replies. Use these prompts to produce a note that lets the next owner act without rereading the whole thread.
They are for unresolved support cases moving between shifts, queues or specialist teams. Paste the complete history where possible. Keep private notes, customer messages and system events together if each changes what the next owner needs to do.
Key point
Preserve the decision
A useful handover names one decision or next action. It does not try to retell the whole case.
Choose the right handover
Start with Standard unresolved-case handover for most open tickets. It gives the next agent the issue, prior work, commitments, status and one decision to make.
Use Cross-team escalation handover when the receiving team needs a focused investigation request. It keeps customer reports separate from confirmed facts, which matters when a technical or operations team must decide whether to act.
Use Shift-change handover when time matters more than background. It is deliberately short. The Do not repeat field stops the next agent from sending the same failed instruction or reopening an already completed task.
Use Handover with promise audit when the ticket has changed hands repeatedly. Run it before transfer if a refund, callback, replacement, investigation or response deadline may have been mentioned.
Use Handover fact check after you have a draft. It is also the right choice when notes disagree, a case has been merged, or you suspect an old update is being treated as current.
| If the case looks like this | Use this prompt | What you should get |
|---|---|---|
| One long unresolved thread | Standard unresolved-case handover | A complete note for the next owner |
| A specialist team must investigate | Cross-team escalation handover | Evidence, impact and a precise request |
| A shift ends before resolution | Shift-change handover | The first action for the next agent |
| Several commitments appear in the thread | Handover with promise audit | A table of promises and their status |
| The draft may contain errors | Handover fact check | Supported corrections with evidence |
Prepare the ticket history
- Copy the full relevant history into the placeholder. Include the original customer report, agent replies, internal notes, system events and attachments described in the thread.
- Remove unrelated conversation from a merged case. Do not remove an old message just because it is old if it contains a promise, deadline, case reference or attempted fix.
- Add the receiving team only where the escalation prompt asks for it. If you do not know the team, leave the placeholder as a description such as
[billing operations team, if confirmed]or use the standard handover instead. - Keep identifiers that the next owner needs, such as an order number, account reference, error text or existing case ID. Follow your organisation’s handling rules for customer data.
Watch out
Do not paste only the latest message
The latest update often omits an earlier promise or a failed step. That is how commitments disappear at handover.
Read the output before you transfer it
Treat the result as a draft assembled from the history, not as the case record. Check it against the ticket while the case is still assigned to you.
First, verify the customer’s issue. It should describe the actual unresolved problem, not merely the latest question. A customer asking for an update may still be waiting on a missing order, a disputed charge or a failed account change.
Next, check actions already taken. Each action needs an outcome. “Sent to billing” is not enough if the history says billing rejected it, requested evidence or completed the work. Confirm that completed actions are not presented as pending.
Then check the promises and deadlines line by line. Look for words such as “will”, “by”, “within”, “callback”, “refund”, “replace” and “update”. Ensure the note distinguishes an agent’s explicit commitment from a customer request.
Finally, read the next owner’s decision as if you have never seen the case. It should tell you what you must decide, investigate or send next. If it says only “follow up”, the handover is too vague.
Check
A quick test
The note worked if the next owner can identify the case, find the evidence, avoid repeating work and choose the next action without asking what happened first.
Handle ambiguity openly
A good handover does not hide gaps. If two messages name different deadlines, retain the conflict and identify both entries. If a refund was discussed but no approval is recorded, say that approval is not evidenced. If an agent says they contacted another team but there is no reply, record the contact attempt rather than claiming the other team owns the case.
Do not resolve uncertainty by selecting the most reassuring version. The receiving agent needs to know what is unknown before they contact the customer or escalate again.
Note
Keep status separate from sentiment
A frustrated customer may require careful handling, but frustration alone does not show whether an action is complete, pending or blocked.
When the result does not work
If the note is too long, use the shift-change prompt, then paste the result into the fact-check prompt with the original history. If the next decision is still unclear, the history is probably missing a key internal update, ownership record or policy decision. Find that item before transfer and rerun the handover.
If the output drops IDs, dates or attachments that matter, put those items in the history near the top and run the prompt again. Interface behaviour and available features can vary, so check the xAI documentation overview if your workflow behaves differently.
