Automatic assignment
Rules assign to a person, a team or by a criterion. Unassigned requests stand out immediately.
Organise the queue and keep priorities, assignments and deadlines in view. Your team can find conversations and customer details in the ticket and follow the case through to resolution.
Without a structured process
Without shared ownership, visible SLAs and a complete history, important requests get lost among new messages and hand-offs.
The risk
With no stated priorities, the most recent notification sets the order. Important requests sink, and whoever chases twice gets ahead of whoever waited quietly.
The risk
A response commitment written into a contract counts for little if nobody watches the time run while the ticket is open. A month-end report tells you who breached; it does not prevent the breach.
The risk
The ticket changes hands and the unwritten part — what had already been tried, what the customer said on the phone — stays in the head of whoever had it before.
Ticket lifecycle
Always the same five, whatever the incoming channel. What separates two teams is how much of this path is automatic and how much stays manual.
The message becomes a ticket with its channel, contact and content. The timers start counting from here.
Priority, topic, tags and custom fields. Rules can set them automatically; AI can suggest them.
To a person or team, by rule or by hand. A name appears beside the ticket, visible from the queue.
Customer replies, internal notes, attachments and watchers. Statuses show how far the work has progressed.
The ticket closes, timers stop, and everything stays in the contact history and dashboard data.
SLAs
Set separate targets for first response, subsequent replies and resolution. Your team can see deadlines and act on tickets that need attention.
What keeps the queue in order
A growing backlog rarely comes down to volume. It comes down to how many tickets sit there with no name, no priority, or no reason to still be open.
Rules assign to a person, a team or by a criterion. Unassigned requests stand out immediately.
Order number, serial number, problem type: the fields you need, as rule conditions and view filters.
Team discussions stay in the ticket and remain hidden from the customer: the context often lost during hand-offs.
People who need updates can follow the ticket without owning it: sales stays informed without joining the queue.
Every rule run is recorded with its outcome: read the log instead of guessing.
Classification, suggested priorities and drafts remain proposals on the ticket: the operator accepts, edits or ignores them.
Frequently asked questions
The warning fires, and you decide when it fires. It reaches you while there is still room to act: from there the ticket can be reassigned, raised in priority or escalated. What the system does not do is resolve it for you.
Yes. Alongside the standard statuses you define custom ones using the words your team already uses. They also work as automation triggers: a change of custom status can fire a rule.
Uppo Assist prepares classifications and drafts for an operator to review and send. AI Agent can reply autonomously using configured sources and rules, handing the case to your team when needed. A verified autonomous resolution uses 3 credits.
The warning fires at the time you choose. While there is still time to act, you can reassign the ticket, raise its priority or escalate it.
No, provided you have configured business hours and holidays. The clocks only count inside your opening hours: a ticket arriving on Friday evening does not consume the weekend.
Yes. Time does not run in waiting states: while a detail, an attachment or a confirmation is missing the ticket accrues no delay, and the clock restarts when the customer replies.
Yes. Rules assign to a person, to a team or by a criterion, and can use the channel, ticket fields, contact data and customer company data as conditions. Every run stays in the log with its outcome: when a ticket ends up in the wrong place you read the log instead of guessing.
No. SLAs and automations are available from Starter. Custom rules are limited to 10 with Starter, 20 with Growth and 100 with Scale; Enterprise offers scalable capacity. See the plan comparison for archived ticket retention limits.
The time between the request arriving and the first human reply going back. This is what the customer experiences as "they have picked it up", and it is almost always what support gets judged on.
The time between a customer message and your next reply, for the whole length of the conversation. It exists to prevent the classic case: a lightning first reply, then two days of silence.
The time from opening to closing. This is the one that matters for contractual commitments, and it should be read alongside the other two, not instead of them.
Four rules — and this is where two helpdesks with the same number in the contract produce different results.
SLAs are included from the Starter plan. Start with commitments you know you can meet and tighten them after a month of real numbers, once the dashboards show where you actually stand.
There is one rule and it has no exceptions: AI proposes, the operator confirms. A ticket does not change status and a reply does not go out unless a person sends it.
Classification, a suggested priority, draft replies built from your knowledge base. They stay visible on the ticket as proposals: whoever is working accepts, edits or ignores them.
Uppo Assist is enabled as a monthly licence for the operators who use it and interactive work does not use credits. AI Agent uses 3 credits only for a verified autonomous resolution.
Where the hours go before the first reply, which rules are worth writing first, and how self-service takes tickets out of the queue.
Where the hours actually go between a request arriving and the first useful reply.
Read the guideThe rules worth writing first, and the ones better left alone.
Read the guideHow to write the content that takes tickets out of the queue instead of adding to it.
Read the guideEvent, conditions, actions: how a rule is written, what it can do and how to read the log.
Read the automations pageWhat changes between a shared mailbox and a helpdesk, and the six questions to put to a vendor.
Go to helpdesk softwareHow many automations, how many agents and what retention each plan includes.
Compare plans and pricingTell us how you handle requests today: we’ll show you how to configure priorities, assignments and service targets.