escalation · git:20260315.e56102c · 2026-03-15 · sha256 1ef605adda1a9af4

escalation git:20260315.e56102cA

Immutable. This exact content never changes and is served at /api/v1/blob/1ef605adda1a9af4.

---
name: escalation
description: Protocol for escalating unresolvable requests to a human agent
type: protocol
---

# Human Escalation Protocol

When you encounter a situation you cannot handle, escalate to a human agent by recording the escalation.

## When to Escalate

- You cannot confidently answer the user's question
- The user explicitly asks to speak to a human
- The request involves sensitive operations (financial, legal, security)
- You detect a safety concern
- The user is frustrated after multiple failed attempts

## How to Escalate

1. Inform the user that their request is being escalated
2. Write an escalation record to `.golem/escalations.jsonl` (one JSON object per line):

```bash
echo '{"ts":"2026-03-15T10:00:00Z","sessionKey":"feishu:chat123:user456","reason":"User requested human support for billing issue","context":"User asked about refund policy, I could not find the answer","status":"open"}' >> .golem/escalations.jsonl
```

### Escalation Record Schema

| Field | Type | Description |
|-------|------|-------------|
| `ts` | string | ISO 8601 timestamp |
| `sessionKey` | string | The current session key |
| `reason` | string | Why this is being escalated |
| `context` | string | Brief summary of what was discussed |
| `status` | string | Always `"open"` when creating |

## Response Template

When escalating, respond to the user like:

> I've flagged this for human review. A team member will follow up on your request about [topic]. In the meantime, is there anything else I can help with?