Build a Telegram Customer Support Bot in 10 Minutes (No Code)

Why Telegram for support?

Telegram is one of the cheapest, lowest-friction channels you can give a customer. No ticketing app to install, no email to write, no chat widget to load. They open Telegram, message your bot, and get an answer.

Most teams skip it because the setup feels like infrastructure work: bot tokens, webhook servers, message queues. With GenMB chat agents none of that exists. You describe the agent, write its instructions, paste a Telegram token, and ship.

What you'll build

By the end of this 10-minute tutorial you'll have:

• A Telegram bot that answers product questions the way you told it to
• Memory so it remembers each user across conversations
• A "talk to a human" hand-off that emails you the conversation
• A daily summary email of every conversation it had

Total cost on any paid GenMB plan, from Pro: 1 credit to create the agent, 1 credit per response.

Step 1: create the agent (90 seconds)

Open the GenMB workspaces page → "Assistants" tab → New assistant. Pick the "Customer support" preset, or describe what you want in plain English:

"A friendly support agent for Acme that answers product questions, escalates angry users, and remembers what each customer asked before."

GenMB generates the agent's system prompt, personality, and skill stack. You can review the YAML it produces and tweak any field before deploying.

Step 2: write the agent's instructions (2 minutes)

This is where the agent learns your product. Open the agent's prompt and persona configuration and write, as plain text, how it should behave and what it should say. Paste the answers you already give people: the refund policy in your own words, the export steps, the pricing tiers, the phrases you never want it to use.

Be specific about the edges. "If someone asks about enterprise pricing, tell them to email sales@acme.com" is a rule the agent will follow. "Be helpful" is not.

For anything you did not write down, give the agent skills instead of text. Turn on web search so it can look things up, and connect it to your app's data through the SDK so it can answer from live records rather than from a guess. If it still does not know, the honest instruction is to say so and hand off, which is Step 4.

Step 3: connect Telegram (60 seconds)

In Telegram:

1. Message @BotFather → /newbot
2. Pick a name and username
3. Copy the token (123456:ABC-DEF...)

Back in GenMB → "Channels" tab → Telegram → paste the token → Connect. The agent starts polling for messages within seconds.

That's it. You can DM the bot now and get answers in the voice you configured.

Step 4: add the hand-off skill

Edit the agent's skills. Toggle on `escalate_to_human` and configure the destination email. Now the agent recognizes phrases like "I want to speak to someone" or sustained negative sentiment and automatically pings you with the conversation transcript.

You don't need to write any logic for this. The skill is built-in.

Step 5: schedule a daily summary

Workflows tab → New workflow → "Scheduled". Set cron to 0 9 * * * (9am every day). Add nodes:

1. Database query → SELECT * FROM assistantMessages WHERE created_at > now() - interval '1 day'
2. AI generate → "Summarize the most common topics customers asked about today in 5 bullets."
3. Send email → To: you@yourcompany.com

Activate the workflow. Every morning you wake up to a one-glance brief of yesterday's support volume.

Iteration tips

After a week, look at the conversation logs in the assistant detail panel. The two most useful patterns:

1. Topics the agent declined → expand the instructions to cover them, or give it a skill that can.
2. Repeated questions → these are your top FAQ candidates. Pin them to your help center.

What this replaces

Hosted support suites like Intercom or Zendesk bill per seat or per resolution, and what you get is a chat widget on the website. With GenMB you get a real Telegram bot, answers grounded in the instructions and data you gave it, hand-off, and daily reporting, for the cost of a Pro plan and the credits you actually use.

The difference is that you own the conversation history (it's in your GenMB workspace) and you can extend behavior with workflows that competitors gate behind add-on pricing.

Ship it

Try the Telegram bot template to start from a working agent in one click.