Less repetitive work. More attention to customers.

Assign tickets, update priorities, send notifications and connect your own systems with visual rules built on customer service events.

  • Ready-to-use rules included with your account
  • Visual editor: no code required
  • HTTP calls to your business systems and CRM
Less repetitive work. More attention to customers.

What changes

Reduce manual work on every ticket

Automate assignments, priorities, updates and communications so your team can focus on resolution.

Every request goes straight to the right place

Channel, content, customer, priority and custom fields decide who picks the ticket up, before anyone opens the queue.

The same process on every ticket

Priorities, tags, assignment, acknowledgement replies and alerts to the team lead are applied the same way every time, busy days included.

Your systems stay in step

A call to your back office, your CRM or whatever the team already uses fires the moment the ticket changes.

Stop at the first match

Evaluate specific rules first and use the general rule as a fallback.

Combine compatible actions

Let multiple rules add tags, watchers and notifications to the same ticket.

Pause rules whenever you need

Pause a rule and turn it back on when needed. Its settings and history remain available.

Ready-to-use examples

Give every request the right path

Route tickets to the right team, handle urgent cases and update your systems without chasing every step.

How it works

Define the rule. Uppo runs the actions.

Choose the event, define the conditions and set the actions. No code required.

  1. 01

    When

    Pick the event that starts the rule: a ticket being created, or one specific change to a ticket already open.

  2. 02

    If

    Combine conditions on ticket data, contact data, the customer organisation and the AI classification.

  3. 03

    Then

    Run one action or several, automatically, in the order you put them in.

Actions

Assign, update and communicate without manual work

Run one action or a complete sequence. Use ticket data to personalise emails, replies and notes automatically.

  • Assign to a person
  • Assign to a team
  • Assign by a rule of thumb
  • Update a field
  • Add a tag
  • Add a watcher
  • Add an internal note
  • Send an email
  • Reply to the ticket
  • Change the subject
  • Call your own systems
  • Mark as spam, block or bin
Configuration, availability and frequently asked questions
More about this feature

Assign tickets, update priorities, send notifications and connect your own systems with visual rules built on customer service events.

  • Start with preconfigured rules
  • Build your own rules in the visual editor
  • Connect business systems with HTTP requests
The Uppo automations builder
Use preconfigured rules as a starting point and adapt them to your team’s work.Product illustration

Make it work for your team

Assign, update and communicate without manual work

Assign to a person

The ticket lands in the queue of the agent you name.

Assign to a team

It goes to the group rather than one individual, and whoever is free picks it up.

Assign by a rule of thumb

Named person, round robin, least busy agent or declared skill, for when you would rather not decide case by case.

Update a field

Status, priority, due date, language, topic and your own custom fields.

Add a tag

To find and group tickets later without adding a new field.

Add a watcher

For the people who need to know what is happening without owning the ticket.

Add an internal note

Internal by default: it stays on the ticket and the customer never sees it.

Send an email

To an agent, a team or an address you type in, with a formatted subject and body.

Reply to the ticket

A reply to the customer on the channel they used, for acknowledgements that do not need an agent.

Change the subject

Replace the title, or add a prefix or suffix so it stands out in the queue.

Call your own systems

GET, POST, PUT, PATCH or DELETE to your endpoint, with the headers, authentication and body you define.

Mark as spam, block or bin

Keep spam and unwanted messages out of your team’s daily work.

Events and conditions
Trigger events

React to every important event in real time

Run a rule when a ticket is created, a field changes, a customer replies or a deadline approaches.

When a ticket arrives

Works across every connected channel: email on your own domain, Microsoft 365 over OAuth, Google Workspace via forwarding, Instagram, Messenger, WhatsApp Business, web chat and web forms. This is where routing, priority and tags get decided, before anyone opens the queue.

When something changes

You pick the events that matter, one or several. On anything else the rule is not evaluated.

  • Status changed
  • Custom status changed
  • Priority changed
  • Agent assigned
  • Team assigned
  • Topic changed
  • Tag added
  • Watcher added
  • Customer replied
  • Agent replied
Conditions

Apply the right treatment to every request

Combine ticket, customer and organisation data to apply different priorities, SLAs and assignments when needed.

Ticket data

Status, priority, inbound channel, subject, topic, tags, assignee, due date, created and updated dates, first reply, last customer reply.

Contact data

Name, email, phone, language, target group and tags of the person who wrote in.

Customer organisation data

Name and domain of the organisation the contact belongs to, so you can treat one account differently from another without tagging by hand.

AI classification result

Use intent, issue type, suggested priority and sentiment in rule conditions. Set a confidence threshold to decide when to apply the AI classification.

Custom fields

The fields you added to the ticket behave like any other in conditions, with the values from your own list.

Operators, ready to use

Is and is not, contains and does not contain, empty and not empty, greater and less than, hours elapsed since a date. Text comparison ignores case.

Execution and control

Stay in control when several rules match

Define the execution order and choose whether to stop at the first match or apply every valid rule.

Stop at the first match

The routing setting. The list is read top down, the first rule whose conditions are true acts, and the scan stops. Specific cases at the top, the catch-all at the bottom.

