If your source is a public channel or private channel with an active invitation link, then you need a Standard account. The pricing for this service you can see by a command /powerup.

If your source is a private channel without an invitation link or is a bot, then you need the Direct connection. The pricing and manual for this service you can see here.

Please create a separate group chat with bot (non-service one). It will be working as a separate account and you will need to pay for it separately. All details you can see with command /account

You need a pro-account.
1. Speed up the channel (delay will be less than several seconds) – €1.20 per month per channel. Speeded up channels you can always change later with command /express.
2. Get 10 more forwards – €0.60 per month.
3. Get 5 more private channels – €0.60 per month.
4. We can connect your telegram-account to the bot (direct connection) so you can forward your messages from any sources wherever you want. It allows to implement the craziest ideas %) Also it can be useful to forward messages from private channels where you are a member and but which are closed for the bot or don’t have invitation links. All channels connected in such a way don’t need a speed up, messages will come in several seconds. The price is €12 per month per account. More details.

How to enable: Top up your pro account with command /poweruppro and contact admin for enabling needed services. Please pay attention that this command is different from a command to pay for your general account (/powerup). Once topped up your pro account will keep your balance and all pro services will be paid using this balance. Once the next payment time is reached the monthly fee will be deducted from your pro balance.
This is different from the general account where your payment directly prolongs working time.

Try to use both ways: via web site (clicking on the link) and through Telegram. On a web site try both Tinkoff and Yandex gateways. If it does not help please send us a screenshot with an error.

No PayPal is not supported. You can pay with bank card, QIWI and Webmoney via website. Also you can pay with cryptocurrency, contact admin for that.

First month of usage bot is working in demo-mode with limit equal to 100 channels. After that you get 10 channels for free but for more you need a paid account.
So paid account gives you 100 subscriptions, allows you to forward messages from one channel to another and subscribe to up to 5 private channels.

Yes. Please see here.

We also have a promo action: Invite a friend and he/she will receive a 50% discount for the first month and you get €6 to your pro-account. For details, see here.

Please see Read_messages_in_several_feeds.

Please see Read_messages_in_several_feeds.

Add a @junction_bot as a member to a chat and then add another bot or person. This chat will stop to be a service chat. After that you can remove this extra bot/person.

Service chats are considered a part of your main account. All the limits on subscriptions and forwards for your main account are working for them also. Non-service chats are separate accounts.

Please create a separate group chat with bot (non-service one). It will be working as a separate account and you will need to pay for it separately. All details you can see with command /account.

For channels just added to our system, the start of delivery can take up to one day. This is caused by Telegram’s limitations – we cannot connect to a lot of new channels in a short period of time. But usually, it’s quicker, so just wait for a little.

Messages can come with a delay, usually it will not exceed 30 minutes. Before trying everything else please ensure that the desired channel presents in the list of your subscriptions (use command /list). Also, check that your filters are not filtering all the messages (usual mistake is to add a mustNotHave filter on all links and forget to disable links in the message’s footer).

If messages are still not coming please contact us and provide:
1. a message which you’ve used to create your subscription or forwarding,
2. date-time when you subscribed,
3. the bot’s answer,
4. the bot’s answer to the /list command.

Questions without this information will be redirected back to this FAQ.

The bot will try to join this channel again, but if the admin will persist in banning it, the messages from this channel will stop coming. To work around this you need the Direct Connection. But for a direct connection to work, you will need to be a member of the source channel yourself.

Please check that you are using a Standard account and that the status of your forward is not PENDING. If not, please forward the message with your command and the message with the bot’s response to the admin, and describe your problem.

Please see Reducing delays.

TODO

Junction Bot should be an admin in the destination channel only (it can be a public or a private channel) and you need a Standard account. If your source is a private channel, you only need an active working invitation link. Junction Bot does NOT have to be an admin of this channel. The Bot will join the source channel as a common user. Administration of the source channel can’t find out that it’s a bot. If you need more control over this consider the Direct connection. It allows you to forward messages from the source channel without being noticed at all.
Please note that if you are in our support group, an admin of the source channel can find this out. So for communication in a support group, we recommend using an account other than that in the source channel.

No, it’s not possible.

Yes. First, enable the authors name display with the
/settingchannel … author …
command, and then configure the filters by the desired names.

Yes. Add the bot to the group and just use it as you do in private chat. Maybe you will need to specify the bot’s name in commands: /join@junction_bot

Yes. Add the bot to the group and use it in the same way as in private chat.

They will start to appear automatically after some time. First of all, a replied message should be in the destination channel already. Also, several replies in the source channel will enable the transferring of replies, so after some time you will start to see replies for the new messages in the destination channel.

Please see Pending status.

Yes, we do not guarantee delivery if messages are published in the source channel more often than once per several seconds.

For channels just added to our system, the start of delivery can take up to one day. This is caused by Telegram’s limitations – we cannot connect to a lot of new channels in a short period of time. But usually, it’s quicker, so just wait for a little.

Messages can come with a delay, usually it will not exceed 30 minutes. Before trying everything else please ensure that the desired channel presents in the list of your subscriptions (use command /list). Also, check that your filters are not filtering all the messages (usual mistake is to add a mustNotHave filter on all links and forget to disable links in the message’s footer).

