---
name: handoff-reply-to-human-agent
description: Writes a customer service reply and an internal handoff note when a case may need a human agent. Use when you have the customer message, the policy and the escalation rules.
---

# Reply to a customer and hand the case to a human agent

## When to use
Use this skill when a customer message might need a person to take over. Typical signs are a request outside policy, a complaint, a legal mention, a large order value or a repeat contact. Also use it for a routine message when you want a safe reply that checks the rules first.

## What to ask for
Ask the user for each item below. If an item is missing, ask for it before writing anything.
- The customer message, as received.
- The policy text that applies to this situation.
- The escalation rules: when a human must take over, who receives the case, and how urgency is set.
- Case facts: dates, order or account value, earlier contacts and what has already been tried.
- The channel, tone and sign-off for the reply.

If the user pastes personal data that is not needed, such as full card numbers or home addresses, suggest removing it and leave it out of your output.

## Steps
1. Read the customer message and find the actual request, the problem and the customer's mood.
2. Compare the message and case facts with each escalation rule. List every rule that applies and the owner each rule names.
3. If more than one owner is named, suggest which owner should lead and mark that suggestion [ASSUMED] unless the rules say who leads.
4. Compare the request with the policy. Note what the policy allows, what it forbids and where it says nothing. Do not add limits the policy does not state.
5. Write the reply. Acknowledge the specific problem, say what happens next and who will contact the customer, and ask only for information the agent needs. If the customer asked for something by a set day, do not agree to it unless the policy allows it.
6. Write the handoff note if any rule applies or the policy is silent on a serious request.
7. Check the reply line by line against the policy and remove any unsupported promise. Check the note for worked-out dates or inferred policy points and mark them [ASSUMED].

## Output format
Give the output in this order and keep the headings.

```text
Decision: Handoff needed or No handoff needed, with each rule that applies, its owner, and the suggested lead owner

Reply to customer:
(under 150 words, plain language, customer's name)

Handoff note:
Reason:
Urgency: High, Medium or Low, with one line on why
Customer wants:
Already tried:
Policy points that apply:
What the customer has been told:
Suggested next step for the agent:
Open questions:
```

If no handoff is needed, write the reply, give the reason in the Decision line and leave out the note.

## Quality check
- The reply contains no refund, replacement, exception, compensation or date unless the policy allows it for this exact case.
- The Decision line names each rule that applies, or says that none applies.
- When several rules apply, a lead owner is suggested.
- Every fact in the note comes from the message, the case details or the policy. Anything worked out or assumed is marked [ASSUMED].
- The reply names the customer's real problem and says who will contact them next.
- The note lets another agent act without asking the customer to repeat anything.
- The reply makes no admission of legal fault.

## Watch-outs
- Do not promise anything to calm the customer. When the policy is silent or the request goes beyond it, say that a colleague will review the case. Give no date unless the policy provides one.
- Do not invent order facts, names, dates, next steps or policy wording.
- Do not argue with threats or complaints. Acknowledge the concern and move to the next step.
- Keep personal data to the minimum. Remind the user to use an approved workspace and to follow their obligations under India's DPDP Act or GDPR.
- Tell the user that a person should read the decision, the lead owner, the reply and the note before anything is sent or saved.