Multichannel helpdesk

Every customer care channel, in the same flow

Customers keep writing wherever they prefer. The team works from a single queue, with context and ownership always in view.

  • Read and reply from the same ticket for each connected channel
  • SLAs and customer history available in the ticket
  • The original channel stays visible on the ticket
Every customer care channel, in the same flow

Multichannel context

The problem is not how many channels you have: it is the jump between them

Adding a channel is easy. What is hard is keeping the conversation whole when the customer switches route halfway through.

One request, across channels

The customer starts on WhatsApp and emails a document: both conversations stay on the same contact record and can be merged with a click.

Centralised access for the team

Connect company accounts to Uppo: authorised operators handle messages without sharing credentials or devices.

No duplicate replies

See who owns each request: avoid duplicate replies and silence before the customer notices.

A shared process

One handling process, across every channel

Requests enter the shared queue. Your team assigns them, replies and tracks progress with the channel and history in view.

  1. 01

    It arrives and becomes a ticket

    The original channel stays on the ticket. If the sender is a known contact, the ticket is attached to their record.

  2. 02

    It joins the shared queue

    Routing rules also read the channel: WhatsApp requests can go to a different team from requests submitted through forms.

  3. 03

    You reply from the ticket

    The outbound channel is already set to the original one. Internal notes stay internal and are never shown to the customer.

  4. 04

    It stays on the contact record

    Once closed, the conversation joins the contact history: whoever opens the record sees everything, beyond the email thread.

The channels, one by one

What each channel needs, and where the reply goes out from

For each channel: what you prepare before you start, and which address, account or number the reply goes out from.

Email on your own domain

What it takes to connect it
Two DNS records: a verification TXT and the DKIM signature.
Where the reply goes out from
From the verified address on your domain.

Microsoft 365 and Outlook

What it takes to connect it
OAuth authorisation of the mailbox, no shared passwords.
Where the reply goes out from
From the connected mailbox.

Google Workspace and Gmail

What it takes to connect it
Automatic forwarding from the Google mailbox to Uppo.
Where the reply goes out from
From your verified domain, not from Gmail.

Instagram DMs

What it takes to connect it
Connecting the business account.
Where the reply goes out from
In the same conversation, from the connected account.

Facebook Messenger

What it takes to connect it
Connecting the business page.
Where the reply goes out from
In the same conversation, from the connected page.

WhatsApp Business

What it takes to connect it
A WhatsApp Business number dedicated to support.
Where the reply goes out from
In the same conversation, from the connected number.

Website chat

What it takes to connect it
The widget installed on the pages where you want it.
Where the reply goes out from
In the chat while the visitor is there, by email if they left an address.

Web forms

What it takes to connect it
A published ticket form with the fields you need.
Where the reply goes out from
By email, to the address given on the form.

Slack

What it takes to connect it
Connecting the workspace.
Where the reply goes out from
Notifications for the internal team; customers are answered from the ticket.

Whichever door a message comes through, the work is the same: same queue, same routing rules, same clocks.

The tools

The parts that do the joining up

The number of channels is not what makes the difference. What surrounds them is: who the customer is, who replies, in what words and how fast.

Contact record and history

One record per person, with conversations from every channel: context no longer depends on who was around that day.

Ticket forms and custom fields

Forms ask for order number, serial number and model up front: the ticket opens already filled in, avoiding another round of emails.

Routing by channel

Rules use the channel as a condition: different assignment, priority and tags according to where the request came in.

Saved replies

The same saved replies work on every channel: official wording stays consistent whoever answers.

Website widget

Chat on the pages where it is needed: messages enter the same queue, along with the page they came from.

Self-service portal

Customers follow their requests and find articles without contacting anyone: the channel that reduces work for the others.

Frequently asked questions and related resources

Multichannel work in detail

The problem is not how many channels you have: it is the jump between them

