Project messaging channels: messengers in Requests

SENSEVER

The official Sensever channel: guides and API documentation for Chat, Requests, Flow, Studio, bots and messaging channels.

9 min de lecture

Project messaging channels: messengers in Requests

Customers message you on Telegram, MAX, WhatsApp, Instagram and Facebook Messenger, and you reply from one place — your project's requests in Sensever. Every new customer message lands in that customer's request, and the agent's reply goes back to the customer in the same messenger. If needed, you can turn on an AI assistant in the project to help with replies.

Where to set it up

Projects → your project → the "Channels" tile → the "Messaging channels" block. The project owner and admins can connect and configure channels.

The block has two lists, shown as identical tiles:

  • at the top — connected channels;

  • below — grey tiles for messengers that aren't connected yet, with a "Connect" button.

A project can have one channel per messenger: one Telegram bot, one MAX bot, one WhatsApp number, one Instagram account, one Facebook Page. The same bot or number can't be connected to two projects.

Chat on the website and Sensever

The same list has two built-in ways to write besides the messengers:

  • Chat on the website — the chat right in the widget and on the project's contact page, no messenger needed;

  • Sensever — "Continue in Sensever": the customer writes from their own Sensever account.

Both are on by default. Clear "Show in widget" to remove one from the widget and the contact page. For example, a project that wants every customer on WhatsApp turns off both and keeps only WhatsApp. Drag the rows by the handle to set the order of the buttons in the widget; the built-in rows and the messengers share one order.

At least one way to write must stay: the last visible one can't be turned off. With "Chat on the website" off, new visitors can't start a chat in the widget, and the widget shows no invitations; conversations that already started go on.

How to connect a messenger

Click "Connect" on a grey tile — a form with brief instructions opens below it. Detailed step-by-step guides:

  • Telegram in a project: connecting a bot

  • MAX in a project: connecting a bot

  • WhatsApp in a project: connecting through the Cloud API

  • Instagram in a project: Direct through your own Meta app

  • Facebook Messenger in a project: Page messages through your own Meta app

Channel tile

On the left is the messenger icon (in color when the channel is on), and to its right are three lines:

  1. The name of the bot, number or account.

  2. The messenger and the @username or +number.

  3. The status line: empty if everything is fine, or a short note about what needs attention. The full text is in the tooltip.

What the status line can show:

Text

What it means

Waiting for the first request from Meta

WhatsApp, Instagram or Messenger is saved in Sensever, but Meta hasn't sent a single request yet: the webhook isn't saved or subscribed in the Meta app

Messenger response: "…"

The messenger's own words explaining why it rejected the channel

No incoming messages since …

A channel that usually gets messages has been silent for more than 24 hours

Connection error

Subscribing to messages failed during connection

Not shown in the widget; messages are not received

The channel is turned off

A red icon with an arrow in the status line means there are undelivered replies. Click it to send them again. In the request itself, an undelivered reply has a "Retry" link below it — any agent who replies in the request can use it. Messages that won't get through anyway (the 24-hour window has closed, the customer blocked the bot) aren't resent.

Managing a channel

  • The "On / Off" switch in the top right. A channel that is off doesn't receive or send messages and disappears from the widget; request history is kept. Turning it on reconnects the channel with the saved details.

  • "Show in widget" — a checkbox. If you clear it, the messenger button disappears from the widget on your site, but the channel keeps working: customer messages arrive and replies go out.

  • The order of buttons in the widget matches the order of the tiles. Drag a tile by the dots on the left, or click the dots and move it with the ↑ and ↓ arrow keys. The order is saved immediately.

  • "Refresh channel data" (the arrows icon). Sensever checks the bot or number name against the messenger every 6 hours; the button does it right away.

  • "Configure" (the gear). Opens the settings below the tile: department, tokens, and for WhatsApp, Instagram and Messenger — the webhook details. Saved tokens and secrets are shown as their first characters followed by asterisks; to replace one, click × and paste the new value. Empty fields don't change saved values.

  • "Remove bot" (the trash can). Removes the connection and the saved tokens. Request history remains, and the bot or number itself stays yours in the messenger.

Moving from the widget to a messenger

If a customer starts a conversation in the widget on your site and then clicks a messenger button, the conversation continues in the same request: the agent sees the whole widget history, and replies now go to the customer in the messenger. The customer doesn't have to repeat the question.

  • Telegram and MAX: the bot opens with the request code; the customer just taps "Start".

  • Instagram: Direct opens with a request tag, and Instagram passes it along with the first message.

  • Messenger: the Page's chat opens with a request tag, and Meta passes it along when the customer starts the conversation.

  • WhatsApp: the chat is prefilled with text containing a code like SV-K7M2Q9AB — the customer sends it, and Sensever recognizes the request.

