Deferred posting and moderation

By default a message goes out as soon as it appears in the source. Deferred delivery holds it: either until you approve it, or until the schedule allows it. The setting is per destination chat.

Switching the mode

Open the chat in the mini app. The Delivery mode block has two positions: Instant and Deferred. Choose Deferred and open Deferred posting settings.

Publishing mode

The Publishing mode switch offers Manual review or Auto-publish. Neither requires a moderation chat — without one, the messages wait in a shared service channel instead (see Moderation chat below).

Manual review

In Manual review every message lands in the queue instead of the chat, and the bot sends you a moderation card — the message with Publish and Delete buttons — in your chat with @RoutifyBot, or in the moderation chat if one is connected. The queue lives in its own section — Schedule and queue in the Management block: it appears as soon as the queue is not empty and carries a counter. For each queued message you can:

• Publish — send it to the chat now;
• Edit — open the message in your own moderation chat, change it there and publish the edited version. Only available once your own chat is connected; otherwise just Publish or Delete.
• Delete — drop it.

With a moderation chat connected, a team can review messages from Telegram without opening the mini app; editing still happens in the chat itself.

Auto-publish

In Auto-publish nobody has to approve anything; the bot publishes by rules:

• Hold the post for — delay every message by a set duration, up to 24 hours; "Disabled" (0) skips the delay.
• Pause between posts — the minimum gap between two publications, up to 60 minutes, so a burst of messages from one source spreads out over the day.
• Publish inside a set window — a toggle that opens the day/time picker: publish only inside chosen hours on chosen days, in the chat's time zone. One schedule can hold several periods; add a separate schedule for days with different hours. Turning it on reveals Skip posts outside the window: instead of waiting for the next opening, drop messages that arrive outside it.

A message waits out the delay, then the next open window, and goes out no sooner than the interval after the previous one.

Where the queue is

The list of messages waiting on a decision lives in Schedule and queue — together with your own posts and the publishing calendar. The All / Moderation / Posts filter narrows the list down to source messages when that is what you are reviewing. Dates are shown in the chat's time zone. A message that has already been handled — published by the schedule before you pressed the button, or deleted from another device — says so instead of acting twice.

The Deferred posting settings screen no longer holds a list of messages: it keeps the rules only — mode, delay, window and moderation chat.

Moderation chat

Optional. Connect your own chat — a group or a channel; the bot (and the custom bot, if configured) must be an administrator there. Then you can edit messages before publishing: create a private group or channel, add @RoutifyBot (and your custom bot, if any) as an administrator, paste its id or t.me/c/… link into the field and press the plus button.

Without your own moderation chat the messages are kept in our service channel. You have no access there, so editing is not possible — only publish or delete from Schedule and queue.

Deferred posting and the delivery modes

The queue stores the message as it came out of the pipeline, so Send latest post and the scheduled publication are both delivered the same way as the source — by the bot or from the account, see Delivery modes. Messages parked in the queue can be published even if the source chat has since deleted them.

Deferred posting vs. the time filter

The time filter in Message filtering also has a window, but it is a filter: a message outside the window is dropped. Deferred posting queues it and publishes later. Use the filter for "never at night", deferred posting for "not before 9 in the morning".