Build a support team
In this guide, you’ll build a support team of three employees. Triage reads every new Zendesk ticket and hands it to the right specialist: Billing agent for invoices and refunds, Tech agent for product issues. Anything they can’t solve goes to a human. Once Triage has proven itself, you make it the team’s manager employee. Setup takes about 30 minutes.
Before you start
Section titled “Before you start”- The Builder role or above. You also need an Admin to connect Zendesk and Stripe, create the refund policy and, later, grant L4 Delegate.
- The Business or Enterprise plan, if you want Triage to become a manager employee at L4. See Billing.
- A Zendesk account where you can authorize apps.
- A Stripe account, if you want the Billing agent to issue refunds.
- Your help center articles and internal support macros, to use as a knowledge base.
- A group of human agents in Zendesk, such as
Tier 2, to receive escalations.
Build the team
Section titled “Build the team”Connect Zendesk and Stripe
An Admin goes to Settings > Capabilities > Connectors, searches for Zendesk and chooses the Workspace credential mode, ideally with a service account. Grant Read and Write scopes on tickets, users and macros. Repeat for Stripe with scopes on charges and refunds.
Both connectors are now available to any employee you create.
Create the team
In the sidebar, click Teams, then New team:
| Field | Value |
|---|---|
| Name | Support |
| Goal | Resolve customer tickets quickly and correctly. |
| Team owner | Your support manager |
| Knowledge base | Click Add and upload your help center export and macros |
Click Create team. The knowledge base is shared by every employee in the team.
Add the three employees
On the Support team page, click Add employee three times. Start from the marketplace templates listed, or from Blank employee:
| Name | Template | Role in team | Tools | Autonomy level |
|---|---|---|---|---|
Triage |
Support Triage | Member | Zendesk: read, tag | L2 Act within limits |
Billing agent |
Billing Support | Member | Zendesk, Stripe | L1 Approve |
Tech agent |
Technical Support | Member | Zendesk, web search | L1 Approve |
Set the same human manager for all three, usually your support manager.
Route new tickets to Triage
Open Triage, go to Triggers and click Add trigger. Choose Business event, then Zendesk: ticket created. Leave Filter empty to receive every ticket.
Each new ticket now creates a task for Triage.
Define the hand-offs
On the Support team page, open Routing and add one rule per specialist:
| When the ticket is about… | Hand off to |
|---|---|
| Invoices, payments, refunds, plans | Billing agent |
| Bugs, errors, setup, integrations | Tech agent |
| Anything else, or confidence below 70% | Human: Zendesk group Tier 2 |
Triage reads the ticket, tags it, picks a rule and hands the whole ticket off to the specialist, with a short summary and a link to the original run. For the last rule, it hands the ticket to a human: the Tier 2 group gets an item in its Orqane inbox and the ticket is assigned to it in Zendesk.
Allow small refunds with a policy
Go to Settings > Policies and click New policy:
| Field | Value |
|---|---|
| Name | Refunds under 50 USD |
| Applies to | Team Support |
| Action | Stripe: create refund |
| Rule | Allow if amount ≤ 50 USD and the charge is less than 30 days old |
| Otherwise | Require approval from the Finance group |
Then open Billing agent > Autonomy and set Records changed per run to 1. Once Billing agent reaches L2, it refunds small amounts on its own. Larger refunds always go to Finance, whatever its level.
Set escalation to humans
On each specialist’s profile, open Escalation and fill in:
| Field | Value |
|---|---|
| Escalate to | Zendesk group Tier 2 |
| When | Customer asks for a human, negative sentiment twice, no answer found in knowledge |
| Hand-off note | Summary, steps tried, suggested next action |
The employee assigns the ticket to the group, posts an internal note and stops working on it.
Test with a real ticket
Create a test ticket in Zendesk, such as I was charged twice this month. In Orqane, open Activity and watch Triage tag it and hand it to Billing agent. Billing agent drafts a reply and a refund, then waits in Approvals for you.
You’ve built a support team that triages every ticket, answers within your rules, refunds within policy and hands the hard cases to your human agents.
What to watch in the first weeks
Section titled “What to watch in the first weeks”- Teams > Support > Overview shows tickets handled, hand-offs, escalation rate and average resolution time.
- Approvals shows how often you change the specialists’ replies. Fewer changes mean they’re ready for L2.
- Costs breaks down spend by employee, so you can compare the cost per ticket with your human baseline.
Make Triage the manager employee
Section titled “Make Triage the manager employee”Some tickets mix several issues, such as a bug report that also asks for a refund. To let Triage split them, make it the team’s manager employee. A manager employee creates sub-tasks for its teammates, which is a Delegate action, so it must be at L4 Delegate.
- Wait for Triage’s probation to end and check its performance review: routing accuracy, escalation rate, no critical incident.
- An Admin opens Triage’s profile, clicks Change level, chooses L4 Delegate and enters a reason.
- On the Support team page, open Settings and set Manager employee to
Triage.
Leave Triage’s wallet off: it hands work to its team, it doesn’t buy services. Each sub-task still runs under the level, policies and budget of the specialist that receives it.