{"id":6758,"date":"2026-08-13T11:21:11","date_gmt":"2026-08-13T09:21:11","guid":{"rendered":"https:\/\/help.ino.cx\/?post_type=ht_kb&p=6758"},"modified":"2026-08-20T14:16:43","modified_gmt":"2026-08-20T12:16:43","slug":"telegram-in-the-messaging-pool","status":"publish","type":"ht_kb","link":"https:\/\/help.ino.cx\/index.php\/help-center\/telegram-in-the-messaging-pool\/","title":{"rendered":"Telegram in the messaging pool"},"content":{"rendered":"\n
\"Smart<\/figure>\n\n\n\n

[Reading time: 6 minutes]<\/em><\/p>\n\n\n\n

Overview<\/h2>\n\n\n\n

This article is part of the Messaging pool<\/strong> series. It focuses on the Telegram<\/strong> channel. For the general overview of the pool, see Messaging pool in the Banner<\/a><\/strong>.<\/p>\n\n\n\n

Telegram<\/strong>\u00a0is one of the\u00a0messaging<\/strong>\u00a0channels handled in the Banner. Customers write to you from their Telegram app, through one of your\u00a0Telegram bots<\/strong>, and their messages are handled exactly like the other messaging interactions: they appear in the\u00a0messaging pool<\/strong>, where advisors can\u00a0view, pick up, reply to, transfer, close<\/strong>\u00a0them, or attach them to CRM elements. If you need help to set up your Telegram bot, please click here<\/a>.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Telegram is an asynchronous<\/strong> channel relayed by Telegram: the customer can reply minutes or hours later, and the conversation stays open for the duration of a configurable session window<\/strong> (see section 7).<\/p>\n\n\n\n

1. How a Telegram message arrives in the pool<\/h2>\n\n\n\n

Every Telegram bot is linked to a Smart Routing<\/strong>. When a customer writes to the bot, the message always enters through that Smart Routing<\/strong>, which can:<\/p>\n\n\n\n

    \n
  • qualify the request automatically,<\/li>\n\n\n\n
  • send automatic messages<\/strong> (text, links, and choice menus rendered as Telegram buttons),<\/li>\n\n\n\n
  • then distribute<\/strong> the conversation to the appropriate queue<\/strong>, where it appears under Messages pending<\/strong>.<\/li>\n<\/ul>\n\n\n\n

    From there, the interaction is either presented<\/strong> to an available agent or picked up manually<\/strong> from the pool.<\/p>\n\n\n\n

    Note: if a bot has no Smart Routing linked, its incoming Telegram messages are ignored. A Telegram conversation can later be transferred<\/strong> to a specific agent, queue or Smart Routing.<\/em><\/p>\n\n\n\n

    2. The incoming Telegram popup<\/h2>\n\n\n\n

    When a Telegram interaction is distributed to you, a notification popup appears. It shows:<\/p>\n\n\n\n

      \n
    • the interaction type (Messages<\/strong>),<\/li>\n\n\n\n
    • the sender<\/strong> (the customer’s Telegram name, or an anonymous identifier),<\/li>\n\n\n\n
    • the queue<\/strong> name and the time already spent waiting<\/strong> in that queue,<\/li>\n\n\n\n
    • transfer<\/strong> details, if the interaction reaches you through a transfer,<\/li>\n\n\n\n
    • the associated script<\/strong>, if one is attached and you have the right.<\/li>\n<\/ul>\n\n\n\n

      Accept the interaction with the check button, or decline it with cross. A countdown<\/strong> shows the time you have left to decide before the interaction stops being presented to you. If your profile is configured for auto-accept<\/strong>, an “Acceptance in\u2026”<\/em> countdown accepts it automatically. Some profiles also use a preview<\/strong> mode, which lets you review the interaction before answering.<\/p>\n\n\n\n

      \"\"<\/figure>\n\n\n\n

      3. Picking a Telegram message from the pool<\/h2>\n\n\n\n

      You can also serve yourself from the pool instead of waiting to be presented an interaction:<\/p>\n\n\n\n

        \n
      1. Open the Messages pending<\/strong> tab.<\/li>\n\n\n\n
      2. Spot the Telegram rows using the Source<\/strong> column (Telegram tag and icon).<\/li>\n\n\n\n
      3. Click the hand button, Take this conversation<\/strong>, on the row you want.<\/li>\n<\/ol>\n\n\n\n

        The pool list shows, for each interaction: Wait time<\/strong>, Source<\/strong> (channel), Sender<\/strong>, From<\/strong> (reception time), Queue<\/strong>, Session duration<\/strong> and Forwarded<\/strong> status. An interaction can only be handled by one agent at a time<\/strong>: once you take it, it is yours until you close, end or quit it.<\/p>\n\n\n\n

        \"\"<\/figure>\n\n\n\n

        4. The Telegram conversation interface<\/h2>\n\n\n\n

        The conversation opens in the same interface used by the other messaging channels, organised in three areas: an info panel<\/strong> on the left, the central tabs<\/strong> (conversation, CRM card, case, script, and so on), and the reply area<\/strong> at the bottom.<\/p>\n\n\n\n

        The message thread shows:<\/p>\n\n\n\n

          \n
        • Customer messages<\/strong>, left-aligned;<\/li>\n\n\n\n
        • advisors messages<\/strong>, right-aligned;<\/li>\n\n\n\n
        • Smart Routing automatic messages<\/strong> sent before the hand-off;<\/li>\n\n\n\n
        • system notifications<\/strong> (events on the interaction).<\/li>\n<\/ul>\n\n\n\n

          Telegram messages support file attachments<\/strong>, images, videos, audio and documents, up to 2 GB<\/strong> per file.<\/p>\n\n\n\n

          Note: the live typing indicator<\/strong> and read receipts<\/strong> are features of the synchronous Chat channel; they are not surfaced for Telegram. Telegram profiles also have no avatar, so the sender is shown by name (or an identifier) without a picture.<\/em><\/p>\n\n\n\n

          5. Available actions during the conversation<\/h2>\n\n\n\n
            \n
          • Reply<\/strong> \u2014 type your message, attach files<\/strong> (from your computer or the documents centre), insert emojis<\/strong>, or send a private<\/strong> (advisor-only) message that the customer does not receive.<\/li>\n\n\n\n
          • Transfer<\/strong> \u2014 from Open the transfer options<\/strong>, route the conversation to a User<\/strong>, a Queue<\/strong>, a Smart Routing<\/strong>, or a Directory<\/strong>.<\/li>\n\n\n\n
          • CRM card<\/strong> and Case<\/strong> \u2014 from the Options<\/strong> menu, create or attach a CRM card or a case to the interaction.<\/li>\n\n\n\n
          • Payment<\/strong> \u2014 from the Options<\/strong> menu, request a secure payment<\/strong> (requires the billing\/payment right).<\/li>\n\n\n\n
          • Custom buttons<\/strong> \u2014 any buttons your organisation has configured for interactions.<\/li>\n<\/ul>\n\n\n\n

            To finish the conversation, you have three distinct actions:<\/p>\n\n\n\n

              \n
            • Close<\/strong> \u2014 you have answered and are waiting for the customer; the interaction moves to Messages pending customers<\/strong> (see section 8).<\/li>\n\n\n\n
            • End<\/strong> \u2014 the exchange is over; the interaction is terminated and archived.<\/li>\n\n\n\n
            • Quit<\/strong> \u2014 you hand the interaction back; it returns to Messages pending<\/strong> in the queue it came from, for another agent to take.<\/li>\n<\/ul>\n\n\n\n
              \"\"<\/figure>\n\n\n\n

              6. Conditional actions<\/h2>\n\n\n\n

              These actions appear only when their conditions are met:<\/p>\n\n\n\n

                \n
              • Qualification<\/strong> \u2014 available when a qualification form is configured on the queue<\/strong> and you have the qualification right.<\/li>\n\n\n\n
              • Script<\/strong> \u2014 available when a script is attached<\/strong> to the interaction and you have the script right.<\/li>\n\n\n\n
              • Start video call<\/strong> \u2014 available when video call is enabled on the queue<\/strong> and you have the right; The customer receives a link<\/strong> in the Telegram conversation and joins the video call by opening it in their browser (the call runs as a web session, not inside Telegram).<\/li>\n<\/ul>\n\n\n\n

                7. The session window<\/h2>\n\n\n\n

                Because Telegram is asynchronous, a conversation is kept alive for the duration of a session window<\/strong> configured on the bot. The window is reset every time the customer sends a new message<\/strong>. Its length is set per bot, up to a maximum of 72 hours<\/strong> (3 days).<\/p>\n\n\n\n

                If the customer sends nothing before the window expires, the interaction is closed automatically<\/strong>. When the customer writes again after that, a new<\/strong> interaction is created and routed again through Smart Routing.<\/p>\n\n\n\n

                8. Messages pending customer reply<\/h2>\n\n\n\n

                When you Close<\/strong> a Telegram conversation while waiting for the customer, it leaves your active interactions and moves to the Messages pending customers<\/strong> tab. As soon as the customer replies, within the session window, it comes back automatically<\/strong> to Messages pending<\/strong>, ready to be picked up and continued.<\/p>\n\n\n\n

                9. Notifications<\/h2>\n\n\n\n

                Sound and visual notifications for the messaging flow are configurable in your user notification settings<\/strong>. For Telegram (as for the other messaging channels), you can be alerted:<\/p>\n\n\n\n

                  \n
                • When a message arrives<\/strong> in one of your active conversations;<\/li>\n\n\n\n
                • When a new message arrives in a queue<\/strong>;<\/li>\n\n\n\n
                • When a message exits a queue<\/strong>;<\/li>\n\n\n\n
                • when the messaging has just ended<\/strong>;<\/li>\n\n\n\n
                • when a participant has left the messaging<\/strong>.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

                  [Reading time: 6 minutes] Overview This article is part of the Messaging pool series. It focuses on the Telegram channel. For the general overview of the pool, see Messaging pool in the Banner. Telegram\u00a0is one of the\u00a0messaging\u00a0channels handled in the Banner. Customers write to you from their Telegram app, through one of your\u00a0Telegram bots, and…<\/p>\n","protected":false},"author":5,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[105],"ht-kb-tag":[],"class_list":["post-6758","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-using-ino"],"_links":{"self":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/6758","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/comments?post=6758"}],"version-history":[{"count":5,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/6758\/revisions"}],"predecessor-version":[{"id":6866,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/6758\/revisions\/6866"}],"wp:attachment":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/media?parent=6758"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-category?post=6758"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-tag?post=6758"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}