Helpdesk software

Helpdesk software that turns every request into organised work

Organise conversations, people and processes in one platform. Uppo brings together tickets, SLAs, Uppo Flow, AI and the customer portal to coordinate service and measure its performance.

  • All connected channels in one queue
  • SLAs and automations to organise the work
  • Service content hosted in the EU
Helpdesk software that turns every request into organised work

The problem

Centralise the work before it gets scattered

It is not about volume. It is enough that requests arrive from several places and that more than one person answers them.

"Three of us watch the mailbox"

A shared mailbox does not show who owns each request: two people reply to the same message, or nobody does.

"Who was handling this customer?"

A colleague is away and the conversation is in their mailbox: the customer starts over and response time doubles.

"We don't know what to look at first"

Without priorities and deadlines, the latest arrival gets attention: a production outage stays below a quote request.

"We can't say how it's going"

When requests live in mailboxes, chats and spreadsheets, volumes, response times and recurring issues cannot be measured together.

What changes

A shared foundation for organised service

A shared queue, clear ownership, visible deadlines and customer history help your team provide consistent service.

Every request in one queue

Email, social, WhatsApp, chat and forms in one list: everyone can see the open workload.

Clear ownership

Assign explicitly to a person or team: ownership is visible in the queue, easy to change and recorded in the history.

See deadlines before they expire

SLAs track time while work is happening: early warnings leave room for escalation.

History shared with your team

Messages, internal notes, files and handovers stay in the ticket and contact record: the next agent reads the context.

The process

From shared mailbox to queue, in four steps

This is the order worth following. Each step works on its own: you do not need everything ready before you start using it.

  1. 01

    Connect the channels

    Start with email: two DNS records for your domain, OAuth for Microsoft 365, forwarding for Gmail. Add other channels when needed.

  2. 02

    Decide where the work goes

    Rules handle initial routing, ownership, priority, tags and fields. Requests not covered remain available for manual assignment.

  3. 03

    The team works the queue

    Reply from the ticket with the original channel selected. Use internal notes, saved replies and watchers to keep colleagues informed.

  4. 04

    Measure the results

    Closing a request leaves its history and dashboard data: channel volume, response and resolution times, SLAs, agent and team workload.

Before you sign

Six questions to put to any vendor, Uppo included

Demos nearly all show the same things. These six questions are what brings the differences out, and the answers are worth having in writing.

Does the subscription grow with headcount?

Why it matters
It determines the three-year cost: per-agent pricing multiplies whenever someone joins the team.
How Uppo answers
Starter €19, Growth €25, Scale €35 and Enterprise €45 per agent per month, excluding VAT. No minimum license count.

Which channels can you actually reply from?

Why it matters
“Supported channel” can mean a notification only: reading and replying are different daily tasks.
How Uppo answers
Read and reply through your domain email, Microsoft 365, forwarded Gmail, Instagram DMs, Messenger, WhatsApp Business, chat and web forms.

Are SLAs included, or a separate module?

Why it matters
Hard-to-see deadlines make it difficult to identify which requests need attention first.
How Uppo answers
First response, next response and resolution targets from Starter, with service calendars and configurable alerts.

Can customers resolve things on their own?

Why it matters
A request avoided costs less: charging separately for self-service changes the total.
How Uppo answers
Knowledge base, self-service portals and widget on every plan; a custom portal domain from Growth.

Can the data be reached from outside?

Why it matters
A closed helpdesk becomes an island when you need to connect business systems or export its history.
How Uppo answers
Public REST API, signed inbound webhooks and a GraphQL connector to your API. Data exports on every plan.

Where is the data held, and who can see it?

Why it matters
It is the first question Legal asks, and it can determine eligibility in a public tender.
How Uppo answers
EU-hosted content, tenant isolation and role permissions. SSO, extended audit and IP restrictions from Scale; SCIM on Enterprise.

If a vendor answers these six questions only verbally, ask for them in the contract: the features that count are the ones that stay in writing.

Frequently asked questions and related resources

The comparison in detail

Does the subscription grow with headcount?
Why it matters This is the line that decides the three-year cost. Per-agent pricing starts low and multiplies every time someone joins the team, part-timers included.
How Uppo answers Starter €19, Growth €25, Scale €35 and Enterprise €45 per agent per month, excluding VAT. There is no minimum number of licences.
Which channels can you actually reply from?
Why it matters "Supported channel" sometimes only means a notification arrives. The gap between reading and replying is the entire working day.
How Uppo answers You read and reply on email from your own domain, Microsoft 365 and Outlook, Gmail via forwarding, Instagram DMs, Facebook Messenger, WhatsApp Business, website chat and web forms. Slack carries notifications for the internal team.
Are SLAs included, or a separate module?
Why it matters When deadlines are hard to see, it is difficult to identify the requests that need attention first.
How Uppo answers First response, next response and resolution targets from Starter, with a service calendar and configurable alerts.
Can customers resolve things on their own?
Why it matters The request that never arrives is the cheapest one. If self-service is a paid add-on, the sums change.
How Uppo answers Knowledge base, self-service portals and the website widget are on every plan. From the Growth plan you also get a custom portal domain.
Can the data be reached from outside?
Why it matters A closed helpdesk becomes an island the day you need to connect it to your back office or take the history out.
How Uppo answers A public REST API, signed inbound webhooks and a GraphQL connector towards an API of your own. Data export via API too, on every plan.
Where is the data held, and who can see it?
Why it matters It is your legal team's first question, and in a public tender it is the one that rules vendors out.
How Uppo answers Service content hosted in the European Union, isolation per company and role-based permissions. Operator SSO with SAML, OIDC or LDAP, extended audit logs and IP restrictions from Scale; data redaction and widget attachment scanning from Scale, with scanning enabled in coordination with the Uppo team; SCIM provisioning from Enterprise.

