Channels

One inbox, every channel. The agent experience is the same everywhere; delivery and a few rules differ per channel.

Webchat

Agent replies are delivered live to the embedded webchat widget. The customer sees them appear in real time, with the agent's name, exactly as they'd see a bot message. There's nothing extra to configure beyond embedding the widget.

If the widget is closed when an agent replies, its unread badge increments so the customer knows to reopen it.

Mobile app

Replies reach a customer in your app the same way as on webchat: live, with the agent's name. When the app is closed, they also get a push notification that opens the conversation, once the deployment has its Firebase key (see Push Notifications). A customer your app signed in keeps one conversation across every device they sign in on.

Intercom

Intercom is two-way. Replies sent from the inbox are posted to Intercom as the linked admin (see Linking Intercom admins), and actions taken inside Intercom are mirrored back into the inbox:

  • An admin replying in Intercom is recorded in the thread and takes over the conversation.
  • Assigning, opening, or closing a conversation in Intercom updates its inbox assignment and status.
  • Handoff applies the handoff tag and unassigns the bot; resuming the bot removes the tag and reassigns it to the bot admin.
  • With the Universal Inbox Queue handoff strategy, the inbox decides who has the conversation: claiming, transferring, releasing, closing and reopening in the inbox do the same in Intercom.

If Intercom assigns a conversation to someone who isn't a linked support agent, the inbox leaves the existing assignment alone rather than dropping it from your queue.

Telegram

Replies are delivered to the customer's chat through your Telegram bot. There's no service window, so you can reply whenever the conversation is open. Connect Telegram via the Telegram deployment guide.

WhatsApp

WhatsApp enforces a 24-hour customer-care window: you can send free-form replies only within 24 hours of the customer's most recent message. The composer tracks this for you: when the window is open you reply normally; when it closes it shows a banner and blocks free-form replies.

Outside the window:
  • Free-form replies are blocked. The one reply WhatsApp delivers is an approved message template, sent from the Template tab in the composer.
  • Internal notes are never affected: you can always leave notes for your team.
  • The window reopens the moment the customer sends a new message.

Message templates

Templates are written and submitted for approval in Meta's WhatsApp Manager, on the WhatsApp Business Account your number belongs to. The inbox reads them from there; you don't create or edit them here. A number connected through Meta signup has them straight away. A number connected with your own Meta app has them once its first message arrives, provided you subscribed to the template webhook fields (see the WhatsApp deployment guide).

The list keeps itself up to date. Templates are copied from Meta when the number is connected, and again whenever Meta approves, rejects, pauses or recategorises one, or its text changes. The whole list is also re-checked against Meta once a night. A template deleted in WhatsApp Manager disappears from the list. If a template you just had approved isn't there yet, use the refresh button beside the search, or Check for new templates when the list is empty, to look again straight away. Each number can be checked once a minute, by anyone on your team.

Only approved templates the inbox can fill in are offered: text headers, the body, footers, and quick-reply, call and fixed-link buttons. Anything else is left out, including authentication (one-time code) templates, image, video, document or location headers, carousels, limited-time offers, coupon codes, catalog and product buttons, WhatsApp Flows, and buttons that carry their own variable, such as a personalised link.

To send one, open the Template tab, search by name or wording, and pick a template. The preview stays in view while you fill in its variables: the one you are typing in is highlighted, and filled values are marked so you can check the message reads as intended. Each field shows Meta's sample value as a hint. A variable named for a contact detail, such as first_name or email, is filled in from the contact for you to check. The template is sent once every field has a value.

A sent template appears in the conversation with its footer and buttons, as the customer sees it. When the customer taps a quick-reply button, the button's text arrives as their reply. If WhatsApp refuses a template, straight away or after accepting it, the message is marked failed with the reason and a Retry option.

Opt-outs

A customer who replies UNSUBSCRIBE opts out, and replying SUBSCRIBE opts them back in. Only the word on its own, in capitals, counts: "unsubscribe" or "please unsubscribe me" reaches your bot or your team like any other message, and so does SUBSCRIBE from a customer who never opted out. Each gets a confirmation, and the conversation records a note so agents can see when it happened. Neither word is read as an answer to the bot's last question.

In UniversalChatbot, what UNSUBSCRIBE holds back is your choice, under Settings → Support → WhatsApp opt-outs; UniversalDesk uses the defaults below. It only ever covers messages you start: a customer who writes to you is always answered.

  • Marketing templates (on by default): offers and promotions.
  • Utility templates (on by default): updates on something the customer already has with you, such as an order or an account.
  • Automated follow-ups: messages your bot sends on its own when a conversation closes, times out or is left unanswered.
  • Customer satisfaction surveys: the rating question sent when a conversation ends.

The same page sets the confirmation sent for UNSUBSCRIBE and for SUBSCRIBE. Leave either blank to use the default wording, which for UNSUBSCRIBE tells the customer which messages they will no longer get and that you still reply when they write.

