Escalation Protocol

Escalate unresolved conversations to human agents via SAGE channel.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ferundatattoo/ethereal --skill escalation-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Escalation Protocol
Source: https://github.com/ferundatattoo/ethereal/tree/main/orchestrator/src/concierge/skills/escalation-protocol
Command: npx skills add https://github.com/ferundatattoo/ethereal --skill escalation-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route a conversation to a human (artist or admin) when the bot can't resolve, must respect Bug F escalation gates, and notify via SAGE channel (Regla #45).

Core Features & Use Cases

  • Tools owned: escalate_to_human, escalate_to_artist, request_artist_travel_availability.
  • When to invoke: ALWAYS available — this skill is appended to every eligible set by the resolver. The specific escalation tools to use: escalate_to_human for general 'I want a person' requests; escalate_to_artist for style/budget/timing decisions only the artist can make; request_artist_travel_availability for cross-city / guest-spot inquiries (Doctrine #14 multi-maquila). Bug F gate (Regla #45 + S#77 hardening): only escalate ONCE per pending escalation TTL window (24h). Resolver enforces this via FSM context.
  • Anti-patterns: Escalating in EVERY turn after the first one (spam to artist's SAGE channel). Escalating without summarizing the brief — the artist needs context, not a 'client wants tattoo' ping.
  • Wired by: Resolver selects eligible skills into the set based on FSM state + intent classifier + workspace config (when CONCIERGE_SKILLS_V1_ENABLED=true). The tools listed under capabilities get unioned by harness/skill-tool-union.ts::unionAllowedTools and passed to the LLM as the active palette for the turn. Anything not in the union is invisible to the LLM that turn (progressive disclosure — fixes the 46-tool firehose problem from S#79 P1.quater).

Quick Start

Ask the bot to escalate to a human when automation cannot resolve the user request.

Frequently Asked Questions about Escalation Protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I escalate a chatbot conversation to a human agent with full context?

Human handoff during automated workflows is needed when the bot cannot resolve complex style, budget, timing decisions, or cross-city guest inquiries. Escalation transfers the conversation to a human artist or admin equipped with the full context of the user's request.

When should I escalate a guest spot or travel inquiry to a tattoo artist?

To escalate a conversation to a human agent, the system routes the unresolved request along with a summarized brief of the conversation context. This ensures the human handoff provides the artist or admin with the necessary background details to assist effectively.

What are the limitations on sending human escalation requests through SAGE?

You should escalate cross-city guest spot or travel inquiries when the automation cannot resolve the request. The system uses a specific tool to request artist travel availability and routes the complex multi-maquila logistics directly to the artist for a decision.

Can I trigger multiple escalations if the user keeps asking for a person?

SAGE channel escalation requests are limited by a strict gating mechanism that only allows escalation once per 24-hour pending window. This prevents spamming the artist's channel with repeated pings for the same unresolved conversation.

How does the bot summarize the brief before escalating to an artist?

No, you cannot trigger multiple escalations for the same pending request. The workflow enforces a strict gate that limits escalation to a single occurrence within a 24-hour TTL window, preventing spam to the SAGE notification channel.