Schedule vs. publish now

The ways a post leaves Velisto — immediately, at a chosen time — and what happens if publishing fails.

Last updated

Every post you approve leaves Velisto one of two ways: right now, or at a time you set. Both are server-side — once a post is scheduled, your part is done. No phone reminders, no copy-pasting into apps at 9am.

Publish now

Publish now sends the post to its channels immediately. Use it for time-sensitive moments — the offer was accepted, the open house starts in an hour. The post moves to published on the calendar once each channel confirms.

Schedule for a time

Hit Schedule and pick the moment however suits you: type it in plain language ("thursday at 10:45 pm", "in 3 hours"), tap a quick option (Tonight, Tomorrow morning, Next Tuesday), or hand it to your posting rhythm with Next slot or Queue — your workspace's regular posting times, set under Workspace settings → Scheduling. There's a Save as draft escape hatch right there too.

The Schedule modal: natural-language time input, quick options, Next slot and Queue
Type a time, tap a preset, or drop it into your queue.

Until the moment it publishes you can still edit the caption, swap the design, change channels, or drag it to a different slot on the calendar. Batch tools like Fill my week schedule automatically across the week for you.

Note:

Scheduled times are in your workspace's timezone. Posting at "9:00" means 9:00 where your audience lives, not where your laptop happens to be.

What happens at publish time

Velisto delivers the post to each selected channel from its servers — captions per channel, media in each platform's required format. One post targeting Instagram and Facebook publishes to both within moments of its scheduled time. Video channels (TikTok, reels) can take slightly longer while the platform processes the upload.

When something fails

Platforms occasionally reject a post — an expired connection is the most common cause. When that happens the post is marked failed on the calendar with the reason, and you're notified. Fix the cause (usually a reconnect) and publish the post again from its card — the content is never lost.

Stuck on this step? Send us a message — a real person replies.