How the Bot Stays Connected

You don't need to configure anything for your MemberPass bot to stay connected to Telegram — everything is handled automatically when you complete the bot connection. This page explains how it works, for curiosity's sake and for troubleshooting if things ever get weird.

The short version

When a subscriber sends a message to your bot, Telegram doesn't poll MemberPass for updates. Instead, Telegram pushes each event to MemberPass via a webhook URL. MemberPass processes it immediately and replies through the Telegram Bot API.

That's it — that's the whole story. No polling loops, no delays, no "waiting for the bot to check in." The connection is event-driven.

What MemberPass does automatically

When you paste a bot token during Bot connection and click Activate Bot:

1. MemberPass verifies the token with Telegram.
2. MemberPass registers a secure webhook URL on that bot.
3. From that point on, Telegram sends every event — messages, button taps, new chat members — to that URL.
4. MemberPass handles the event and responds via the Bot API, all within a second or two of the user's action.

The webhook URL points to app.memberpass.net endpoints and includes a project-specific secret so only Telegram's verified payloads are accepted.

What you don't need to configure

• A server — MemberPass hosts the receiving endpoint.
• TLS certificates — Telegram requires HTTPS; MemberPass provides it.
• Message forwarding — the bot token is all Telegram needs; our webhook claims it.
• Polling or cron jobs — the bot reacts in real time to user input, not on a schedule.

When the webhook matters for you

Ninety-nine percent of the time you'll forget the webhook even exists. The moments you might care:

The bot stops responding

If users say the bot has gone silent, a broken webhook is a candidate cause. Things that can break it:

• You revoked or rotated the bot token in BotFather but didn't update it in MemberPass. The stored token no longer authenticates, so MemberPass can't reply. Fix: paste the new token in the bot connection modal.
• The bot was disabled or deleted in BotFather. Telegram stops pushing events to a dead bot. Fix: re-enable it in BotFather, or replace with a new bot.
• Another service is trying to set a webhook on the same bot. Only one webhook can be active per bot — if a competing tool overwrites ours, MemberPass stops receiving events. Fix: disconnect the other service and reconnect the bot in MemberPass.

You rotate the bot token

If you send /revoke in BotFather to generate a new token, MemberPass's stored token is invalidated immediately. Paste the new token in the bot connection modal — MemberPass re-registers the webhook with the new credentials and operations continue.

You temporarily disconnect

Disconnecting a bot tells MemberPass to stop processing events from that bot. Telegram may still push events at the webhook URL, but we ignore them. To re-enable, reconnect the bot.

Security notes

• The webhook endpoint verifies a secret token included in every incoming request from Telegram. Requests without the correct secret are rejected.
• Our servers only store the bot token (encrypted), not the full webhook URL or secret — those are derived at runtime.
• Every webhook request is logged so we can audit unusual activity (rate spikes, malformed payloads, etc.).

Related

• Connect your bot — where the bot token lives.
• Telegram integration — the higher-level mechanics (member add/remove, etc.).
• Troubleshooting — common cross-cutting issues including "bot not responding".