Moderate risk
Signed pack $29
GDPRSOC2

Escalation Routing Agent

Escalations reach the right owner the same day.

A ready-to-build governance package for Customer Support / CX. Your runtime enforces it; Agent Bob does not run the agent.

Purpose

You want urgent and sensitive tickets in front of the right person fast. This agent reads ticket history and sentiment and routes escalations. A team lead confirms anything routed to executive or legal channels.

It will

  • Read ticket history and sentiment signals; routing write only — no customer contact or case resolution

It won't

  • Auto-resolve escalated tickets, bypass SLA escalation thresholds, share customer sentiment data outside the support team

It asks a person first

  • Immediate escalation to support manager if customer expresses safety concern or regulatory complaint
  • Team lead must confirm any escalation routed to executive or legal channel

Tools

  • Database updates
  • CRM updates
  • Database updates: Change records in a database.
  • CRM updates: Update records in your CRM.

✋ You approve once at the start of each run

Budget defaults

Per task
$0.10
Per month
$30
Actions a day
100

The runtime pauses the agent at a limit. You can change every number in the builder.

Memory and autonomy

Session only. Nothing is kept once the session ends.

ClawMaven policy: session-only — sentiment and interaction history not retained by agent after routing

Acts within limits: low-risk steps on its own, everything gated still stops for a person.

What you get

The 8-file governed package your runtime loads and enforces. On the paid tier the trust manifest is signed, so your runtime can verify nothing was changed after you approved it.

  • HANDOFF.md What your runtime has to enforce, file by file
  • agent-blueprint.json The agent's purpose, tools and settings
  • policy.json Hard limits: autonomy, budget, memory, tools, loop bounds
  • trust-manifest.json The integrity manifest your runtime can verify
  • routing.rules.json Which tools need approval before use
  • run-report-template.json What every run reports back
  • approval-gates.md The moments that must pause for a person
  • deployment-checklist.md What to check before it goes live

This is a governance specification, not a running agent. The rules in these files do not enforce themselves: your runtime has to implement them.

Start from this package

Bob pre-fills the builder with it and drafts the rest. You confirm every step.

Build this packageHave it set up for you