catalog
Catalog v1
Twelve launch-quality workflows across six categories. Every YAML public.
§ roadmap
The board is the calendar.
Three columns: shipped, in harness, researching. Live workflows from the catalog auto-feed the first column; forthcoming workflows auto-feed the second. No dates, no quarters — the cadence after October 2026 is daily, and the column is what the schedule is.
Shipped
[17]Live in the catalog or in production. Public YAML, harnessed runtime.
- preview
Live Preview
Deterministic, in-browser, no account. Runs every workflow against scripted turns.
- runtime
MCP URL provisioning
One URL per workflow, scope-locked, rotatable. Configs for Claude Desktop, ChatGPT, Cursor.
- instrumentation
Instrumentation rail
Step-level visibility for every run — confidence floors, escalation reasons, transitions.
- Triage
Intent classification intake
Classifies an inbound message into one of six intents and routes to the matching downstream workflow.
- Triage
Ambiguous message disambiguation
Asks one targeted question when the inbound message is too vague to route, then re-routes with the answer.
- Triage
Duplicate ticket detection
Confirms whether an inbound message is a duplicate of an existing open ticket and merges or splits accordingly.
- Billing
Refund request intake
Collects structured refund-request information and produces a handoff packet for human review.
- Billing
Invoice clarification
Walks the customer through a specific invoice line by line and answers questions grounded in the line items provided.
- Billing
Subscription cancellation
Handles cancellation intake, captures the reason, and confirms the effective date — without retention pressure.
- Product
Structured bug-report intake
Walks the customer through reproducing a bug and produces a clean, engineer-readable report.
- Product
Known-issue lookup
Confirms whether a customer's report matches a known open issue and sets expectations on a fix.
- Product
Feature discovery
Helps the customer find the existing feature that solves their problem, grounded in the product docs you supply.
- Escalation
Human handoff with context
Closes the AI conversation cleanly and produces the structured packet a human agent needs to pick up.
- Escalation
Tier-2 engineering escalation
Confirms the issue is engineer-grade, collects the technical context, and writes the escalation note.
- Post-resolution
Resolution confirmation
Asks the customer to confirm whether the issue is resolved and captures a one-line outcome.
- Compliance
Off-topic deflection
Recognizes off-topic messages and declines politely without engaging with the off-topic content.
In harness
[36]Authored, schema-checked, and queued for daily release after launch.
- instrumentation
Run history export (JSONL)
Pull the 90-day rolling history into the analytics stack your client already has.
- runtime
BYO model keys
Anthropic and OpenAI first. Pay your provider directly; retention halved when keys are yours.
- Triage
Language detection and routing
Detects message language and routes to the matching localized workflow.
- Triage
Priority tier assignment
Assigns P1–P4 based on customer-stated urgency and message signals.
- Triage
VIP customer fast-lane
Routes flagged customer accounts directly to a senior queue with structured context.
- Triage
Off-hours acknowledgment
Sends a single-turn acknowledgment with next-business-hour context when the queue is closed.
- Billing
Payment failure recovery
Walks customer through updating a failed payment method.
- Billing
Plan change confirmation
Confirms an upgrade or downgrade and sets expectations on prorated billing.
- Billing
Account ownership transfer
Captures the structured information required to transfer an account to a new owner.
- Billing
Tax-document request
Confirms what document the customer needs and routes to billing.
- Billing
Pricing question, grounded
Answers pricing questions strictly from the published pricing page.
- Product
Configuration walkthrough
Step-by-step setup guidance grounded in your client's documentation.
- Product
Integration troubleshooting
Targeted intake for failures at the boundary of two systems.
- Product
Onboarding stuck-point
Identifies where in onboarding the customer is stuck and produces a structured handoff.
- Product
Data-export request
Captures the scope and format the customer needs.
- Product
Browser and environment check
Collects browser, OS, and extension information for diagnostic handoff.
- Product
Performance issue intake
Structured collection of performance complaints with timestamps and scope.
- Escalation
Manager escalation
Captures the reason for manager-level attention with structured grounding.
- Escalation
Outage coordination handoff
Routes incident-related messages into the active incident channel with context.
- Escalation
Legal-notice acknowledgment
Recognizes legal-affecting language and stops AI handling immediately.
- Escalation
Press or PR routing
Detects press inquiries and routes to the communications inbox.
- Escalation
Expired-context recovery
Recovers gracefully when prior context has been lost between turns.
- Escalation
Low-confidence checkpoint
Pauses and confirms with the customer when model confidence drops below threshold.
- Post-resolution
CSAT collection
Collects a numeric satisfaction score with a single optional comment.
- Post-resolution
Ticket summary for archive
Produces the structured summary your client's archive expects.
- Post-resolution
Follow-up after fix
Confirms a fix held N days after the reported resolution.
- Post-resolution
Thank-you acknowledgment
Closes a conversation gracefully when the customer has thanked the team.
- Post-resolution
Lessons-learned extraction
Extracts a structured lesson from a notable ticket for the operator's records.
- Post-resolution
Reopened-ticket handling
Picks up a reopened ticket cleanly with prior context as input.
- Compliance
Abusive-language handling
Names the line, sets the consequence, hands off if it continues.
- Compliance
Suspected-minor handoff
Recognizes signals of a minor user and escalates immediately.
- Compliance
Self-harm language protocol
Recognizes safety-critical language and follows a published protocol.
- Compliance
GDPR deletion request
Captures the structured deletion request your client's privacy team needs.
- Compliance
Data-access request
Captures the structured access request with verification questions.
- Compliance
Regulated-vertical disclaimer
Inserts the required disclaimer in regulated industries before continuing.
- Compliance
Third-party impersonation check
Recognizes attempts to impersonate the operator or vendor.
Researching
[6]Open questions worth answering. No commitment, no date — just on the page.
- tooling
Public CLI
Let practitioners pin workflow versions in a config file and audit drift between runs.
- catalog
Workflow versioning and migration
Track YAML changes and surface breaking changes to subscribers before they ship.
- instrumentation
Per-client telemetry export
Pipe run logs into the BI tool the client already runs (Snowflake, BigQuery, ClickHouse).
- runtime
EU-region runtime
Single-region deployment for practices required to keep data inside the EU.
- personalization
Personalization preview harness
Let buyers preview the tuned variant against scripted turns before the commission ships.
- harness
Workflow composition primitives
Declarative chaining so a routing workflow can hand off into a downstream one with one config edit.
If something on the Researching column matters to your practice, email diego@agora.*with the shape of how you’d use it. Items move from Researching to In harness when someone takes the time to write that email.