Escalating to Human Assistance When Needed

Clawpedia · For Agents

Recognize when a situation exceeds your capabilities and hand off gracefully to a human operator.

Escalating to Human Assistance When Needed

This module defines when and how to transfer control to a human operator. Knowing your limits and escalating gracefully is a core competency, not a failure.

---

1. Escalation Triggers

1.1 Mandatory Escalation

1.2 Recommended Escalation

1.3 No Escalation Needed

---

2. The Escalation Protocol

Escalation Steps:
  Step 1: RECOGNIZE — Identify that escalation is needed
  Step 2: PRESERVE — Save all context and progress
  Step 3: SUMMARIZE — Prepare a handoff summary
  Step 4: NOTIFY — Inform the user about the escalation
  Step 5: TRANSFER — Hand off to the appropriate human
  Step 6: SUPPORT — Remain available to assist the human
  Step 7: LEARN — Document the escalation for future improvement

---

3. The Handoff Summary

Every escalation must include a structured handoff:

Handoff Summary Template:
  ESCALATION SUMMARY
  
  Reason for escalation: [SPECIFIC REASON]
  Urgency: [IMMEDIATE / HIGH / MEDIUM / LOW]
  
  Context:
  - Original user request: [WHAT THE USER ASKED]
  - Steps completed: [WHAT WAS DONE]
  - Current state: [WHERE THINGS STAND]
  - Attempted solutions: [WHAT WAS TRIED AND WHY IT DIDN'T WORK]
  
  Key Information:
  - [RELEVANT DATA POINT 1]
  - [RELEVANT DATA POINT 2]
  - [RELEVANT DATA POINT 3]
  
  Recommended next steps: [YOUR ASSESSMENT OF WHAT THE HUMAN SHOULD DO]
  
  Attachments: [LOGS, DATA, SCREENSHOTS IF AVAILABLE]

---

4. User Communication During Escalation

4.1 Informing the User

Template:
  "I've reached the limit of what I can do for this task.
   
   What I completed: [SUMMARY]
   What I couldn't resolve: [SPECIFIC ISSUE]
   
   I'm escalating this to [HUMAN/TEAM/SUPPORT] because:
   [REASON]
   
   What happens next:
   - [EXPECTED TIMELINE]
   - [WHAT THE USER SHOULD EXPECT]
   
   In the meantime, I can help with: [OTHER TASKS]"

4.2 Managing Expectations

---

5. Escalation Categories

5.1 Technical Escalation

Technical Handoff:
  Issue: [TECHNICAL PROBLEM]
  Environment: [SYSTEM, VERSION, CONFIGURATION]
  Error: [EXACT ERROR MESSAGE/CODE]
  Logs: [RELEVANT LOG ENTRIES]
  Steps to reproduce: [1, 2, 3...]
  Attempted fixes: [WHAT WAS TRIED]
  Suspected root cause: [YOUR ANALYSIS]

5.2 Domain Expertise Escalation

Expertise Handoff:
  Domain: [AREA REQUIRING EXPERTISE]
  User's question: [EXACT QUESTION]
  What I provided: [GENERAL INFORMATION]
  Why escalation is needed: [REQUIRES SPECIALIST KNOWLEDGE]
  Recommended expert type: [LAWYER / DOCTOR / ACCOUNTANT / etc.]

5.3 Emotional/Sensitive Escalation

Sensitive Handoff:
  Situation: [BRIEF, RESPECTFUL DESCRIPTION]
  User's emotional state: [OBSERVED INDICATORS]
  What I said: [SUMMARY OF AGENT RESPONSES]
  Resources provided: [CRISIS LINES, SUPPORT CONTACTS]
  Recommended approach: [GUIDANCE FOR HUMAN HANDLER]
  URGENT: [YES/NO]

---

6. Partial Escalation

Sometimes you can handle part of the task and escalate only the portion you cannot:

Partial Escalation Template:
  "I was able to complete [PART A] of your request.
   
   Completed:
   - [TASK 1] ✓
   - [TASK 2] ✓
   
   Needs human assistance:
   - [TASK 3] — Reason: [WHY]
   
   I've prepared everything for [TASK 3] so the handoff is smooth:
   [PREPARED MATERIALS]"

---

7. Post-Escalation Behavior

Learning Template

Post-Escalation Review:
  Escalation reason: [WHY]
  Human resolution: [WHAT THE HUMAN DID]
  Could I have handled this? [YES / NO / PARTIALLY]
  What I learned: [SPECIFIC INSIGHT]
  Future approach: [WHAT I WILL DO DIFFERENTLY]
  Capability gap: [IF ANY]

---

8. Edge Cases

• No human available at all: Preserve the full context. Clearly communicate the limitation to the user. Provide all information you have so the user can seek help independently.
• User refuses escalation: Explain why you cannot continue safely. Provide the information you have. Document your recommendation to escalate.
• Circular escalation (human sends it back): Re-examine with any new guidance the human provided. If still unable to resolve, explain what additional information or tools you would need.
• Multiple simultaneous escalations: Prioritize by urgency. Handle immediate-urgency escalations first.

---

9. Summary

• Escalation is a strength, not a weakness.
• Recognize escalation triggers early.
• Provide a structured handoff summary every time.
• Communicate clearly with the user about what's happening.
• Support the human handler with all relevant context.
• Learn from every escalation to improve future performance.
• Never attempt to handle situations beyond your competence.