If messages are still not coming please contact us and provide:
1. a message which you’ve used to create your subscription or forwarding,
2. date-time when you subscribed,
3. the bot’s answer,
4. the bot’s answer to the /list command.

Questions without this information will be redirected back to this FAQ.

TODO

All channel to channel forwards are controlled using the /channel command. Use it in the form /channel @destination leave @source.

Once in a while we are updating Junction Bot. Usually, it takes less than a minute.

After an update the bot needs some time to connect to all its channels again. It will be marked with an UPDATING status – just wait for a little bit.

In very rare cases this status can stay for 10-30 minutes, but even in these cases messages will start coming even before status will change back to normal.

The bot will try to join this channel again, but if the admin will persist in banning it, the messages from this channel will stop coming. To work around this you need the Direct Connection. But for a direct connection to work, you will need to be a member of the source channel yourself.

Please check that you are using a Standard account and that the status of your forward is not PENDING. If not, please forward the message with your command and the message with the bot’s response to the admin, and describe your problem.

Please see Reducing delays.

Then you should use the channel instead of the group. Then all messages will come from the name of the channel.
Also, if you want them to be delivered from your name, you should use a direct connection.

/filter @channel_name – see all current filters applied to a channel.

Please check the following:

• Filter should be set on a source channel.
• Filters are sensitive to case.

If words come together in a filter, for example “one two three”, they should also come together in a message – “one two three” – to be matched.
Also remember that unsubscribing from a channel will delete all your filters so use disabling.

If you have a paid account you can use an explanation feature. Activate it by the command /settingchannel … explain on

You will start receiving explanations about filters matching on the messages.

Please see Combining fllters.

Please see Advanced filtering.

You may face this problem when you use forwarding from your account &1234567890 to a @destination channel without specifying the exact source channel (&1234567890#787878) and in the same time you join the @destination channel by your connected account.

Solution 1: set up forwarding from a specific channel using this format: &1234567890#787878.
Solution 2: leave the @destination channel.

Direct Connection allows you to set up forwards from your connected account only, use the name of your virtual channel. To use forward without your virtual channel you need a common subscription. Use /powerup command.

Forward to the administrator the following messages:

1. Message containing a command /channel with which you set up your forward
2. Bot’s answer
3. Bot’s answer to a command /list
Questions without this information will be redirected back to this FAQ.

Yes. Please see here.

We also have a promo action: Invite a friend and he/she will receive a 50% discount for the first month and you get €6 to your pro-account. For details, see here.

The easiest way is to use a command /channels. It will return a list of your chats and channels with their IDs.
If there is no needed ID in this list, then try another approach:
1. Forward a message from the source channel to the bot @junction_helper0_bot.
2. It will reply you with the message information.
3. There you will see the channel number in field named “forward_from_chat.id”.
4. If a number starts with “-100” just remove “-100” to get a real ID.
This way can fail to work with some groups. Then use another way: click on a post in the source group and select “Copy Link”. You will have in a buffer something like https://t.me/c/123456789/123. Here the middle number is the ID of the group: 123456789.
There is also another way: open the group in Web Telegram and you will see this ID in the browser’s address bar.

If you need to forward messages to a group, use group’s identifier.
For example for a group with id = 123456: /channel 123456 join &1234567890#787878
Notice, that bot should be in a list of administrators of this group.

If you use a direct connection and messages from some channels arrive with a delay or do not arrive at all, please write to the administrator. Be sure to forward the original of the last delayed or not received message. We will quickly fix everything. This is due to the fact that different channels of Telegram work a little differently and in rare cases it requires a fine tuning on our part.

Yes. For that please use a direct connetion.

No, with the Direct Connection it’s not possible to copy messages from channels that you are not a member of. DC does not help you to receive messages knowing only the channel number. It also will not help if you were previously in the channel, and then left it.

No, with the Direct Connection you are not required to be online with your Telegram client. Our system works independently, separately from your client. It is important not to delete the active session with the bot. It is used to get the messages which you want to forward.

With the Direct connection, it is impossible to figure out who forwards the message. The administration of a source channel or a bot sees only your account and does not have any technical ability to find out what you are doing with the messages received. But anyway it’s good should to take any possible measure, right?

For example, if you are copying buttons with notifications, be sure to add a delay before clicking.

Also, please note that if you are in our support group, an admin of your source channel can find this out and have questions towards you. So for communication in a support group, we recommend using an account other than that in the source channel.

If you pay with the command /powerup, then you buy a standard account. To buy Direct Connection you should use the command /poweruppro 12. Direct connection is a different service and is more expensive than a standard account. Please see here the comparison.
If you made this mistake, don’t worry. Just pay the missing amount with the command /poweruppro and let the bot’s admin know, we will transfer your first payment to Direct Connection.

Then you should use the channel instead of the group. Then all messages will come from the name of the channel.
Also, if you want them to be delivered from your name, you should use a direct connection.

Yes, please ask the admin for more details

Most likely, you are looking in the wrong chat. The access codes come to a chat called “Telegram”. News about updates also is there.

Often the code will not come if the account has a cloud password (2FA) enabled. Deactivate the cloud password and request the code again. Once the activation is complete, the cloud password can be re-enabled.

If you are sure, that the phone number is correct, but nothing works, it means the code has been requested too many times. You need to wait, sometimes for up to 24 hours. Keep calm, make sure your cloud password is disabled and try requesting a new code every few hours (but not more often).