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.
Customers keep writing wherever they prefer. The team works from a single queue, with context and ownership always in view.
Multichannel context
Adding a channel is easy. What is hard is keeping the conversation whole when the customer switches route halfway through.
The customer starts on WhatsApp and emails a document: both conversations stay on the same contact record and can be merged with a click.
Connect company accounts to Uppo: authorised operators handle messages without sharing credentials or devices.
See who owns each request: avoid duplicate replies and silence before the customer notices.
A shared process
Requests enter the shared queue. Your team assigns them, replies and tracks progress with the channel and history in view.
The original channel stays on the ticket. If the sender is a known contact, the ticket is attached to their record.
Routing rules also read the channel: WhatsApp requests can go to a different team from requests submitted through forms.
The outbound channel is already set to the original one. Internal notes stay internal and are never shown to the customer.
Once closed, the conversation joins the contact history: whoever opens the record sees everything, beyond the email thread.
The channels, one by one
For each channel: what you prepare before you start, and which address, account or number the reply goes out from.
Whichever door a message comes through, the work is the same: same queue, same routing rules, same clocks.
The tools
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.
One record per person, with conversations from every channel: context no longer depends on who was around that day.
Forms ask for order number, serial number and model up front: the ticket opens already filled in, avoiding another round of emails.
Rules use the channel as a condition: different assignment, priority and tags according to where the request came in.
The same saved replies work on every channel: official wording stays consistent whoever answers.
Chat on the pages where it is needed: messages enter the same queue, along with the page they came from.
Customers follow their requests and find articles without contacting anyone: the channel that reduces work for the others.
When someone contacts you through several channels about the same request, you can merge tickets and retain the history in one shared conversation.
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.
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.
The ones that come up once the conversation moves from "how many channels" to "how does it actually work".
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.
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.
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.
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.
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.
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.
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.
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.
How direct messages, website chat and social expectations are actually handled.
How to bring direct messages into a work queue without losing the tone the channel expects.
Read the guideWhere to put it, what to ask before opening the conversation, and when it is better switched off.
Read the guideWhat people expect when they write from a social channel, and how that differs from email.
Read the guidePriority, assignment, the three SLA clocks and how the backlog is kept in order.
Go to ticket managementHow the chat is configured, what it collects and how it behaves when nobody is online.
Read the widget pageWhat you connect today with a ready-made connector, and how to connect a system of your own with the API and webhooks.
See the available integrationsTell us where customers contact you today: we’ll show you how messages enter Uppo and how their history stays connected.