> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/web-app-features/content-calendar/create-schedule.md).

# Create Schedule

Create recurring posting slots using local time, weekdays, and eligible accounts. Slots do not choose a post's publishing destination.

## Create Slot Schedule

A weekly slot provides a time for posts submitted with Next free slot time. Slots are not required for Pick a time or Now.

1. Open [Calendar > Weekly schedule](https://my.blotato.com/calendar#weekly-schedule).
2. Review the existing times and eligible accounts.

Example: *You have a LinkedIn post slot at 8:23 AM on Monday.*

## **Add New Slots**

1. Select Add slot in the Weekly posting schedule section.
2. Enter Time in your computer's local timezone.
3. Select the days of the week under Days.
4. Select the eligible destinations under Accounts.
5. Click Create.
6. Verify the slot appears under its weekday in Weekly posting schedule.

![Create slot dialog with local time, weekdays, and eligible accounts](https://2374509648-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FevfU9S4Nh53PiGflQLah%2Fuploads%2Fgit-blob-10955b2c136096b27000abb41d06bf57e24b7183%2Fui-weekly-slot-2026-10.jpg?alt=media)

## No available slot time found

If Next free slot time reports no available time in the next 9 months:

1. Open Calendar > Weekly schedule.
2. Check the slot's weekday and time.
3. Check its Accounts selection includes the destination on your draft.
4. Add a matching slot if none exists.
5. Return to the draft and review the proposed time before submitting.

Use Pick a time to schedule at an exact time without a recurring slot. A recurring slot is a timing rule, not a scheduled post.

## Choosing Accounts for a Slot

When you add a slot for a platform like LinkedIn, choose which posts are allowed to use the slot:

* **All LinkedIn** — posts targeting any connected LinkedIn personal profile or company Page are allowed to use the slot.
* **\[Your specific account name]** — only posts targeting that profile or Page are allowed to use the slot.

**All LinkedIn does not publish one post to every LinkedIn destination.** The destination selected on the post still controls where it publishes. To publish the same content to a personal profile and a company Page, create one post for each destination.

## Enabling Slots for Different Platforms

Use the slot's Accounts choices to select eligible platforms, accounts, or Pages. A LinkedIn slot does not match an Instagram post. The post still needs its own destination selection.

Use Add account on an existing slot to add an eligible destination. Removing an account from a slot changes its eligibility, not the destinations of existing posts. Review the slot before selecting Delete slot.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.blotato.com/web-app-features/content-calendar/create-schedule.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.