Every request in one queue
Email, social, WhatsApp, chat and forms in one list: everyone can see the open workload.
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.
The problem
It is not about volume. It is enough that requests arrive from several places and that more than one person answers them.
A shared mailbox does not show who owns each request: two people reply to the same message, or nobody does.
A colleague is away and the conversation is in their mailbox: the customer starts over and response time doubles.
Without priorities and deadlines, the latest arrival gets attention: a production outage stays below a quote request.
When requests live in mailboxes, chats and spreadsheets, volumes, response times and recurring issues cannot be measured together.
What changes
A shared queue, clear ownership, visible deadlines and customer history help your team provide consistent service.
Email, social, WhatsApp, chat and forms in one list: everyone can see the open workload.
Assign explicitly to a person or team: ownership is visible in the queue, easy to change and recorded in the history.
SLAs track time while work is happening: early warnings leave room for escalation.
Messages, internal notes, files and handovers stay in the ticket and contact record: the next agent reads the context.
The process
This is the order worth following. Each step works on its own: you do not need everything ready before you start using it.
Start with email: two DNS records for your domain, OAuth for Microsoft 365, forwarding for Gmail. Add other channels when needed.
Rules handle initial routing, ownership, priority, tags and fields. Requests not covered remain available for manual assignment.
Reply from the ticket with the original channel selected. Use internal notes, saved replies and watchers to keep colleagues informed.
Closing a request leaves its history and dashboard data: channel volume, response and resolution times, SLAs, agent and team workload.
Before you sign
Demos nearly all show the same things. These six questions are what brings the differences out, and the answers are worth having in writing.
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.
The six parts that decide whether the working day flows or jams. The full inventory lives on the features page.
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.
Set response and resolution times using your service hours, holidays and waiting states.
Rules in three parts: event, conditions, actions. They assign, update fields, notify and call a webhook, and every run stays in the log.
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.
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.
REST APIs for integrations, signed inbound webhooks and a GraphQL connector towards your own systems.
Setup, integrations and selection criteria.
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.
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.
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.
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.
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.
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.
Yes. First response, subsequent replies and resolution have separate targets from Starter, with service hours, holidays and configurable alerts.
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.
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.
How to choose a helpdesk, what changes compared with a shared mailbox, and which numbers to watch once you are live.
What actually changes between a shared mailbox and a helpdesk, with examples from small companies.
Read the guideThe questions to put to every vendor before you sign, from channels to what it really costs your team.
Read the guideWhich numbers to watch once you are live, and which ones say very little about how the team is doing.
Read the guideHow conversations stay connected when the same customer writes on WhatsApp, then by email.
Go to multichannel helpdeskPriorities, assignments and deadlines to follow each request through to closure.
Go to ticket managementWhat each plan costs and the quantities included in each.
Compare plans and pricingShow 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.