The request shows the line "The customer continued the conversation from the website widget at …". The code is valid for 14 days and can be used only once. If the customer has already written to this messenger before, they keep their existing request.

Department

In the channel settings, choose a department — new requests from this messenger go to its queue. "Shared queue" means the whole project support team sees the requests.

What is passed between the messenger and Sensever


Telegram

MAX

WhatsApp

Instagram

Messenger

Customer text, photos, videos, voice messages, files

yes

yes

yes

yes

yes

Customer location and contacts

yes

yes

yes

—

—

Agent files

as a file

as a file

as a file

as a file

as a file, up to 25 MB

Agent text formatting

bold, italic, strikethrough, code, links, spoilers, quotes

the same, a spoiler as plain text

the same, a link as text with its address, a spoiler as plain text

plain text, a link as text with its address

plain text, a link as text with its address

Customer reply to a specific message

shown as a reply

shown as a reply

shown as a reply

shown as a reply

shown as a reply

"Typing…" shown to the customer

yes

yes

typing indicator

yes

yes

Agent deletes a reply

deleted for the customer (up to 48 hours)

deleted for the customer

not allowed by WhatsApp

not allowed by Instagram

not allowed by Messenger

Reactions

both ways

not in the MAX API

both ways

both ways

both ways

Customer edits

shown in the request

shown in the request

—

shown in the request

shown in the request

Agent edits

sent to the customer

sent to the customer

WhatsApp doesn't allow edits

Instagram doesn't allow edits

Messenger doesn't allow edits

Read receipts

not passed to bots

the customer sees that you read it

both ways

both ways

both ways

Reply window

unlimited

unlimited

24 hours

24 hours

24 hours

Formatting from the message field (bold, italic, strikethrough, code, links, spoilers, quotes) reaches the customer as the messenger's own formatting; where the messenger has none, the customer gets the plain text without formatting characters. A file the messenger doesn't accept (too large or of an unsupported type) is sent as a link that is valid for 48 hours. In WhatsApp, the typing indicator also marks the customer's message as read — that's how WhatsApp works.

The customer's name and @username are updated with every message they send: if the customer changes them in the messenger, the request shows the new ones. For Instagram and Messenger, they are taken from the customer's profile. The request info shows the @username for Telegram, Instagram and MAX, with a link to the profile for Telegram and Instagram.

The 24-hour window (WhatsApp, Instagram and Messenger)

WhatsApp, Instagram and Messenger allow replies only within 24 hours of the customer's last message. After that, the messenger rejects the reply — the agent sees "Not sent: …" below the message, and the channel keeps working. As soon as the customer writes again, the window reopens.

  • WhatsApp: after the window closes, you can send the customer a Meta-approved message template — use the templates icon next to the paperclip in the request or the "Send template" link below an unsent reply. For details, see the article "WhatsApp in a project: connecting through the Cloud API", section "Message templates".

  • Instagram: you can reply for up to 7 days after the customer's message if Meta has granted your app the human_agent permission (through App Review). Sensever tries to send this way on its own when the window is closed.

  • Messenger: the same as Instagram — up to 7 days with the human_agent permission.

"Sensever Channels" notifications

If something happens to a channel, the service bot "Sensever Channels" messages the project owner and admins — as a regular conversation, with a notification and an unread counter. It reports when:

  • the messenger rejected the channel: the token was revoked or expired, Meta blocked the app or restricted the WhatsApp Business account, or the WhatsApp number was deregistered from the Cloud API;

  • another service started receiving the bot's messages;

  • Meta signs messages with a different app secret;

  • Meta doesn't send Sensever the messages of people without a role in your app (Messenger, Standard Access);

  • the Instagram token can't be renewed and will soon stop working;

  • WhatsApp, Instagram or Messenger is saved in Sensever, but an hour later Meta still hasn't sent the first request;

  • a channel that usually gets messages has been silent for more than 24 hours.

Each message says what happened and what to do. Until the problem is fixed, a reminder arrives once every 24 hours. When the channel works again, the bot tells you that too. If the message subscription was simply deleted, Sensever restores it on its own without bothering anyone.

Personal notification settings

Each agent decides for themselves how requests from each channel are shown: "On home" or "Quiet". This is set in personal feed settings and doesn't affect other agents.

If messages don't arrive or aren't sent, see the article "Messaging channels: when messages don't arrive or aren't sent".

Commentaires

Auteurs