Start with a Marketplace template
The Marketplace ships pre-built Agents you can clone in one click. Adapt them to your products, your tone of voice, your escalation rules. Or build a custom Agent from scratch.Customer Query Handler
Answers customer questions from your knowledge base — useful for first-response drafts and self-serve flows.
Customer Support Categorization
Classifies tickets into billing / technical / account / feature / bug and assigns P1–P4 priority on the way in.
Browse the Marketplace
The full catalog of Agents — ticket triage, response drafting, KB management, escalation routing.
Pick your path
How hands-on do you want to be? Pick a tab — the rest of the page is written for you.- No build
- Build visually
- Build with AI
You don’t need to touch the builder. Open the cloned Agent above, ask in plain English, and let it work across the systems it’s connected to.
Sharpen the answers with knowledge
Upload your support playbook, tone-of-voice doc, escalation rules, and knowledge base articles. Every conversation references them — sharper output, no new setup.Add knowledge
Upload context once. Every conversation references it.
Make it run on its own
When the same kinds of tickets keep landing, set a trigger — every billing question gets first-touch drafted, every refund request gets routed to the right team. One toggle, no code, no builder.Triggers
Schedule runs, fire on ticket events, listen to webhooks.
Ready to go further?
When prompting and templates stop being enough — when you want the Agent to follow your playbook word for word and orchestrate triage across channels — pick the Build visually tab above.The four levels in support
How the autonomy ladder plays out across the support queue:L1 — Assisted
An agent opens a ticket and asks the Agent to summarize the customer’s history and suggest a reply — the Agent returns context with a draft response.
L2 — Copilot
An agent reviews a batch of new tickets — the Agent has already drafted replies and triage suggestions, the agent approves and sends.
L3 — Autopilot
A new ticket lands → triaged, tagged, routed, first-reply drafted and auto-sent on simple cases, all without an agent touching the queue.
L4 — Self-driving
You set the objective — “cut time-to-first-response” — and the Workforce triages, drafts, and routes, with its triage and template criteria tuned through evals as CSAT outcomes flow back.
Zoom into a single use case
Each use case below is a working entry point — clone a template, then run it, shape it visually, or build with AI depending on which tab fit you.Ticket triage and routing
Classify, tag, and route every inbound ticket so the right agent picks it up first.
Response drafting from KB
First-draft replies grounded in your knowledge base, with citations so the agent can spot-check.
KB article generation
Turn resolved tickets into knowledge base articles — close the loop without writing them by hand.