Two ways to schedule
Pick a time. Open a post, choose a date and time, done. Use this when the post belongs at a particular moment โ an announcement, an event, something time-sensitive.
Queue it. Hit Queue and DemandBird drops the post into the next free slot in your posting schedule. Use this for everything else, which is most things.
The queue exists so that "when should this go out?" stops being a decision you make one post at a time. You set a rhythm once and then feed it.
Setting up your schedule
Your posting schedule is a set of time slots: a day of the week and a time, per channel. Find them at Settings โ Posting schedule.
Slots are per channel, not per platform. Two LinkedIn profiles on the same account each get their own schedule, because they are different audiences.
Connecting a channel adds no posting times. You add them here, or accept the suggested times the first time you queue a post to that channel (see below).
The quickest way to start is a preset:
| Preset | Slots per channel |
|---|---|
| 1ร per week | Wednesday |
| 3ร per week | Tuesday, Wednesday, Thursday |
| 5ร per week | Monday to Friday |
Presets seed every slot at 9:00am and replace whatever that channel had. Then move the times to where you actually want them.
How the queue picks a slot
When you queue a post, DemandBird walks forward through that channel's slots and takes the first one that has nothing in it. Slots already holding a scheduled post are skipped, so queueing five posts fills your next five open slots rather than stacking five posts on Wednesday.
If a channel has no posting times yet, pressing Add to queue offers suggested times in the send menu instead. For example: "LinkedIn has no posting times yet. Post on weekdays at 9:00am and 1:00pm?" Two buttons follow:
- Use these times adds those posting times to the channel and queues the post, in the same click.
- Choose my own opens Settings โ Posting schedule, so you can set times yourself.
The suggested times depend on the platform:
| Platform | Suggested posting times |
|---|---|
| Weekdays at 9:00am and 1:00pm | |
| X | Weekdays at 9:00am, 1:00pm and 5:00pm |
| Threads | Weekdays at 12:00pm |
| Bluesky | Weekdays at 9:00am |
| Weekdays at 1:00pm | |
| Monday, Wednesday and Friday at 11:00am | |
| Substack | Tuesday at 9:00am |
| YouTube | Tuesday and Saturday at 3:00pm |
The check is per channel. A second LinkedIn profile with no posting times gets the offer even when your other LinkedIn profile already has times.
A seat that can't edit that channel's schedule sees no buttons. It is told to ask an admin to add posting times instead.
Posting to several channels at once queues each one independently, into its own next open slot. They will not all land at the same minute, which is usually what you want.
Where you land
Schedule, Queue, and saving changes to a scheduled post all take you to the Queue, with the post highlighted and a "Scheduled for [time]" note, so you can see exactly where it went. Post now takes you to Published instead.
Telling channels apart
When a workspace has 2 or more accounts on one platform (say a LinkedIn company page and a personal profile), queue rows, calendar cards, post cards, and board cards show that channel's avatar in the corner of the platform icon. Hover the icon to see the channel's name. With only one account on a platform, the plain icon already says which channel it is, so no avatar is added.
Out of date posts
A scheduled post whose channel copy predates your last edit shows an Out of date chip. Click it to open the post and choose which version goes out.
Taking a post out of the queue
Remove from queue moves a scheduled post back to Drafts and keeps everything: its copy, media, and channels. The trash can is different: it deletes the whole post.
Open slots on the calendar
The calendar draws open slots from now on. A slot in the past only shows if a post went out, or failed, in it; empty past slots are never drawn, so the calendar shows what happened rather than what you missed.
Posting variance
By default a post goes out at exactly its scheduled time. Every week. Forever. That is a recognisable pattern.
Posting variance spreads each publish randomly around its slot. Set it at Settings โ Posting schedule, up to a one-hour spread โ so ยฑ30 minutes at the widest. Set it to zero to publish at the exact time.
Variance applies to the whole account, not per channel.
Best time to post
Once a channel has enough history, DemandBird can tell you which day-and-hour combinations your posts have actually performed best in โ computed from your own engagement data, in your timezone, not from a generic industry chart.
You will find it in analytics, and you can ask for it from Claude or any MCP client with a question like "when should I post on LinkedIn?".
Treat it as evidence, not instruction. It is your history, so it partly reflects when you have posted rather than when your audience is best reached โ a slot you have never used cannot show up as your best one. It is most useful for spotting a slot that is clearly underperforming.
Pausing
Pause holds every scheduled and queued post for the whole account, every workspace included. Nothing is deleted or moved, and post times do not shift.
When you resume, held posts go out right away, including any whose time passed while the queue was paused. Before you resume, cancel or reschedule anything you no longer want to publish.
Post now still publishes while the queue is paused, and so does publishing a post from Claude or ChatGPT.
To pause, text pause (and resume to start again) if you have SMS or
WhatsApp set up, or ask Claude or ChatGPT through the
DemandBird connector.
Who can change the schedule
Editing a channel's slots needs edit access to that channel. A read-only seat sees the schedule but no controls. On an agency account, a seat scoped to one client's workspace cannot change another client's posting times.
When a slot is missed
A post whose publish fails is retried, and if it keeps failing it is marked failed on the content board with the platform's reason. It does not silently vanish, and it does not block the slot behind it.
The most common cause is an expired channel authorisation. When a channel needs reconnecting, a banner across every page names it, and admins who can manage channels get a Reconnect link right there. Settings โ Connected Accounts also shows which channel needs reconnecting.