Run every rule that matches

The setting for effects that add up: tags, watchers, notifications. Each rule checks its own conditions and does not take the turn away from the others.

Control the order the rules run in

The two modes do not compete: a rule set to "run every match" still acts when another one stopped at the first match. That keeps cumulative effects independent of routing.

A rule that is switched off is not evaluated and does not take a turn: the order of the others stays exactly as you set it.

Control

Every run is tracked, including failures

Review the ticket, conditions, actions and errors in a complete and understandable log.

Execution log

For each rule: when it fired, on which ticket, which conditions came back true and which actions ran.

Outcome of the actions

Success, partial or failed. Partial means one action did not complete and the others did, with the error message sitting next to the action that stopped.

Every step of the chain is visible

An action that changes a field can set off another rule: the log shows the whole sequence, in the order it happened.

Calls to your systems on record

URL, method, the body sent, the response code and the response received, so you verify the integration here rather than by trial and error.

Statistics for the period

Total and active rules, successful, partial and failed runs, and which rule did the most work.

Switch off without deleting

One toggle stops the rule and leaves its configuration and history intact. It is the right way to isolate a behaviour and switch it back on later.

Duplicate instead of rewriting

Copy a rule that works, change the one value that needs changing, switch it on. Per-channel and per-team variants get built this way.

Connect automation to processes with Uppo Flow

Connect automation to processes with Uppo Flow

Start workflows with tasks, approvals and deadlines to coordinate processes that involve several people and steps.

Automations

Run actions in response to an event, such as assigning a ticket, updating a field or sending a notification.

Uppo Flow

Handles procedures with several steps: tasks assigned to people, approvals, waits and branches that run in parallel. A case stays open until the path is finished.

From rule to process

A rule can start a Flow and coordinate subsequent tasks. Basic nodes are included in every plan; advanced nodes are available with Enterprise.

Explore Uppo Flow

Availability by plan

What changes from one plan to the next, in one place.

Custom rules
10 on Starter, 20 on Growth, 100 on Scale. Enterprise capacity is scalable. The rules shipped with the account sit outside that count.
Available actions
The same on every plan. The only one tied to a module is starting a Flow, which is enabled with Uppo Flow.
Triggers
Ticket events: creation and the changes you choose, from a status move to a customer reply.
Calls to your own systems
GET, POST, PUT, PATCH and DELETE to your endpoint, with the headers and authentication you set: custom header, Basic or Bearer.
Who gets to write the rules
Automations are configured in settings and follow role permissions, so the people working tickets cannot change everyone's rules by accident.
Uppo Flow
Base nodes on every plan; advanced nodes with Enterprise.

Frequently asked questions

Configuration, assignments and connecting automation to Uppo Flow.

What can a helpdesk automation do?

Assign the ticket to a person, a team or by a rule of thumb; update status, priority, due date, language, topic and custom fields; add tags, watchers and internal notes; send an email or a reply to the customer; change the subject; call one of your own systems; mark as spam, block or bin. A rule combines as many of these as you need, in the order you choose.

How does automatic ticket assignment work?

You pick the event, usually ticket creation, and the conditions that single out the case: channel, subject, customer, AI classification, custom fields. Then you choose the action: named person, team, round robin, least busy agent or declared skill. The ticket lands in the right queue before anyone opens it.

When does a rule fire?

The moment the event you chose happens: a ticket being created, or one specific change to an existing ticket such as a status move, an assignment or a customer reply. Conditions combine with AND, with OR or in blocks, and the fields come from the ticket, the contact, the customer organisation, the AI classification and your own custom fields.

What happens if several rules match?

It depends how you set each one. A rule marked "stop at the first match" halts the scan of rules with that same setting; one marked "run every match" acts anyway, because the two modes are two independent passes. Evaluation order is list order, and you change it by dragging.

How do I try out a new rule?

Switch it on against a narrow condition, read the execution log, then widen it once the behaviour is what you wanted. You can switch it off with a toggle at any point, and its configuration and history stay where they are.

Can I connect Uppo to my own systems?

Yes. An action calls your endpoint with the method, headers, authentication and body you define, and the log keeps the URL, the body sent and the response received. For deeper integrations there are the Uppo REST API and the available connectors, from GitHub to Stripe.

Automations or Uppo Flow?

Automations react to an event and update the ticket. Uppo Flow handles procedures with several steps: assigned tasks, approvals, waits and parallel branches. A Flow starts from an automation rule, so the two work together. Base nodes are included on every plan and advanced nodes with Enterprise.

How many rules can I create?

10 on Starter, 20 on Growth, 100 on Scale; Enterprise capacity is scalable. The rules shipped with the account sit outside that count, and the available actions are the same on every plan.

Read more

Every feature

Channels, tickets, SLAs, knowledge base and portals, on one page.

Go to the features overview

Plans and limits

What each plan costs and what it includes.

Compare plans and pricing

Security and governance

SSO, permissions, IP restrictions, audit trail and data hosted in the European Union.

Read how we protect your data

Automate repetitive work

Start with the rules included in your account and build your own without writing code.