Customers can also stop marketing messages from your business inside WhatsApp itself. The inbox respects that too, whatever your settings say, until they turn marketing messages back on in WhatsApp.

Templates a customer has opted out of are left out of the Template tab, with a short note saying which kind is hidden and why. If that leaves nothing to send, the tab says so: wait for the customer to write, or, if the account simply has no approved templates of the kind still allowed, get one approved in WhatsApp Manager.

Messenger

Replies are delivered to the customer's Messenger chat through your Facebook Page. Messenger has two windows rather than one, and the composer tells you which you are in.

For 24 hours after the customer's last message you reply normally. Between then and seven days, only a person may answer: the bot stops, an agent can still reply, and the composer says the reply goes as a human agent reply. Past seven days nothing can be sent and the composer stops you.

If someone on your team answers from Meta's Page Inbox, or from Instagram's own inbox on an Instagram conversation, the reply shows in the inbox and the bot stops answering that conversation, the same as replying from the inbox.

Replying as a human agent:
  • Meta allows it on the understanding that a person wrote it, so keep it a personal answer to that customer rather than marketing.
  • A campaign sent this way is a policy violation, and it is your Page that carries the consequence.
  • Internal notes are never affected, whichever window you are in.
  • Both windows reopen the moment the customer sends a new message.

Instagram

Replies are delivered to the customer's Instagram inbox, and the windows work exactly as they do on Messenger: free for 24 hours, a person only for seven days, nothing after that.

Replies to your stories and mentions in other people's arrive here as ordinary direct messages, but only once you have switched them on for that account. Until then they are not answered and do not reach the inbox at all. See the Instagram deployment guide.

X

Replies are delivered to the customer's X direct messages as text. X does not carry files, so the composer sends text only on these conversations. There is no reply window: you can answer a customer at any time.

If someone on your team answers from the X app, the reply shows in the inbox and the bot stops answering that conversation, the same as replying from the inbox. Encrypted chats on X never reach the bot or the inbox, and a customer who has closed their direct messages to your account cannot be reached.

See the X deployment guide.

Public comments and mentions

Comments, mentions and reviews that Social sends to support arrive as conversations. A public thread shows a Public label with the platform and an Open post link. Replies you type are posted publicly as the account, so everyone can see them. The composer says so and shows the platform's length limit. Attachments cannot be sent on public replies.

Where the platform allows it, Hide removes a comment from view and Show it again puts it back. Hiding does not close the conversation. Close it as usual, and the team's close sheet still applies. On Facebook and Instagram, Reply privately sends the author a private message and claims the conversation.

Some replies the platform will not take. On X, apps can reply only when the author tagged or quoted the account. Private replies on Facebook and Instagram have a 7-day limit and allow one reply per comment. In those cases the composer explains why and offers a button to open the post on the platform, such as Open on X, so you answer there. A reply made in the platform's own app closes the conversation.

If the platform may have posted a reply but did not confirm it, the reply cannot be sent again from the inbox. Check the post first.

When Social deletes a collected comment, mention or review, because it reached the end of the time Social keeps it, was deleted on the platform, or was deleted with its account, its messages stay in the conversation and read "This post was deleted", with no link to the post. A conversation left with nothing to answer closes, and a reply still waiting to go out fails.

A team can turn on Approve public replies in its inbox settings. Its agents' public replies then wait, unsent, until a supervisor of the team or an owner, manager or admin approves them. The setting can only be turned on once at least two of them have inbox seats, so every reply has someone other than its author to approve it. If the team is the Social account's support team for comments, its threads keep waiting for approval when they are moved to another team or to no team. A canned response marked Approved for public use posts straight away when sent without changes, as long as every placeholder in it is filled in. One that still shows a placeholder, such as an agent name for an agent with no profile name, waits like any other reply. A canned response that uses the customer's name can't be approved for public use, so replies built from it always wait. Private replies and direct messages never wait.

Public threads do not count towards your plan's conversation allowance, because they were already counted when Social collected them. AI used on them, such as reply suggestions, uses your AI allowance as usual.

Delivered and read

Each reply shows Sent once the channel has it, then Delivered and Read as the channel reports them. Channels report different things:

ChannelDeliveredRead
WhatsAppYesYes, unless the customer turned off read receipts
MessengerYesYes
InstagramNoYes
XNoYes
IntercomNoYes, once the customer opens the conversation
Webchat and mobile appNoYes, once the reply is on screen in the open chat
TelegramNoNo

Where a channel reports neither, a reply stays at Sent, and hovering over it, or pressing and holding in the app, says so. A read covers every earlier reply as well. On WhatsApp, a reply the channel accepted and then couldn't deliver is marked Not delivered with WhatsApp's reason. Your own reading is never shown to the customer.

Talk to sales
This form is running on UniversalChatbot.