Telegram bot approval: where your sales bot should stop and ask you

Telegram bot approval means the bot stops at a moment you picked and waits for you to tap yes or no before it goes on. Scalegram is the Telegram CRM for IBs and forex affiliates, and its Ask Me block does exactly that: the bot runs the sale on its own and pauses only where you placed a checkpoint, such as a payout, a discount or a stranger claiming a funded account.

The hard part is choosing where the checkpoints go. Put one on every step and you are back to answering every lead yourself. Put none anywhere and the bot makes calls you would have made differently.

Why a fully manual bot defeats the point

Most owners start by approving everything. The bot drafts, they read, they send. It feels safe for about a week. Then a lead writes at 03:00, the draft waits until 09:00, and by then the lead has joined someone else's group.

The reply time is what a cold lead judges you on. A bot that needs you for every message has the same reply time as you do. The only thing it saved you is typing.

Scalegram's autopilot is built the other way round. Started once, the bot answers every message in the language it arrived in, decides who is ready, sends your broker link, asks for the email or account number, checks it against the broker's own records over a read-only API, opens the paid group, files the client and follows up on whoever went quiet. Approval is optional and placed by hand. Everything you did not mark completes without you.

How an Ask Me checkpoint works

You draw the conversation as a flow of triggers, conditions, questions and follow-ups. An Ask Me block is one more step in that flow. When a conversation reaches it, the flow stops and the bot asks you in your own Telegram. You tap yes or no. The flow carries on down the branch you chose.

Two things make this workable at volume. The question comes to you in Telegram, where you already are, so there is no dashboard to keep open. And it is one tap, so you can answer it standing in a queue.

Where to keep the final yes

A good checkpoint guards a decision that is expensive to get wrong and rare enough that tapping it does not become a job. Four places fit that description for most IBs and affiliates.

Payouts

Any step where money or something with money value leaves your side: a cashback, a rebate you pass on, a bonus you promised a referrer. The bot gathers the details in the conversation. You press the button that says it goes out. If a customer has worded a request cleverly, this is where you catch it.

Discounts and exceptions

Leads ask for a better deal. Some deserve one. An Ask Me block on that step stops the flow until you decide whether this person gets the exception. What you should not do is write a discount rule into the bot's description and hope it applies it only to the right people.

A stranger claiming a funded account

If you work with prop firm affiliates, you will meet someone who says they already passed a challenge and should be in the funded traders' group. Scalegram can look that email up in the prop firm CRM and see whether a funded account is live. When the records confirm it, the bot can grant access with no help from you. When they do not, or when the person is not in your referral list at all, an Ask Me block hands the call to you instead of a flat refusal. The walkthrough in how to verify a broker deposit automatically shows what the lookup returns.

Anything outside the offer

A partnership pitch, a media request, a lead asking for something you do not sell. The bot can hold these at a checkpoint rather than improvise an answer. For the conversations that need a person for longer than one tap, the bot can hand over to a human and mute itself.

Where a checkpoint only slows you down

Some steps look risky and are not, because the check already happens against a source you trust.

The group access row is where owners hesitate most. Once the deposit is read from the broker's own records, a person tapping yes adds nothing the records did not already say. Our guide to VIP group access after a deposit covers that flow step by step.

What Telegram does with a join request

Much of this happens around the paid group, so it helps to know how Telegram handles the door. An invite link can be set so that people joining through it need approval by chat administrators; the Bot API marks that with a creates_join_request field on the ChatInviteLink object. A bot can then approve or decline each request with the approveChatJoinRequest and declineChatJoinRequest methods, and for either one the Bot API says the bot must be an administrator in the chat with the can_invite_users right.

One detail matters for timing. The same Bot API reference says a bot can use the join request's user_chat_id for five minutes to send messages until the request is processed, assuming no other administrator contacted the user. A pending request that waits hours for a human misses that window. That is one more reason to let verified deposits through without a tap and keep your attention for the cases that need it.

If you have built your own bot, you will know Telegram's inline keyboards, whose buttons do not send messages to the chat when pressed. A yes/no approval in a chat is the kind of interface they are made for. In Scalegram you do not build any of that; you drop an Ask Me block into the flow.

What the bot can never be talked into

A checkpoint is a decision you keep. It is not the only thing standing between a customer and data they should not see. Every message Scalegram sends is checked before it goes out: API keys and tokens, the bot's own instructions in any wording, and any email or account number the conversation cannot account for are removed. So even with no checkpoint on a step, one customer does not receive another customer's details, whatever they ask.

That separation is useful when you plan checkpoints. You do not need one on every message "in case the bot leaks something". Keep them for judgment calls.

A starting setup

If you are setting up a bot this week, start small and add checkpoints only where you catch yourself wanting to intervene.

1. Write the product description in plain sentences: what you sell, who it is for, what the steps are, what you do not answer.
2. Connect your broker's IB portal or prop firm CRM under Integrations with a read-only API key, so deposits are checked against the source.
3. Draw the flow: answer, qualify, link, ask for the email, verify, open the group, file the client, follow up.
4. Place Ask Me blocks on payouts and exceptions. Leave the rest open.
5. Read the bot's live conversations in the Chats tab for the first few days. Each time you wince, ask whether that step needs a checkpoint or a better line in the description. It is usually the description.

You can also ask the bot in your own Telegram what happened today, what is queued or what broke, and it answers from the real data. That is how most owners find out which checkpoints they actually use and which ones they tap yes on every time. A checkpoint you always approve is a checkpoint to remove.

For how the bot splits the setter and closer work between itself and you, see the AI setter and closer on Telegram. The full flow is on how Scalegram works, and every feature, Ask Me included, is on both plans on the pricing page.

Sources

• Telegram Bot API, Telegram, checked 29 September 2026
• Telegram Bot Features, Telegram, checked 29 September 2026

Put your yes where a mistake costs you. Let the broker's records answer everything else.

— The Scalegram Team

Frequently asked questions