Pricing question
Xuda Tickets
Five ways in.One way through.
Requests arrive from your published forms, your profile contact form, your customer portal, your Public Assistant and your own software. You can also open a ticket yourself. Xuda Tickets files every one of them against a real contact, numbers it, routes it through your topics and workflows, and keeps the whole history on the ticket.
2 people are waiting on you.The longest, Marco, for 2 days.
Needs a first reply
1Your turn
1Login issue
With the customer
2The March invoice charged twice on the same card.
Data import
Watch it work
See it work, start to finish
A film from Xuda's YouTube channel.
01How a desk comes together
Four things to set up. Then it runs itself.
You name your topics, describe in a workflow what should happen for each one, publish a form if you want one, and start answering.
Turn the desk on
Open Tickets from the account menu and pick a tier. Free is the default and costs nothing. The queue replaces the landing page the moment you choose.
Name your topics
Two levels, topic and sub topic, and that is the whole tree. Point each one at the workflow that should run when a request lands under it.
Describe the workflow
One short form: a name, who it hands off to, a deadline measured in your business hours, the message the customer gets, and how far the AI agent may go.
Publish a form and answer
Design the public request page, copy its link and send it out. Submissions arrive already filed under a topic, with the requester saved as a contact.
02One desk, not five inboxes
Requests do not arrive in one place. They should land in one.
Your published forms, your profile contact form, your customer portal, your Public Assistant and your own API calls all land on the same desk in the same shape. You can also open a ticket yourself.
Five entry points, one submit path:
- Your published forms
- Profile contact forms
- Customer portal
- Public Assistant
- API
Contact created · CRM thread mirrored
Every requester is a contact
Before the ticket is written the person is created or matched in your own contact book, deduplicated on their email, and the ticket carries their contact id and the date your relationship started.
03Whose turn
Every ticket says whose turn it is.
One clock runs on each ticket, quiet at first, then amber, then red.
Deadlines that respect your week
Set your business hours and deadlines are counted in working hours only. A four hour deadline taken on a Friday afternoon lands on the next working day, not Friday night.
The queue
The desk tells you who is waiting on you and for how long. Switch between a grid and a board whose lanes follow whose turn it is. Search, then add filters such as status, topic, source, stage, workflow, assignee or overdue: each one becomes a chip in a single Filters menu. Display sets the sort and the columns, and every cell holds one thing, a face and a name, or the number and subject on one line.
- Filter down, then select rows and close them or set a topic in bulk.
- Flip the desk selector to Submitted by me to follow tickets you raised elsewhere.
- A bulk run that half fails tells you how many and why, and keeps your selection so you can retry.
04Answering
One thread, and one box to answer in.
Creation, replies, internal notes, status changes, workflow runs and every system event write a row on the timeline, each with who did it and when. Nothing about a ticket happens off the record.
An AI agent on a short leash
Each workflow can hand the ticket to one of your AI agents. You choose how far it may go: draft an answer for a person to approve, reply to the customer, or reply and mark the ticket resolved. The agent never closes a ticket. Your plan sets the highest level.
Who can see an internal note?
Only your desk. Internal notes are stripped out of every read that is not the desk itself, so they never appear on the requester's view of the ticket, in the API response, or in a webhook payload. They still sit on the same timeline as everything else, which is what makes the handover between two agents readable.
05Topics and workflows
Say what a request is. The desk knows what to do with it.
Topics are two levels deep, no more. Each topic, or each sub topic, points at one workflow, and a workflow is a short form rather than a flowchart. Retriage a ticket to a different topic and the new workflow runs once, not twice.
Billingbilling_triage
- Refund requestbilling_refund
- Invoice questionbilling_triage
Technicaltech_triage
- Login issuetech_urgent
- Data importtech_triage
Salessales_handoff
Each workflow runs the same steps, in this order:
- Hand offThe ticket goes to one person, or to a group of up to 10 in turn, and they get a notification.
- Set the due dateThe deadline is counted forward through working hours only, so it never lands outside them.
- Message the customerYour templated message goes out when the ticket is linked to an account, so nobody wonders whether it arrived.
- Hand off to an AI agentIf the workflow has an AI agent, it runs at the autonomy you chose and stops there, even if your plan once allowed more.
The run is written on the ticket timeline.
Topics, exactly two levels
A topic with no sub topics runs its own workflow. A topic with sub topics runs the sub topic's workflow and falls back to the topic's when the sub topic has none. That is the entire routing model.
Workflows, not flowcharts
A workflow is one short form: a name, who it hands off to, a deadline, a message to the customer and an AI agent. A run is idempotent per workflow and trigger, so correcting a mis-filed topic twice does not notify anyone twice.
06Public request forms
A request page you can send anyone.
Design the form in Ticket settings under Ways in, copy its public link and put it where your customers are. The page is hosted for you. You set the heading, intro, button text, success message and accent color, choose which of Phone, Company, Subject and Reference appear, and add your own questions. If you leave the success message empty, the visitor sees their ticket number.
- Signed token, 2 hour life
- 2 second minimum fill
- 5 per IP per 10 minutes
Public forms you design
Your heading, your intro, your button text, your success message and your accent color. Choose which of Phone, Company, Subject and Reference appear, and add your own questions.
- Name, Email and a fixed "How can we help?" prompt are always on the page. Phone, Company, Subject and Reference are yours to show.
- Scope a form to the topics it may file into, or leave the "Not sure" option on so a visitor never has to guess.
- A success message of your own replaces the default one, which carries the ticket number. A visitor never gets an account id or an internal ticket id.
- No captcha to solve. A hidden honeypot, a signed token that lasts 2 hours, a 2 second minimum fill time and two rate limits (5 per IP per 10 minutes, 200 per form per day) keep the bots out.
07Drive it from your own software
9 methods and 4 events.
Submit, get, list, reply, close, set a stage, assign, read your team and read your topics, all on the account API key you already have. The key is bound to its own desk, so a key can never address anyone else's tickets. Reads work on the free tier, writes need a paid one, and each tier carries its own calls-per-minute ceiling.
- Responses are the narrow external view: no owner ids, no contact ids, no internal automation state.
- Outbound events for created, replied, status changed and closed, over HTTPS only.
- Each delivery is signed HMAC-SHA256 when you set a secret, and abandoned after five seconds, so a slow endpoint never holds up a ticket.
08Four tiers
Start free. Grow the desk, not the tooling.
Every tier is the same product. What moves is how many tickets you can take in a month, how many people work them, how much of the API you can write to, and how far the AI agent is allowed to go.
Free
Default$0 a month
100 tickets a month, then the desk stops rather than billing you
Run a small desk without paying for one.
No card needed
- No card, and Free is the tier every new desk starts on.
- Read your desk over the account API key you already have.
- Agent seats
- 1
- Public forms
- 1
- Topics
- 5
- Workflows
- 3
- API access
- Read only
- API calls a minute
- 10 / min
- Webhooks
- AI agent
- History kept
- 90 days
- Past the allowance
- Stops for the month
Starter
$19 a month
1,000 tickets a month, extra tickets counted
A real desk: write to it from your own software.
- Everything in Free, plus
- Full API access, so your software can submit, reply and close.
- Signed webhooks for created, replied, status changed and closed.
- Closing settings per topic, and the AI agent may draft an answer.
- Agent seats
- 3
- Public forms
- 3
- Topics
- 25
- Workflows
- 15
- API access
- Full
- API calls a minute
- 60 / min
- Webhooks
- AI agent
- Draft
- History kept
- 365 days
- Past the allowance
- Counted
Grow
Unlimited topics$49 a month
10,000 tickets a month, extra tickets counted
A desk with a team behind it and nothing left to ration.
- Everything in Starter, plus
- Topics and workflows stop being counted. Build the whole routing tree.
- The AI agent may reply to the customer, not only draft for you.
- Ten agent seats and twenty published request forms.
- Agent seats
- 10
- Public forms
- 20
- Topics
- Unlimited
- Workflows
- Unlimited
- API access
- Full
- API calls a minute
- 300 / min
- Webhooks
- AI agent
- Reply
- History kept
- 1,095 days
- Past the allowance
- Counted
Scale
$149 a month
100,000 tickets a month, extra tickets counted
A desk at volume, with the longest memory.
- Everything in Grow, plus
- Unlimited agent seats and unlimited published forms.
- The AI agent may reply and mark a ticket resolved. It never closes a ticket.
- Nothing ages out of the queue.
- Agent seats
- Unlimited
- Public forms
- Unlimited
- Topics
- Unlimited
- Workflows
- Unlimited
- API access
- Full
- API calls a minute
- 1,200 / min
- Webhooks
- AI agent
- Resolve
- History kept
- Unlimited
- Past the allowance
- Counted
Free is the default and needs no card: past its allowance it stops taking tickets, while paid tiers keep accepting and count the extra. A paid tier is added to the one Xuda subscription your account already has, and a downgrade that would strand more forms, topics, workflows or seats than the lower tier holds is refused up front with the number you need to remove. Two flags the paid plans carry are not delivered yet either: SLA breach tracking never fires on your own desk, and every form link is still on a Xuda domain rather than one of yours.
09Tickets vs the usual setup
What a shared mailbox never gives you.
Most teams answer requests from a mailbox everyone can see, a form builder that emails the results, or a standalone helpdesk bolted on beside the CRM. Here is what changes when the desk is part of the platform your contacts already live in.
| Xuda Tickets | A shared mailbox | Form builder plus email | Standalone helpdesk | |
|---|---|---|---|---|
| Every request gets a number people can quote | ||||
| Requester saved as a contact automatically | Extra sync | |||
| Whole thread mirrored into your CRM | Extra sync | |||
| Timeline of every change, human and system | ||||
| Two-level topics that route the work | Labels only | |||
| Deadlines counted in your business hours | ||||
| Hosted request page you design | ||||
| Bot defence with nothing for the visitor to solve | Captcha | Captcha | ||
| Internal notes hidden from the customer | ||||
| Signed outbound webhooks | Varies | |||
| Runs on the API key your account already has | Separate key | |||
| Sits beside the rest of your account |
Common questions
The things worth checking before you switch.
Turn on the desk. Send the link. Start answering.
Name your topics, describe what should happen for each one, publish a form and put its link where your customers are. Every request that arrives gets a number, a contact record, a topic, an owner and a history you can read end to end.