Organising and setting up the service

The recurring symptoms of support without a tool

"Three of us watch the mailbox"
A shared mailbox does not say who picked up what. Two people answer the same message, or nobody does, because each assumes the other is on it.
"Who was handling this customer?"
Your colleague is on holiday and the thread is in their mailbox or on their phone. The customer explains everything again, and response time doubles over a filing problem.
"We don't know what to look at first"
With no priorities and no deadlines, the queue gets worked newest first. A production stoppage sits below a quote request, and nobody notices until the phone rings.
"We can't say how it's going"
When requests live in mailboxes, chats and spreadsheets there is no number to look at: not how many come in, not how long you take, not what people keep asking about.

A shared foundation for organised service

Every request in one queue
Email, social messages, WhatsApp Business, website chat and web forms land in the same list. Whoever opens the queue sees all the open work, not the share that happened to reach them.
Clear ownership
Assignment is explicit, to a person or to a team. You read it from the queue, change it in one click, and it stays in the ticket history.
Deadlines are visible before they pass
SLAs count time while the work is in progress, not afterwards. The warning threshold is configurable, so escalation arrives while there is still room to act.
History shared with your team
Messages, internal notes, attachments and hand-offs sit in the ticket and on the contact record. Whoever takes over reads instead of asking.

From shared mailbox to queue, in four steps

Connect the channels
Start with email. On your own domain that means two DNS records, a verification TXT and the DKIM signature; Microsoft 365 and Outlook connect over OAuth; Gmail goes through automatic forwarding. Social, WhatsApp, chat and forms come whenever you want them.
Decide where the work goes
Rules read the incoming message and do the first routing: assign to a person or a team, set priority, tags and fields. Whatever the rules do not cover is still assigned by hand.
The team works the queue
Replies go out from the ticket, on the channel it came in on. Internal notes for the team, saved replies for recurring questions, watchers for the people who only need to be kept informed.
Measure the results
What stays behind is the history on the contact and the data in your dashboards: volume by channel, first response time, resolution time, SLA compliance, workload per agent and per team.

One practical piece of advice: switch on one channel at a time and start from a few narrow rules. The execution log shows you where every ticket ends up, so you widen them with the data in front of you.

What you will actually use

The features you use every day

The six parts that decide whether the working day flows or jams. The full inventory lives on the features page.

Queue and tickets

Status, priority, assignee, tags and custom fields. Filters and views so you work the slice of the queue that concerns you instead of the whole list.

SLAs and business hours

Set response and resolution times using your service hours, holidays and waiting states.

Automations

Rules in three parts: event, conditions, actions. They assign, update fields, notify and call a webhook, and every run stays in the log.

Knowledge base and portal

The articles customers find on their own, and the portal where they follow their own requests. Dashboards also show the questions with no answer yet.

Widget and forms

Chat and forms on your own site: the visitor writes from there and a ticket opens with the fields already filled in, without going through a generic mailbox.

API and webhooks

REST APIs for integrations, signed inbound webhooks and a GraphQL connector towards your own systems.

Frequently asked questions about helpdesk software

Setup, integrations and selection criteria.

What is the difference between a helpdesk and a shared mailbox?

A mailbox keeps messages; a helpdesk keeps the work. Every request becomes a ticket with a status, an owner, a priority and a deadline, and stays attached to the customer record even when it arrives on another channel. It is the difference between knowing what was written and knowing what was done.

What does Uppo cost?

Starter costs €19, Growth €25, Scale €35 and Enterprise €45 per agent per month, excluding VAT. There is no minimum number of licences; capacity, included features and add-ons are on the Pricing page.

Does the price change if I add people to the team?

Yes: every agent licence follows the price of the selected plan. Add or remove licences without changing plans; the plan determines features, capacity and governance.

Do I need someone from IT to set it up?

Email on your own domain needs two DNS records, a verification TXT and the DKIM signature: whoever manages the domain adds them, and that is the only technical step. Microsoft 365 and Outlook are authorised over OAuth, Gmail with automatic forwarding. Social channels, the widget, forms, rules and SLAs are all configured from the settings.

Which tools does it integrate with?

GitHub, Stripe, Fatture in Cloud, Zoom, Trello and the file stores: Google Drive, OneDrive, Dropbox, Box, SFTP and WebDAV. For the systems you use that are not on the list there are the public REST API, a GraphQL connector towards your own API and a signed inbound webhook for your company.

Can I bring in the data I already have?

Yes. Contacts and content can be imported, and you can take your data back out whenever you want, via API too. For ticket history from another helpdesk we look together at what the source system exports and what is worth moving: it is a check we run before we start.

Are SLAs in the smallest plan too?

Yes. First response, subsequent replies and resolution have separate targets from Starter, with service hours, holidays and configurable alerts.

Is the phone one of the channels you can connect?

The channels you can connect are email, Microsoft 365 and Outlook, Gmail via forwarding, Instagram DMs, Facebook Messenger, WhatsApp Business, website chat and web forms. Requests that come in by phone join the queue when whoever answers opens the ticket from the contact record, under the same SLA as everything else.

Where is the data hosted?

In the European Union, with data isolated per company. The governance controls — audit trail, data redaction, IP restrictions, SSO and SCIM — are described on the security page.

Explore Uppo for your team’s work

Show us how requests reach you today and we will show you what they look like in Uppo: channels, routing, SLAs and the numbers that come out.