Skip to main content
Scheduling lets you approve a post now and publish it later.

Schedule from chat

Ask for a date, time, and target platform.
daoco prepares the post, shows a preview, and asks for approval before scheduling.

Schedule from Manual post

1

Prepare the post

Create or open the post you want to schedule.
2

Choose accounts

Confirm the connected accounts and platform variants.
3

Set date and time

Choose the schedule time in the workflow.
4

Approve

Confirm the scheduled publish action.

Calendar drafts and edits

The calendar’s Drafts button opens saved drafts. Use Load more to fetch older drafts. A plus sign beside the count means more results are available. Choose Schedule on a draft to pick its date and time, or drag it onto a future day. Scheduled posts offer Move and Unschedule. Moving a post by dragging keeps its local time on the new day. If saving a date fails, the picker keeps your selection so you can retry. For a post with several accounts, unscheduling one account leaves the others scheduled. That account appears as a draft with its account name. Scheduling it again changes only that account’s delivery. Use Edit to open the manual composer or Chat to open the existing post in chat. Opening a post checks that it belongs to the current brand and shows a read-only preview. Tell daoco what to change when you are ready to edit. Published post cards show available performance data and links to the published post.

Move a scheduled post from a chat channel

If your workspace has an assistant on Slack, Discord, or WhatsApp, you can ask it for a day’s schedule and have it move posts to a different time or day without opening the dashboard. It changes timing only, and a whole-day move keeps each post’s local time on the new day. Moving a post needs a chat account linked to your daoco account.

Scheduling checks

  • Use a specific timezone when timing matters.
  • Check platform limits before scheduling mixed media, multi-account posts, or per-platform variants.
  • Review scheduled and published posts in the calendar on Home.
  • Use campaign calendars for launch planning across multiple posts.
  • A post in review can be scheduled, but it publishes only after every stage signs off. If sign-off finishes after its time, it goes back to draft.
  • Campaign and post calendars place published and scheduled items more consistently across day, week, and campaign views.
  • On mobile, use the compact calendar pills to open the post details instead of relying on full post text inside each month cell.
  • If a scheduled publish fails because a social connection expired, reconnect the account from Connections, then review the delivery from the calendar or its chat workflow.

Unconfirmed deliveries

Sometimes daoco sends a post and the platform never answers. The request may time out, or the connection may drop while the post is being created. The post might be live. daoco does not send it again, because a retry could post it twice. The calendar marks it Sent, result unconfirmed. Open the post and choose Check to look through the account’s recent posts on the platform. If daoco finds the post, it is marked as published with its link. A missing post stays unconfirmed because the recent-post list may be incomplete. Check the account yourself before sending it again. For platforms daoco cannot read, or when the check cannot finish, use the same manual check. Then choose Mark as published or Mark as failed. daoco records your confirmation on the post’s history. Unconfirmed posts cannot be moved or deleted until they have a result, and their post cannot be edited or retargeted. The same rule applies to other integration writes, such as a CRM update or a file created in a connected tool. If the result never comes back, the chat shows that it is unconfirmed and daoco does not run it again. An approved write also stops if the connection now uses a different account than the one you approved. daoco asks you to approve it again.

Mixed schedules

If a multi-platform post has variants scheduled for different times, review the schedule details in the inspector before approving. daoco groups related variants together, but each delivery can still have its own platform-specific requirements and timing.