{"id":6781,"date":"2026-08-18T11:34:32","date_gmt":"2026-08-18T09:34:32","guid":{"rendered":"https:\/\/help.ino.cx\/?post_type=ht_kb&p=6781"},"modified":"2026-08-18T11:34:32","modified_gmt":"2026-08-18T09:34:32","slug":"telegram-bot-set-it-up","status":"publish","type":"ht_kb","link":"https:\/\/help.ino.cx\/index.php\/help-center\/telegram-bot-set-it-up\/","title":{"rendered":"Telegram bot – Set it up"},"content":{"rendered":"\n
\"Smart<\/figure>\n\n\n\n

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

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

This article explains how to configure a Telegram bot<\/strong> in the Maker so its messages can be handled as Telegram interactions. For how advisors then handle those conversations in the Banner, see Telegram in the messaging pool<\/strong>.<\/p>\n\n\n\n

Connecting a Telegram bot<\/strong> lets your organisation receive the bot’s Telegram<\/strong> messages and route them through a Smart Routing<\/strong>, exactly like the other messaging channels. Configuration is done in the Maker, under Entry points > Telegram bots<\/strong>.<\/p>\n\n\n\n

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

1. Prerequisites<\/h2>\n\n\n\n

This section requires the Telegram bots<\/strong> right. Reading the list needs the read<\/strong> right; adding, editing and deleting a bot need the create<\/strong>, modify<\/strong> and delete<\/strong> rights in the role.<\/p>\n\n\n\n

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

To connect a bot you need:<\/p>\n\n\n\n

    \n
  • a Telegram bot and its token<\/strong>. You create the bot in Telegram with @BotFather<\/strong>, which gives you a bot token<\/strong> to paste into the configuration;<\/li>\n\n\n\n
  • a messaging Smart Routing<\/strong> already created, to which the bot will be linked. A bot with no Smart Routing linked has its incoming messages ignored<\/strong>.<\/li>\n<\/ul>\n\n\n\n

    2. Adding a bot<\/h2>\n\n\n\n
      \n
    1. Go to Entry points > Telegram bots<\/strong>.<\/li>\n\n\n\n
    2. Click New Telegram bot<\/strong>.<\/li>\n\n\n\n
    3. Fill in the fields below, then save with Add the Telegram bot<\/strong>. On success you see “The bot has been successfully created.”<\/em><\/li>\n<\/ol>\n\n\n\n

      The available fields are:<\/p>\n\n\n\n

        \n
      • Name<\/strong>: the display name of the bot (required).<\/li>\n\n\n\n
      • Telegram bot token<\/strong>: the token provided by @BotFather (required). It is entered in a masked field, with a button to reveal it.<\/li>\n\n\n\n
      • Session duration<\/strong>: the delay between two messages during which they are considered to belong to the same interaction<\/strong>. It is entered in seconds<\/strong> and must be between 10 seconds and 259 200 seconds<\/strong> (72 hours \/ 3 days); the default is 259 200. Each new customer message resets this window; if the customer sends nothing before it expires, the interaction is closed and a later message starts a new one.<\/li>\n\n\n\n
      • Time zone<\/strong>: the time zone applied to the bot, or By default<\/em> (the customer account time zone).<\/li>\n\n\n\n
      • Language<\/strong>: the language used by the Smart Routing actions, or By default<\/em>.<\/li>\n\n\n\n
      • Smart routing<\/strong>: the messaging Smart Routing that qualifies and distributes the bot’s incoming messages. When one is selected, choose its Smart routing version<\/strong>: Production<\/strong> or Test<\/strong>.<\/li>\n\n\n\n
      • End-of-interaction Smart routing<\/strong>: an optional Smart Routing run at the end of the interaction, also with a Production<\/strong> \/ Test<\/strong> version.<\/li>\n<\/ul>\n\n\n\n

        Note: the Smart routing must already exist to appear in the list, so create it first. Selecting it here is the only step needed to route the bot’s messages: there is nothing to configure on the Smart Routing side.<\/em><\/p>\n\n\n\n

        3. The list of bots<\/h2>\n\n\n\n

        Each bot appears as a row. The columns are:<\/p>\n\n\n\n

          \n
        • Name<\/strong>: the bot name.<\/li>\n\n\n\n
        • Time zone<\/strong>: the bot’s time zone, or By default<\/em>.<\/li>\n\n\n\n
        • Language<\/strong>: the language used by the Smart Routing actions, or By default<\/em>.<\/li>\n\n\n\n
        • Session time<\/strong>: the configured session window (see section 2).<\/li>\n\n\n\n
        • Smart routing<\/strong>: the linked messaging Smart Routing, with a Production<\/strong> or Test<\/strong> tag.<\/li>\n\n\n\n
        • End-of-interaction Smart routing<\/strong>: the Smart Routing run when the interaction ends, if one is linked.<\/li>\n<\/ul>\n\n\n\n

          4. Managing a bot<\/h2>\n\n\n\n

          The actions below are available from a bot’s row in the list.<\/p>\n\n\n\n

          4.1. Editing a bot<\/h3>\n\n\n\n

          Click Modify<\/strong> to reopen the bot’s settings. You can change any of the fields described in section 2, then save with Modify the Telegram bot<\/strong>.<\/p>\n\n\n\n

          4.2. History and tags<\/h3>\n\n\n\n

          Each row has an Options<\/strong> menu (the cog icon) that gives access to:<\/p>\n\n\n\n

            \n
          • History<\/strong>: the record of changes made to the bot, including who created it and who last modified it.<\/li>\n\n\n\n
          • Tags<\/strong>: a side panel to attach or detach tags<\/strong> on the bot, to organise and filter your entries. Managing tags requires the modify<\/strong> right.<\/li>\n<\/ul>\n\n\n\n

            Note: a Dependencies<\/strong> entry also appears in this menu when the bot is referenced by other elements.<\/em><\/p>\n\n\n\n

            4.3. Deleting a bot<\/h3>\n\n\n\n

            Use the Delete<\/strong> row action to remove a bot. A confirmation is asked, and the action cannot be reversed. Once deleted, the bot no longer receives messages. You can also select several bots and delete them together.<\/p>\n","protected":false},"excerpt":{"rendered":"

            [Reading time: 3 minutes] Overview This article explains how to configure a Telegram bot in the Maker so its messages can be handled as Telegram interactions. For how advisors then handle those conversations in the Banner, see Telegram in the messaging pool. Connecting a Telegram bot lets your organisation receive the bot’s Telegram messages and route them…<\/p>\n","protected":false},"author":5,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[107],"ht-kb-tag":[],"class_list":["post-6781","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-configuring"],"_links":{"self":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/6781","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=6781"}],"version-history":[{"count":5,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/6781\/revisions"}],"predecessor-version":[{"id":6793,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/6781\/revisions\/6793"}],"wp:attachment":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/media?parent=6781"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-category?post=6781"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-tag?post=6781"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}