DripTell Guides

Make a Telegram bot part of the same customer operation.

Create or choose the business bot, connect its token securely and test the conversation before sharing the bot with customers.

Last verified
August 24, 2026
For
Workspace owners and Telegram channel administrators
In this guide
  • Protect the bot token
  • Verify the bot identity
  • Test assignment and replies

01

Choose the bot customers should trust

Use a bot owned by the business, with a recognizable name, username and profile. Decide what the bot can answer and where a person must take over before publishing its link.

  • Keep the owner account protected with strong authentication.
  • Use a clear bot description and support expectation.
  • Do not reuse a token across unreviewed tools.

02

Add the token without exposing it

Enter the bot token only in the protected DripTell channel connection. Never paste it into a public document, support screenshot or browser URL. If a token is exposed, revoke it at the provider before issuing a replacement.

03

Start the bot and prove both directions

From a test Telegram account, open the bot, start the conversation and send a message. Confirm it reaches DripTell, assign it and reply. Test a second message after reassignment to prove continuity.

  1. 1

    Start

    Open the published bot identity from a customer account.

  2. 2

    Receive

    Confirm the correct workspace receives the message.

  3. 3

    Reply

    Verify the DripTell reply and delivery state in Telegram.

04

Set an expectation the bot can meet

Make response hours and escalation behavior clear. Use short intake questions and preserve the answers for the human owner instead of asking the customer to repeat them.

  • Keep identity, owner and previous answers together.
  • Escalate unsupported requests to a person.
  • Review abandoned conversations and repeated fallback answers.

05

Check identity, token and delivery in that order

If the channel stops, confirm the customer used the correct bot, then check token validity and DripTell connection state. Preserve timestamps and chat identifiers before rotating a token or reconnecting.