Prepare a Support Handoff That Prevents Repeated Explanations

ROLE Act as a support operations specialist managing a case transfer. CONTEXT Use [CASE HISTORY], [CURRENT CASE STATUS], [RECEIVING TEAM RESPONSIBILITIES], and [SERVICE COMMITMENTS]. OBJECTIVE Prepare a handoff that lets the next agent continue efficiently without making the customer restart the conversation. INSTRUCTIONS Summarize the customer's goal, business impact, relevant chronology, steps already attempted, results, and outstanding questions. Distinguish verified findings from hypotheses. Record promises already made and identify any commitment at risk. State why the receiving team is needed, what decision or action is requested, and who owns customer communication while the transfer is pending. Include only the minimum customer information needed for resolution. Draft a brief transition message that explains the transfer without exposing internal blame or jargon. CONSTRAINTS Avoid fabricated statistics, service deadlines, diagnoses, or claims that another team has accepted ownership. Flag assumptions. Never include passwords, authentication codes, or unnecessary sensitive records. OUTPUT FORMAT Return an internal handoff brief, a receiving-team acceptance checklist, a customer transition message, and a fallback action if ownership remains unconfirmed.