Customer Support and Voice AI
AI receptionist for small business: calls, bookings and handoffs
What an AI receptionist does on a real call, the rules that apply, a sample greeting and a pass/fail checklist to launch one safely.
Support Operations
AI Ticket Routing
Every ticket sent straight to the right queue and agent, based on what it actually says, not a static rule.
Static routing rules break as soon as a customer describes a problem in their own words. This workflow reads each incoming ticket and sends it to the team or agent best placed to handle it, matching the content against the queues, skills and workload rules you define. Tickets it is unsure about go to a default queue, and every assignment is logged with a reason.
- Tickets sent to the right team based on what they say
- Assignments matched to your queues, skills and workload rules
- A routing log explains why each ticket went where it did
$2,400
20–30 working days
Optional maintenance $249/mo
What it is
AI Ticket Routing reads each incoming ticket and sends it to the team or agent best placed to handle it, matching content against the queues, skills and workload rules you define. It works quietly in the background, with no customer-facing channel. Every assignment is logged with the reason it was made.
Why businesses buy it
Misrouted tickets are a hidden cost: each one waits in the wrong queue, gets passed along, and reaches the right person late and with an irritated customer behind it. Someone usually ends up triaging by hand. After launch, tickets land with the right team on the first try, and leads can see exactly why each one was assigned. The Scope Card fixes the queues, skills and fallback rules in writing before you order, so routing follows your structure rather than guesswork.
Problems this solves
Tickets sit in a shared queue until someone claims them
Each incoming ticket is read and sent to the team or agent best placed to handle it. Assignment happens in the background as soon as the ticket arrives.
Specialist tickets reach generalists and get passed around
Routing matches the ticket's content against the queues, skills and workload rules you define. Technical, billing or language-specific tickets go where the right skills are.
Nobody can explain why a ticket went to a certain person
Every assignment is logged with the reason it was made. Team leads can review decisions and adjust the rules where routing does not suit them.
A good fit if
Tickets get misrouted often enough that agents spend real time reassigning them before they can even start work.
Your routing today depends on a handful of brittle keyword rules that break whenever customers phrase things differently.
You have distinct teams or skill groups, such as billing, technical or account management, and want tickets landing with the right one first time.
You want routing decisions logged, so you can see where volume is actually going and adjust the rules over time.
Not the right fit if
Your tickets are not tagged consistently to begin with, so routing has nothing reliable to work from. See AI Ticket Classification, which we recommend pairing with this build.
Your real gap is catching tickets that need escalating upward, not sideways to another queue. See AI Escalation Agent.
You need a customer-facing agent that answers questions directly rather than just moving tickets between queues. See AI Helpdesk Agent.
Your routing logic spans more than three connected systems or unusually complex skill-matching rules. Talk to us through our Custom AI enquiry form.
How it works
- A ticket arrives in your helpdesk through your existing channels, with nothing different from the customer's side.
- The agent reads the content and matches it against the queues and skill groups you defined, not a fixed keyword list.
- It checks current workload or availability where you connect that data, so tickets are not routed into an already overloaded queue.
- It applies the assignment and, where your helpdesk supports it, writes a short note explaining why that queue or agent was chosen.
- Tickets that do not clearly match any defined queue are flagged for a person to route manually, rather than guessed.
- Every routing decision is logged, so misroutes are easy to spot and the rules can be tuned over time.
What you provide within 72 hours
Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.
- A list of the systems involved, with admin or API access to each one.
- A written description, or a short screen recording, of how tickets are routed manually today.
- Your queues or skill groups, and the rules for which ticket type goes where.
- Five to ten real sample tickets that show your typical routing decisions.
- Admin access and API keys for every connected system, shared by adding our team as a user or creating a key you control, never by email.
- Your business information (company basics, hours and brand voice), shared during intake.
- One decision-maker who can confirm scope questions during the build.
- An API key for your own AI model account (for example OpenAI or Google Gemini), created for this build with a spending limit.
The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.
Timeline
Start
Intake reviewed, queues and routing rules confirmed.
Weeks 1–2
Routing logic and skill-matching workflow built.
Week 3
Helpdesk and team-data systems connected and tested.
Weeks 3–4
Twenty test runs on your sample data, with results sent to you.
Week 4
Your review, plus two rounds of requested changes.
Go-live
Live routing new tickets, recorded handoff session, support begins.
| Option | Delivery time | Price |
|---|---|---|
| Standard | 20–30 working days | $2,400 |
| Express | 15–25 working days | $2,900 |
| Rush | 10–20 working days | $3,350 |
What you receive at handover
- The routing workflow running in the background, with no customer-facing channel
- One workflow of up to twelve steps with an AI decision step, set to your queues, skills and workload rules
- Connections to up to three of your systems
- Test report from 20 test runs on your sample data
- Admin guide, recorded 45-minute handoff session and 30 days of post-launch support
Expected benefits and how to measure them
- Tickets can reach the right person without waiting in a shared queue.
- Helps spread work more evenly across your team.
- A reason log makes routing easy to review and adjust.
- Time to assignment
- Measure time from ticket creation to first assignment in your helpdesk. Compare four weeks before and after launch.
- Reassignments per ticket
- Count tickets that change owner more than once. Compare the month before and after launch.
- Workload balance
- Compare open tickets per agent at the end of each week, before and after launch.
Before you start: Record a month of time-to-assignment, reassignment counts and open tickets per agent from your helpdesk.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
Running costs
The build price is one-time. Running AI Ticket Routing costs roughly $20 to $100 a month, covering the automation platform and AI model usage together. Ticket volume and the number of queues both influence where in that range you land.
AI usage during the build and afterwards runs through your own accounts, so the cost and the provider relationship both stay visible.
Ask about running costsCustom requirements
If your routing spans more than three connected systems, more than twelve workflow steps, or skill-matching rules this Scope Card does not cover, add a note at checkout for a written Change Quote. Larger or bespoke projects go through the Custom AI request form instead.
Request a custom versionKeep it running
Monthly maintenance covers monitoring, fixes, model and platform updates, a monthly health report and change hours for work such as a new queue or an adjusted skill rule. It starts after the post-launch support period, bills monthly and can be cancelled any month.
$249/mo (the minimum fee, includes 2 change hours)
Optional. Starts after the post-launch support period. Cancel any month.
How maintenance worksHow this compares
| Do it yourself with a SaaS tool | Hire a custom agency | Upmark Labs | |
|---|---|---|---|
| Price | A helpdesk routing add-on bills per seat or per automation rule | A custom agency quotes after discovery calls | Ours is one fixed price, shown on this page before you buy |
| Scope | A generic rules engine needs every queue and condition configured by hand | An agency agrees scope during the project | Ours is written on the Scope Card before purchase |
| Delivery | A routing add-on can connect in days but the matching logic still needs building | An agency build usually takes several weeks, set per project | Ours has a fixed delivery time shown before you buy, with faster options |
| Matching quality | Keyword-only rules misroute as soon as customers phrase things differently | An agency build depends on what was agreed | Ours matches on actual content and, where connected, current workload |
Questions about this product
Does AI Ticket Routing replace our helpdesk's built-in routing rules?
It works alongside them. Most helpdesks route on simple conditions like a form field; this build reads the actual ticket content and, where you connect workload data, current team capacity, then writes the assignment back using your helpdesk's own routing or assignment fields. Nothing about your existing setup is removed.
What does AI Ticket Routing cost to run each month?
Roughly $20 to $100 a month, covering the automation platform and AI model usage together. Ticket volume and the number of queues you route between both affect where in that range you land. You pay these providers directly, with no separate per-ticket fee charged by us.
How long does AI Ticket Routing take to launch?
The delivery time is fixed and shown on this page before you order, and express or rush delivery can bring the launch forward if you need it sooner. All three include the same twenty test runs against your own sample data before the workflow starts routing live tickets.
What access does AI Ticket Routing need?
Admin or API access to your helpdesk, and to whatever system holds your team or skill definitions, up to three connected systems in total. Sandbox or test records work for the build itself. Every credential is shared by adding our team as a user or creating a key you control, never by email, and can be revoked at any time.
Can AI Ticket Routing account for who is available right now?
Yes, where you connect a system that tracks workload or availability, such as your helpdesk's own assignment data. Without that connection, it routes purely on content and the queue rules you defined. Either way, tickets that do not clearly match a queue are flagged for a person.
Can I add a new queue or skill group after launch?
Yes, through monthly maintenance. Its change hours usually cover adding a queue or adjusting a skill rule. The hours scale with the build, and heavier tuning goes through a Change Quote first. Tell us which ticket types should go to the new queue, and we update the routing rules. Maintenance can be cancelled any month.
Should I order AI Ticket Routing on its own or with AI Ticket Classification?
Either works, but routing is more accurate when tickets are already tagged consistently. AI Ticket Classification produces those tags, and this build reads them to route. Ordering both together gives you one connected pipeline, and each remains its own focused, fixed-price workflow with a separate Scope Card.
Guides on this topic
All guides Get every ticket to the right desk on the first try.
Order AI Ticket Routing and every ticket reaches the right team on the first try, with a clear record of why it was sent there.
Works well with
Support Operations
AI Ticket Routing for Salesforce Service Cloud
Routes tickets to the right team or agent based on content and skills, connected natively to Salesforce Service Cloud so it reads…
Support Operations
AI Ticket Routing for HubSpot Service Hub
Routes tickets to the right team or agent based on content and skills, connected natively to HubSpot Service Hub so it reads…
Support Operations
AI Ticket Routing for Intercom
Routes tickets to the right team or agent based on content and skills, connected natively to Intercom so it reads incoming conversations…