Install
openclaw skills install @ruti3/inbound-call-triage-briefTriage inbound calls to an AI agent line — classify caller intent, screening questions, escalate-vs-handle rules, message-taking script, and spam signals before the agent picks up.
openclaw skills install @ruti3/inbound-call-triage-briefProduce an inbound triage brief when a call arrives (or is expected) on an AI agent phone line — PollyReach, Agent Phone Call, OpenPhone, Twilio, etc. Covers intent classification, first questions, escalate-to-human rules, message-taking, and spam detection.
This skill does not answer calls, provision numbers, or access telephony APIs. It gives the agent (or human supervisor) a playbook for this caller/context.
Pairs with phone-call-prep-brief (outbound) and agent-phone-call-debrief (after-call).
Use when:
Do not collect passwords, OTP codes, full card numbers, or SSNs — even if callers offer them.
Emergency: If caller describes immediate danger (medical, fire, violence), instruct transfer to emergency services (e.g. 911) — do not attempt AI-only handling.
Harassment/spam: Document disengage script; do not engage debate.
Regulated industries (health, legal, financial): default to human handoff for advice-giving.
Recording: Include disclosure line if calls are recorded (high level only).
Adapt to line purpose; pick 3–6:
| Intent | Typical handle |
|---|---|
| Booking / scheduling | Agent collects slots → confirm |
| Order / account status | Verify identity lightly → lookup or escalate |
| Support issue | Troubleshoot tier-1 → escalate if unresolved |
| Sales inquiry | Qualify → book or escalate |
| Wrong number / spam | Polite disengage |
| VIP / urgent | Fast-track human |
| Field | Value |
|---|---|
| Line purpose | … |
| After-hours | … |
| Human backup | … |
| Recording disclosure | yes/no + one-liner |
What the agent says when answering (friendly, states who they represent, sets expectation).
| Intent | First questions | Agent can resolve? | Escalate when |
|---|---|---|---|
| … | … | yes / partial / no | … |
Numbered list, minimal PII.
If taking a message: fields to capture + read-back script.
Behaviors that trigger short disengage (silent line, obvious pitch, repeated hang-up).
Bullets (e.g. process payments, give medical advice, promise refunds without policy).
Good opening: “Thanks for calling Acme Support — I’m the automated assistant. I can help with order status or scheduling a callback. What are you calling about today?”
Bad opening: “Hello, how can I help?” (no context, no boundaries)
Good escalate trigger: “Caller requests chargeback over $500 or mentions attorney.”
Bad escalate trigger: “If the caller is angry.” (too vague)