escalation

Featured

Escalate unresolvable or sensitive requests to a human agent by recording an escalation entry. Use when the user asks to speak to a human, the bot cannot answer confidently, the request involves financial, legal, or security concerns, a safety issue is detected, or the user is frustrated after repeated failures.

AI & Automation 322 stars 43 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
84
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
78
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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? ## Verifying Escalation After writing the record, confirm the file exists and the e...

Details

Author
0xranx
Repository
0xranx/golembot
Created
6 months ago
Last Updated
6 days ago
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

human-escalation

Recognize when to stop autonomous work and escalate decisions, ambiguity, or risk to a human.

2 Updated 1 months ago
varunk130
AI & Automation Listed

escalation

Runs the first four hours of an account on fire: what to say before you know the answer, who to pull in, and what the customer actually wants, which is often not the fix. Trigger whenever the user says "escalation", "the account is escalating", "their VP is involved", "this has gone to their exec", "angry customer", "they are threatening to churn", "account on fire", "major incident with a customer", "they want a call today", "I need to escalate this internally", or describes a customer situation that has just moved above their usual contact. It separates the incident from the relationship damage, sets one owner and one cadence, decides who to pull in and when, and plans the repair step most teams skip. Use hard-conversation when you are the one delivering bad news that has not landed yet, and churn-postmortem when the account has already gone.

1 Updated 5 days ago
CSPulse
AI & Automation Listed

internal-escalation

Gets your own company to act, with the ask and the evidence shaped for the people you are asking rather than for you. Trigger whenever the user says "internal escalation", "escalate internally", "I need engineering to look at this", "get leadership involved", "how do I get this prioritised", "nobody is picking this up", "I need an exception", "raise this with my manager", "who do I go to", or describes needing something from another team on a deadline. It works out who can actually decide, states a specific ask rather than a request for attention, refuses to inflate severity, and plans the follow-through. Use escalation when the customer is the one escalating and the first four hours are customer-facing, and product-feedback when the ask is roadmap consideration rather than action now.

1 Updated 5 days ago
CSPulse