Ticket management

Every request has a priority, an owner and a deadline

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.

  • Deadlines for first response, subsequent replies and resolution
  • Assignments and statuses visible from the queue
  • An automation log for every rule run
Every request has a priority, an owner and a deadline

Without a structured process

When notifications set the agenda instead of priorities

Without shared ownership, visible SLAs and a complete history, important requests get lost among new messages and hand-offs.

The risk

The queue gets worked newest first

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

Deadlines are discovered once they have passed

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

Hand-offs lose pieces

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

The ticket lifecycle, in five steps

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.

  1. 01

    Arrival

    The message becomes a ticket with its channel, contact and content. The timers start counting from here.

  2. 02

    Classification

    Priority, topic, tags and custom fields. Rules can set them automatically; AI can suggest them.

  3. 03

    Assignment

    To a person or team, by rule or by hand. A name appears beside the ticket, visible from the queue.

  4. 04

    Working it

    Customer replies, internal notes, attachments and watchers. Statuses show how far the work has progressed.

  5. 05

    Resolution and closing

    The ticket closes, timers stop, and everything stays in the contact history and dashboard data.

Three clocks on every ticket

SLAs

Three clocks on every ticket

Set separate targets for first response, subsequent replies and resolution. Your team can see deadlines and act on tickets that need attention.

  • They count during your business hours: a ticket received at 7 pm does not run overnight
  • Holidays are excluded from the calculation
  • They pause in waiting states while you wait for the customer
  • They warn before the deadline, leaving time for escalation

What keeps the queue in order

The parts that stop the backlog growing on its own

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.

Automatic assignment

Rules assign to a person, a team or by a criterion. Unassigned requests stand out immediately.

Tags and custom fields

Order number, serial number, problem type: the fields you need, as rule conditions and view filters.

Internal notes

Team discussions stay in the ticket and remain hidden from the customer: the context often lost during hand-offs.

Watchers

People who need updates can follow the ticket without owning it: sales stays informed without joining the queue.

Automation log

Every rule run is recorded with its outcome: read the log instead of guessing.

AI prepares the work; you decide

Classification, suggested priorities and drafts remain proposals on the ticket: the operator accepts, edits or ignores them.

Frequently asked questions

Questions about SLAs and automation

More questions
What happens when a ticket is about to breach its SLA?

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.

Can I use my own statuses instead of yours?

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.

Can AI close or answer tickets on its own?

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.

Can’t find an answer? Contact the team
What happens when a ticket is about to breach its SLA?

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.

Do SLAs count nights and days you are closed?

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.

Does the clock stop while I am waiting on the customer?

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.

Can assignment be automatic?

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.

Do I need a higher plan to get SLAs and automations?

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.

AI and related resources

The ticket lifecycle, in five steps

It is worth automating steps 02 and 03 and leaving 04 by hand: rules are good at routing and much worse at recognising an exception.

Arrival
The message becomes a ticket carrying its channel, contact and content. From here the clocks start counting.
Classification
Priority, topic, tags and custom fields. Rules can set them on their own; AI can propose them, and an operator confirms.
Assignment
To a person or a team, by rule or by hand. From that moment there is a name next to the ticket, visible from the queue.
Working it
Replies to the customer, internal notes for the team, attachments and watchers. Statuses say where the work has got to, including waiting on a reply.
Resolution and closing
The ticket closes, the clocks stop, and everything stays in the contact's history and in the dashboard numbers.

The parts that stop the backlog growing on its own

Automatic assignment
Rules assign to a person, to a team, or by a criterion. Whatever stays unassigned stands out immediately, because it is the exception rather than the norm.
Priorities and custom statuses
Beyond the standard statuses you can define your own, using the words your team already uses. A status that genuinely describes the situation is what makes a queue readable at a glance.
Tags and custom fields
Order number, serial number, problem type: the fields you need, available as conditions in rules and as filters in views.
Internal notes
What the team says to each other stays in the ticket and the customer never sees it. This is the part that usually gets lost in hand-offs.
Watchers
People who need to be kept informed but not to reply can follow a ticket without owning it. Sales stays up to date without joining the queue.
Automation log
Every rule run is recorded with its outcome. When a ticket ends up in the wrong place you read the log instead of guessing.
How they count time
  • First response

    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.

  • Next response

    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.

  • Resolution

    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.

They count inside your business hours
Hours are configurable. A ticket arriving at seven in the evening does not burn through the night: the clock resumes when you open, as a person would.
Holidays are excluded
Your closure calendar is part of the calculation. A bank holiday does not count as delay, and nobody has to explain it by hand in the report.
They pause in waiting states
In configured waiting states, the timer pauses while you await information or confirmation from the customer. It resumes when handling continues.
They warn before they expire
The warning threshold is configurable: you are told while there is still room to act, not afterwards. That is the difference between a useful escalation and an observation.

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.

AI prepares the work; you decide

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.

Suggestions to review before sending

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 for operators, usage-based AI Agent

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.

Give your team a clear queue to work from

Tell us how you handle requests today: we’ll show you how to configure priorities, assignments and service targets.