Post once in one channel. It publishes everywhere.

You already post in more than one place. The same announcement, typed once — then copied into Bale, again into Telegram, again into Rubika. Or, more often: posted in one of them and forgotten in the others.

Smart Publishing removes that step. You post natively, exactly where you already post, and SocialsPro publishes the post itself into the other channels you chose.

What It Does

Nothing about your routine changes. There is no second composer to learn and no second app to open: you post in your own channel, in the app you already use.

Within moments the same post appears in the channels you picked — the post itself, not a link and not a screenshot. Its caption and its media come with it.

Everything You Post

• Photos and videos, including several at once.
• Audio and voice notes.
• Documents — a PDF, a ZIP, a DOCX, and a GIF sent as a file.
• Albums. A gallery is published in the other channel as one post: the photos together, the caption written once.
• Long captions. When a caption is too long for a single message, its parts follow each other in order.

Two Ways A Post Travels

That 20 MB is not a setting we are holding back: it is the platform’s own download ceiling for a bot. Where a large file has to cross to another platform, we would rather tell you than fail quietly.

It Cannot Loop Or Double-Post

A channel post carries no bot identity — Telegram leaves the sender out of one entirely. So the only reliable way to know whether a post is yours or ours is a record of what we published, and SocialsPro keeps one:

• Every post we publish is recorded, so our own copies are never mirrored back.
• Every post is claimed before it is sent, so a restart that replays the platform’s backlog cannot publish it a second time.
• Two rules pointing at each other (A → B and B → A) cannot ping-pong — the copy in B is recognised as ours.
• The same photo or gallery posted in two of your channels is not published twice either: the system remembers what it has already delivered, so a rule pair that points both ways still leaves one copy per channel — with the caption, not the caption-less rerun that used to come back.
• A channel is never mirrored into itself.

You Will See It Everywhere It Counts

A mirrored post is not a silent background action. It is recorded exactly like a post you sent yourself:

• it appears in your send history;
• it appears in Activity & Logs, with the same success or failure detail;
• it counts toward Messages Posted;
• and it does not spend the free trial’s single Compose try — a mirror is not you composing anything.

Set It Up In Five Steps

1. Connect a Telegram, Bale or Rubika account, and make its bot an admin of the channel you post in.
2. On that account, fill in the Source channel — unless it is already the channel the account publishes to.
3. Open Accounts → Smart Publishing and press + Add rule.
4. Choose the account that watches the channel, then tick the channels to mirror to.
5. Post as usual. That is the whole workflow.

On Rubika there is one extra switch inside its BotFather: enable “receive all channel and group messages”, otherwise the bot only sees messages that mention it.

Which Plans Include It

Smart Publishing is included in every paid plan. It is not part of the Free plan.

What It Does Not Do Yet

We would rather you know the edges now than find them later:

• 20 MB is the ceiling for a file crossing to a different platform; same-platform copies have none.
• Eitaa can never be a source. Its API has no way to read messages, so it works as a destination only.
• Stickers are not mirrored, and a document can arrive from a channel but is not something you upload in the composer yet.
• Audio and documents are published as one message each — only photos and videos can form a gallery.
• Composing several photos into one image on Rubika and Eitaa is lossy: it is a single grid image, not the separate photos.

Ready to stop copy-pasting? Open SocialsPro, connect a channel, and publish once.