The customer changes channel, the context does not follow
They message on WhatsApp because they are in a hurry, then email the invoice because the file is on their computer. To you that is two disconnected threads; to them it is one request, and making them repeat it feels like a call centre.
Every channel has its own key
One person has the Instagram login, the WhatsApp phone sits in the shop, and accounts watches the info@ mailbox. The channel works as long as that person is around.
Nobody knows whether a colleague has already replied
With no single place there is no way to tell. You risk the double reply, or silence, and either way the customer notices before you do.

One handling process, across every channel

It arrives and becomes a ticket
The originating channel stays written on the ticket. If the sender is already a known contact, the ticket opens attached to their record.
It joins the shared queue
The same queue for every channel. Routing rules can read the channel too, so WhatsApp requests can go to a different team from the ones arriving through forms.
You reply from the ticket
The outbound channel is already set to the one it came in on: no wrong route, no copying the message somewhere else. Internal notes stay internal and the customer never sees them.
It stays on the contact record
Once closed, the conversation joins the contact's history alongside the ones from other channels. Whoever opens that record sees everything that happened, not just the email part.

The parts that do the joining up

Contact record and history
One record per person, holding conversations from every channel. It is the point where context stops depending on who was around that day.
Ticket forms and custom fields
Forms ask up front for what you need — order number, serial number, model — so the ticket opens already filled in instead of starting a round of emails.
Routing by channel
Rules can use the channel as a condition: different first assignment, priority and tags depending on where the request came in.
Saved replies
The same saved replies work on every channel, so the official wording does not change depending on who answers and from where.
Website widget
Chat on the pages where you want it. Whoever writes from there lands in the same queue, and the ticket carries the page it started from.
Self-service portal
Customers follow their own requests and find knowledge base articles without writing to anyone. It is the channel that takes work off the others.
Connect conversations from the same customer

When someone contacts you through several channels about the same request, you can merge tickets and retain the history in one shared conversation.

What you see

Both messages stay in the queue, both can be assigned, both run their own clocks, and both are already attached to the same contact record: the customer history is complete even before you merge.

What you do

One click from the ticket and it becomes a single conversation, carrying both channels and everything already written.

The person who knows the case decides: two different requests from the same customer never end up in one ticket, and one person's conversation never lands in front of another.

Questions about channels

The ones that come up once the conversation moves from "how many channels" to "how does it actually work".

If a customer writes on WhatsApp and then by email, do the two messages end up together?

You get two tickets and you merge them in one click from the ticket: from then on it is a single conversation. Both stay attached to the same contact record anyway, so the history is complete from the start.

Can I reply to Instagram messages straight from Uppo?

Yes. Instagram DMs and Facebook Messenger messages are read and answered from the ticket, and the reply goes out from the connected account or page. There is no need to open the app.

Which number can I connect to WhatsApp?

You can connect a number eligible for WhatsApp Business Platform. During setup, Meta shows which numbers you can use with your account. Messages arrive in the Uppo queue and replies are sent from the connected number.

How do I connect Google Workspace or Gmail?

With automatic forwarding from the Google mailbox to Uppo: messages join the queue and replies go out from your verified domain. Nothing changes for the customer; what changes for you is that the thread is worked in Uppo, with assignment, internal notes and SLAs.

What about requests that come in by phone?

The channels you can connect are email, Microsoft 365 and Outlook, Google Workspace and Gmail, Instagram DMs, Facebook Messenger, WhatsApp Business, website chat and web forms. A phone call joins the queue when whoever answers opens the ticket from the contact record, under the same SLA as every other request.

How many mailboxes can I connect?

It depends on the plan: the number of mailboxes grows from Starter through Growth, Scale and Enterprise. The exact figures are in the plan comparison table.

What is the Slack connection for?

Keeping the internal team informed: Uppo's notifications land in Slack, while the customer is answered from the ticket, on the channel the request came in on.

Do SLAs work the same way on every channel?

The clocks belong to the ticket, not to the channel: first response, next response and resolution are counted the same way whether the request came by email, on WhatsApp or through a form. The rules for applying them are yours to set.

Bring your customer service channels together

Tell us where customers contact you today: we’ll show you how messages enter Uppo and how their history stays connected.