volbor

Looking for something?

↑↓navigateEnteropenEscclose

Choose language

Get started

Telegram: Connect Your Channel in the Dashboard and Run a Test

This guide does not replace the connection screen inside your volbor workspace, nor does it replicate third-party messenger UI step-by-step, as their labels change frequently. The rule of thumb here is simple: a channel is officially connected only when a message sent from an external account appears in your Inbox and your agent reply from the dashboard appears back in that same chat thread.

Until this round-trip test succeeds, do not share your bot link with customers.

Get startedLearn more
  1. 01
    Bot created, but dashboard doesn't see it

    in messenger, the bot replies with silence or outdated text, and your volbor feed remains empty.

  2. 02
    Two bots running on the same workflow

    an old auto-responder and the new channel send competing replies to the customer.

  3. 03
    Test sent from the bot administrator account

    it looks like an incoming customer message, but it is actually routed as an internal admin loop.

  4. 04
    Channel launched straight into live ads

    the first real customer arrives before anyone verifies two-way message delivery from the dashboard.

Common Pitfalls When Connecting Telegram

  1. 01

    Bot created, but dashboard doesn't see it

    in messenger, the bot replies with silence or outdated text, and your volbor feed remains empty.

  2. 02

    Two bots running on the same workflow

    an old auto-responder and the new channel send competing replies to the customer.

  3. 03

    Test sent from the bot administrator account

    it looks like an incoming customer message, but it is actually routed as an internal admin loop.

  4. 04

    Channel launched straight into live ads

    the first real customer arrives before anyone verifies two-way message delivery from the dashboard.

Core Connection Steps

  1. 01

    1. Open the channel settings in your dashboard

    In your dashboard, select Telegram integration and follow the setup wizard displayed by volbor. If the screen asks for an API token or verification, retrieve it from the location indicated by the wizard and paste it back in. Do not search for tokens in this article: they are omitted intentionally.

  2. 02

    2. Disable any existing auto-responders in this channel

    If another service is currently responding via this bot or an adjacent bot, turn it off before testing. Otherwise, you won't know which system sent the reply. See migration guide if you still need the old tool for historical records.

  3. 03

    3. Send a message from a personal account that doesn't manage the bot

    Send a short text message without attachments. It must appear in the Unified Inbox. If it does not appear, stop and check troubleshoot delivery. Do not connect a second channel "for comparison" until the first one is working.

  4. 04

    4. Reply from the dashboard

    The reply must appear in Telegram on the account you used to send the test. After that, have a colleague repeat the exact same test. Only then should you share the link with customers.

What to Verify During Your First Week

Repeated inquiries from the same user, empty or media-only messages, and questions not covered in the welcome flow. A repeat inquiry should not create a duplicate ticket if your dashboard merges conversations: verify from the customer's perspective that everything remains in a single chat. Do not promise file attachments or voice note support in your welcome message unless your agents can reliably view and answer them during testing.

Frequently Asked Questions

Where do I get the bot token?

The connection screen in your dashboard provides exact instructions on where to copy it. This article does not duplicate external interface buttons: if on-screen instructions differ, always follow the dashboard screen.

Can I connect an existing bot?

Only if your dashboard flow supports it and the previous service is no longer actively responding. Two active auto-responders on the same bot will confuse customers with conflicting answers.

Do I need a website widget if I have Telegram?

Not if your customers already reach out via Telegram. The web widget is designed for website traffic. It is a secondary step, not a replacement for channel verification.

What if the test is visible in Telegram but missing from the Inbox?

The channel is active for the customer, but disconnected for your team. Do not drive customer traffic yet. Review message delivery and connection status rather than welcome copy.

Do I need an AI knowledge base bot live on day one?

No. First, establish reliable human agent replies from the dashboard. Automated AI answers should be enabled only after two-way round-trip messaging is proven stable.

Helpful Resources & Related Solutions

  • Quick StartWhy it matters: Follow a structured first-day rollout sequence, not just channel setup.
    The risk without it: Telegram gets connected without verifying Inbox routing.
  • Unified InboxWhy it matters: Centralize incoming messages where your team actually responds.
    The risk without it: The bot exists in Telegram, but conversations never reach a shared team feed.
  • Message DeliveryWhy it matters: Troubleshoot scenarios where test messages fail in either direction.
    The risk without it: Assuming the channel works simply because a "Connected" badge is green.
  • Platform MigrationWhy it matters: Deactivate legacy auto-responders before running new tests.
    The risk without it: Customers receive two conflicting, overlapping automated replies.
  • Chatbot BuilderWhy it matters: Add automated recurring responses after verifying live handoff.
    The risk without it: Agents waste hours on identical repetitive queries despite a working channel.
  • Launch PlanWhy it matters: Never publish a bot link until a queue owner is assigned.
    The risk without it: The first inbound customers arrive in a channel with nobody on duty.