Telegram Bot API 10.0 Guest Mode: What Channel Operators Need to Know

Telegram Bot API 10.0 Guest Mode: What Channel Operators Need to Know

TL;DR. Telegram Bot API 10.0 (May 8, 2026) shipped Guest Mode: any bot with the setting enabled can now reply once when a user tags its @username in a chat it never joined — no invite, no admin rights. A separate bot-to-bot toggle lets bots respond to each other for autonomous multi-agent workflows. Neither replaces an admin-installed automation layer — Guest Mode is stateless and one-reply-only by design. For channel operators, the news is less "install this" and more "here's a new primitive your community will start expecting."

Curious how this fits your channel's existing automation? See what Autogram's scheduling and multi-channel tools already handle.

What Bot API 10.0's Guest Mode Actually Does

Photo by RDNE Stock project on Pexels

Before Bot API 10.0, a bot could only see and respond to messages in chats it had actually joined — as a member of a group, or an admin bot on a channel. That boundary is why cross-bot mashups and "just ask the AI in any group chat" experiences never quite worked on Telegram: the bot had to be added first.

Guest Mode, shipped May 8, 2026 (Telegram Bot API changelog), removes that requirement for a narrow, well-fenced interaction. Tag a bot's @username in any chat — even one it has never joined — and if that bot has Guest Mode enabled, it receives a dedicated update and can send exactly one reply, visible to everyone in the chat.

On the API side, Bot API 10.0 added:

• supports_guest_queries — a new field on User, so clients and other bots can tell whether a given bot accepts guest queries
• guest_bot_caller_user, guest_bot_caller_chat, and guest_query_id — new fields on Message that carry the context of who tagged the bot and from where
• SentGuestMessage and the answerGuestQuery method — how a bot actually sends its one guest reply

Bot API 10.0 also landed three unrelated changes worth a one-line mention: deleteAllMessageReactions and deleteMessageReaction (reaction cleanup without deleting the message), the minimum poll-option count dropping from 2 to 1, and a new LivePhoto type for sendLivePhoto. None of those are the headline here — Guest Mode and bot-to-bot are.

How Guest Mode Actually Works — and What It Deliberately Can't Do

Photo by El Jundi on Pexels

Telegram's own developer documentation (core.telegram.org/bots/features) is explicit that Guest Mode is scoped tightly on purpose:

That statelessness is the load-bearing design decision. Telegram built Guest Mode for one-off "ask the bot" moments inside a conversation humans are already having — not as a backdoor for a bot to quietly monitor a group it was never invited to. A developer enables it per-bot from BotFather's Mini App, under that bot's settings.

Bot-to-Bot Communication: The Multi-Agent Piece

Guest Mode governs a human tagging a bot. Bot-to-bot communication — a separate toggle, also enabled per-bot in BotFather — governs a bot messaging another bot, and it's aimed squarely at agentic workflows: a "contributor" bot requesting a code review from a "reviewer" bot, or a research bot handing a summarization task to a specialist bot, all playing out as visible, auditable messages in a chat humans can still read.

Telegram's own framing is that a group no longer has to be a place where "humans talk and bots merely respond" — it can become a workspace where multiple bots coordinate in the open. The catch developers are explicitly warned about: because two bots can message each other, an unguarded loop can talk to itself forever. Telegram's guidance is blunt — implement your own termination safeguards, because the platform won't stop a runaway exchange for you.

For a channel operator, bot-to-bot is mostly invisible infrastructure rather than something you configure directly — it's what makes it possible for, say, a moderation bot to consult a classification bot before acting, without a human relaying messages between them.

Where This Actually Changes Anything for Your Channel

Photo by Ivan S on Pexels

Worth being honest about what Guest Mode is not: it's not a scheduling tool, not a way to auto-post, and not a substitute for a bot that's actually a member of your channel with full context. Autogram doesn't call Guest Mode or bot-to-bot APIs today — and if an article tells you otherwise about any scheduling tool, be skeptical.

What it does change is audience expectation. Once a handful of popular AI bots support Guest Mode, members of your community will start tagging bots inside your channel's discussion group expecting a reply — the same reflex people already have with @ mentions on other platforms. That's a UX shift worth planning for even if you never touch the API yourself: it's one more reason the bots and automations you do run (like scheduled posts, welcome flows, or engagement prompts) benefit from being consistent and predictable, since guest-mode bots are now part of the same conversational surface.

If you're already running Autogram to handle scheduling, multi-channel fan-out, or AI-drafted posts, none of that changes — Guest Mode and bot-to-bot operate at the individual-message level inside group chats, not the channel-broadcast level Autogram automates. But if you're evaluating a custom bot build for your community, it's now a real design option worth knowing exists.

What Shipped Next: Bot API 10.1 and 10.2

Telegram didn't stop at 10.0. Two more releases followed within ten weeks, both worth flagging so you don't mistake this article for the full picture:

• Bot API 10.1 (June 11, 2026) added sendRichMessage for document-grade formatted posts, plus answerChatJoinRequestQuery — the primitive behind "Guardian Bot" join-request screening.
• Bot API 10.2 (July 14, 2026) added ephemeral messages visible only to specific users, and Telegram's first Community support linking supergroups, channels, and bots together.

Both deserve their own deep dive; this article stays scoped to what 10.0 actually shipped.

Related reading

• Telegram Managed Bots: What We Know Before the April Launch — the platform-hosted bot surface Guest Mode builds on top of
• Telegram Super Channels: The Multi-Author Setup Guide for Brand Teams — another 2026 platform addition aimed at teams, not solo operators
• AI-Powered Telegram Content Bot: Setup Guide for 2026 — for when you want a bot that's a full channel member, not a stateless guest

FAQ

What is Telegram Bot API 10.0 Guest Mode?

Guest Mode, shipped May 8, 2026, lets a bot receive a message and send exactly one reply in a chat it isn't a member of, triggered when a user tags the bot's @username. It carries no access to chat history or the participant list.

How do I enable Guest Mode for my bot?

A bot developer turns it on in BotFather's Mini App, under that specific bot's settings. It's opt-in per bot — existing bots don't gain guest-query behavior automatically.

What can't a guest bot do?

It can't read message history, see who else is in the chat, persist any memory between separate mentions, or send more than one reply per guest query. Up to three guest bots can be tagged in a single message.

How is bot-to-bot communication different from Guest Mode?

Guest Mode is triggered by a human tagging a bot. Bot-to-bot communication is a separate, also opt-in feature that lets one bot message another directly — the primitive behind multi-agent workflows like a bot requesting a review from a specialist bot.

Does Autogram support Guest Mode or bot-to-bot bots?

Not today. Autogram's automation operates at the channel-broadcast level — scheduling, multi-channel posting, AI-drafted content — which is a different surface from the per-message guest interactions Bot API 10.0 introduces.

What came after Bot API 10.0?

Bot API 10.1 (June 11, 2026) added rich-message formatting and join-request screening; Bot API 10.2 (July 14, 2026) added ephemeral messages and initial Community support. Neither changes how Guest Mode itself works.

Bottom line

Explore Autogram's automation. Connect your first channel to start 7 days of Solo access, with a $1 AI budget and no card required.

Image credits

• Hero: Photo by RDNE Stock project on Pexels
• Inline 1: Photo by El Jundi on Pexels
• Inline 2: Photo by Ivan S on Pexels