A Telegram VIP group should open on its own the moment a deposit clears, and stay shut until then. That takes two Telegram features working together, a request-to-join invite link and a bot with the right to approve requests on it, plus a check that runs before the approval instead of after. Scalegram is the Telegram CRM for IBs and forex affiliates that wires the three together: the bot checks the deposit against the broker's own records, then approves the join request itself, at any hour, with no admin watching a queue.
Why a human at the door does not scale
The usual setup is an open invite link pasted in a bio or a landing page. Anyone with the link is in the group the second they tap join. The IB then has to sort real depositors from people who never opened a broker account, which means checking a screenshot after the fact and removing whoever should not have been let in, one profile at a time.
A request-to-join link flips the order. The person asks to join, an admin (or a bot standing in for one) decides, and nobody is a member until that decision is made. The gate moves from after the fact to before it, which is the only place a deposit check is worth running.
The Telegram feature underneath it
Telegram's Bot API documents a creates_join_request parameter on createChatInviteLink: "True, if users joining the chat via the link need to be approved by chat administrators." Set it, and the link stops adding members directly; it queues a request instead.
Two methods handle what happens next. approveChatJoinRequest is described as a method where "the bot must be an administrator in the chat for this to work and must have the can_invite_users administrator right", and returns true on success; declineChatJoinRequest works the same way in the other direction. Both take just a chat id and a user id, which is what a bot needs to act on a request without a human opening the chat.
None of that requires custom infrastructure. It is a standard part of the Bot API, and any Telegram CRM that grants access after a check is calling these same three methods under a different label.
One link per click instead of one link for everyone
The same documentation page gives createChatInviteLink a member_limit parameter, "the maximum number of users that can be members of the chat simultaneously after joining the chat via this invite link", capped at 99,999, with the note that it cannot be combined with creates_join_request. Telegram lets a bot mint any number of separate invite links for the same group, each with its own name and its own limit, which is what makes a link specific to one ad, one campaign or one visitor rather than shared by everyone who sees the same post.
Scalegram uses that per-link property for tracking rather than for the join-request gate itself: a tracked link carries UTM tags and reads fbclid, gclid, ttclid and sccid off the click, and every subscriber that link brings is reported server side, broken down by source, medium, campaign and creative. Pair a distinct tracked link with each ad and every join carries the campaign that paid for it, before the request even reaches the deposit check. Meta ads Telegram conversion tracking covers the reporting half of that.
Where the deposit check sits in the sequence
Turning on admin approval only moves the decision to a human tapping accept or decline in the group's request bar, which is still a person reading a screenshot unless something else feeds that decision. In Scalegram the bot is the administrator standing at that door, and the decision runs off the broker's own records rather than a claim in the chat:
- The lead asks about the group and gets the broker link, in whatever language they wrote in.
- Once they say the account is open, the bot asks for the email or account number they registered with.
- The bot looks that email up in the broker's IB portal or the prop firm CRM over a read-only API and reads back what the records say: account found, deposit completed, the amount.
- A deposit that meets the rule the IB set triggers the join request approval. No deposit yet gets a plain answer and a queued follow-up instead of a decline that shuts the door for good.
- The client card updates on its own: UID, email, broker, deposit, a dated note, and the stage moves to Deposited.
The mechanics of that lookup, and why a read-only, affiliate-scoped API key is the part brokers will actually issue, are in how to verify a broker deposit automatically. This article is about the door; that one is about the proof the door checks.
What the IB still gets to decide
Not every knock at the door is routine. A stranger claiming a funded account, a deposit sitting just under the minimum, someone asking for an exception, these are the moments worth a human's attention rather than a rule. Scalegram calls that an Ask Me block: placed on one step, it holds the flow for a single yes or no tap in the owner's own Telegram, and everything not marked that way completes without anyone watching. The approval itself still runs through the same approveChatJoinRequest call; only the decision that triggers it moved from the bot to a tap.
No manual admin work left
Once the link requires approval and a bot holds the invite right, there is nothing for a human to do at the door on the normal path. No admin refreshing a request list at midnight, no cross-checking a screenshot against a portal open in another tab, no forwarding the link to someone who already deposited an hour ago and is still waiting. The client card, the pipeline stage and the group membership move together because one check produced all three. Telegram CRM for IBs covers what else lives on that card once someone is in.
Setting it up on an existing group takes three changes: switch the group's primary invite link, or mint a new one, with join requests turned on; add the bot as an administrator with the invite right; and connect the broker's read-only API key under Integrations so the bot has something to check against. The IB CRM guide lists what else an IB's side of the funnel needs to track. Lite at $99 a month covers one bot, one Telegram account and one tracked link; the full plan at $999 a month removes every count. The pricing section has both.
If leads are still asked to screenshot a deposit before someone lets them in by hand, that is the piece to replace first. Sign in, connect the group with a request-to-join link, and let the check decide who gets approved.
Sources
- createChatInviteLink, Telegram Bot API, Telegram, checked 22 September 2026
- approveChatJoinRequest, Telegram Bot API, Telegram, checked 22 September 2026
- declineChatJoinRequest, Telegram Bot API, Telegram, checked 22 September 2026
The gate belongs before the join, not after it. A request-to-join link plus a check that runs on the request is the whole trick.
— The Scalegram Team
Key takeaways
- A request-to-join invite link (Telegram's
creates_join_requestparameter) stops adding members directly and queues a request an admin, or a bot, has to approve. - Telegram's Bot API gives a bot
approveChatJoinRequestanddeclineChatJoinRequest, so the group opens without a human reading the request bar. - Separate invite links, each with its own
member_limit, let a group tie one link to one ad or one visitor for tracking, on top of the approval gate. - Scalegram's bot checks the deposit against the broker's own records first, then approves the request itself, and files the client card in the same step.
Frequently asked questions
How do I open a Telegram VIP group only after a deposit?
Set the group's invite link to require admin approval (Telegram's join request feature), make a bot an administrator with the invite right, and have that bot check the deposit against the broker's own records before it approves each request.
Can a bot approve Telegram join requests without a person tapping anything?
Yes. Telegram's Bot API has an approveChatJoinRequest method that any bot with the can_invite_users administrator right can call once it decides a request should be accepted.
What happens to a join request if the deposit is not there yet?
Scalegram answers with what the broker's records show and queues a follow-up instead of declining outright, so a deposit made later still opens the group without the lead having to ask again.
Do I need a different invite link for every ad?
Not for the approval gate, but a separate tracked link per ad or per campaign is how a join gets attributed to the click that brought it, which is what Scalegram's Ad Tracking uses the per-link limit for.
Put one bot on your own Telegram
Scalegram answers every lead in the language it arrived in, checks the deposit against the broker's own records, opens the paid group and files the client. Lite starts at $99 a month.