Telegram FAQ Bot

What it does

Answers questions sent to your Telegram bot from your own FAQ, and hands anything unclear to a person.

• Starts within seconds of each message to your Telegram bot.
• AI answers using only the FAQ you paste in, in the person's language, and rates how sure it is.
• It remembers the last 5 messages and answers sent in each chat for 30 days, so a follow-up like “and on Sundays?” is understood.
• Clear FAQ answers are sent straight back in the chat.
• Anything else (personal orders or bookings, complaints, requests for a person, questions the FAQ doesn't cover) gets a short holding message and is posted to your Slack channel with a draft answer.
• A teammate writes or fixes the answer in Reviews and approves it; the bot sends it as a reply in the chat.

What it needs

• A paid plan (agents run live on paid plans).
• An AI provider key (Settings → AI Providers).
• A Telegram bot (free, from @BotFather) and Slack, connected in Settings → Integrations.
• Your FAQ as text.

What it doesn't do

• It answers only from the FAQ you paste in: no document or website search.
• Its memory is short: only the last 5 exchanges per chat (in a group, the whole group shares one), forgotten 30 days after the last one, and only answers that were sent (not holding messages or rejected drafts).
• It doesn't look up orders, bookings or accounts; those questions go to a person.
• In groups it only sees commands and replies to the bot unless you turn off privacy mode in @BotFather.
• One bot per workflow: Telegram delivers a bot's messages to a single webhook.

Availability and plans

Included free on the Enterprise plan; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.

Before you start

• A paid plan: agents run live, and the Free plan only runs Dry Runs.
• An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
• These apps, connected in Settings → Integrations: Telegram and Slack.
• The app it watches, connected in Settings → Integrations (the agent starts from an app event).
• About 15 minutes.

• Bring your own AI key
• Telegram (live)
• Slack (live)

Set it up step by step

Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.

1. Connect your AI provider

The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.

• Connect your AI provider

2. Connect Telegram

Create a bot with @BotFather (/newbot) and paste its token in Settings → Integrations → Telegram.

• Connecting Telegram

3. Connect Slack

Connect the Slack workspace your team uses (Settings → Integrations → Slack).

• Connecting Slack

4. Paste your FAQ

Open “Answer from your FAQ” and replace the placeholder with your FAQ.

5. Pick your bot

Pick your bot on the trigger, “Send the answer” and “Tell the person a teammate will reply”.

6. Pick the Slack account and channel

Open “Hand off to a person in Slack” and pick your account and channel. Invite the app to private channels first (/invite @Fluxo Flow).

7. Test it with Dry Run

Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.

• Dry Run vs Run

8. Switch the trigger on

Open the trigger and click “Activate app trigger”: Fluxo Flow registers itself as your bot's webhook.

How it works

The agent is a normal workflow with 11 steps (1 AI step, with a person approving in Reviews). You can open, edit and monitor it like any other workflow.

• New message to your bot — Starts on “New message to the bot” in Telegram (an app event). Starts a run within seconds for each message people send your Telegram bot.
• Recall the conversation — Recalls what it remembered earlier (memory “telegram-faq-bot”). Reads the last 5 messages and answers in this chat (remembered for 30 days after the last one). Nothing is found for a new chat.
• Answer from your FAQ — AI step (runs on your AI provider key). AI answers the question using only the FAQ you paste in (with the earlier messages in the chat for context), and says how sure it is. Anything the FAQ doesn't clearly cover goes to a person.
• Answered by the FAQ? — Decision: picks the branch to follow. Clear FAQ answers are sent straight back; everything else goes to a person in Slack and Reviews.
• Send the answer — Telegram: Send a message. Branch: FAQ answer / Approved. Replies in the person's chat, quoting their message.
• Remember this exchange — Remembers it for later runs (memory “telegram-faq-bot”, kept 30 days). Saves the message and the answer sent with the earlier ones (the last 5 are kept, for 30 days after the last one). Holding messages and rejected answers aren't saved.
• Answered — Kept in the run history. The run history keeps the question and the answer sent.
• Tell the person a teammate will reply — Telegram: Send a message. Branch: Needs a person. Sends a short “we've passed this to the team” message so the person isn't left waiting in silence.
• Hand off to a person in Slack — Slack: Post a message. Posts the question, why it needs a person and the draft answer to your Slack channel, pointing to Reviews.
• Handed off — Kept in the run history. The run history keeps the question and the hand-off.
• A person answers — A person approves or rejects it in Reviews (the run waits). Branch: Needs a person. A teammate writes or corrects the answer (json.answer) in Reviews and approves it; the bot sends it. Reject to answer another way.

Test it with Dry Run

Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live. The sample has the same shape as a real event from the app.

Sample data fields

text, update_id, message_id, caption, chat_id, chat_type, chat_title, from_id, from_username, from_first_name, date, photo_file_id, document_file_id, contact_phone, location.

• Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.
• Approval steps use the Dry Run decision you pick in the step's settings (approved, rejected or timeout), so you can try each branch.
• Memory steps don't read or write stored memory: a recall finds nothing, and a save only shows what it would store.

Go live

• Open the trigger and click “Activate app trigger”: Fluxo Flow registers itself as your bot's webhook.
• Activating the app trigger needs the trigger's connected account. The first check only remembers what's already there, so older items don't start runs; the same item never starts two runs.
• The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
• When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.

• App event triggers
• Switching a trigger on (Activation)

Questions

Can it make things up?

It's instructed to use only your FAQ, and anything it isn't sure about goes to a person instead of being answered automatically.

Does it remember the conversation?

Briefly: it remembers the last 5 messages and answers sent in each chat, for 30 days after the last one, so follow-up questions make sense. Answers still come only from your FAQ.

Troubleshooting

• “No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
• A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
• An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
• Slack says the app isn't in the channel: in Slack, type /invite @Fluxo Flow in that channel (always needed for private channels).
• No runs start: activate the app trigger with a connected account. Only items created after activation start runs.
• A run shows as paused: it's waiting for someone in Reviews to approve or reject it.
• A step failed: open the run in History and check that step in the Trace tab for the error and what it received.

• Debugging failed runs
• Error messages
• Get help