Infinity3 Help Centre
Practical guides and answers for your Infinity3 tools and services.
Schedule recurring social media posts in Infinity3
- View as Markdown Open this page as plain Markdown (opens in a new tab)
- Open in ChatGPT Ask questions about this page (opens in a new tab)
- Open in Claude Ask questions about this page (opens in a new tab)
- Open in Google AI Studio Ask questions about this page (Google account required) (opens in a new tab)
Repeat suitable evergreen content on a planned schedule, such as a regular reminder about a service or booking option.
Before you start
You’ll need access to Social Planner and connected publishing accounts. Choose content that will remain accurate throughout the schedule.
Avoid recurring posts for temporary offers unless you set and check an appropriate end date.
Create the schedule
- Open Marketing → Social Planner.
- Select New Post → Create New Post.
- Choose the social accounts and prepare the content.
- Review each channel’s preview and customise variants where needed.
- Open the publishing options and choose Schedule Recurring Posts.
- Choose the supported daily, weekly, monthly or yearly recurrence.
- Set the relevant days, time and date range.
- Review and confirm the schedule.
Check upcoming occurrences
Open the Planner calendar and confirm the intended repetition. Check that recurring posts do not clash with other scheduled content.
When editing, review whether the controls affect one occurrence or the parent recurring post. Check future occurrences afterwards.
Review regularly
Revisit recurring content when prices, services, opening hours or links change. Update or stop the series using its available controls when it is no longer relevant.
Things to know
- Repeated identical content may be restricted or treated differently by individual platforms.
- Each occurrence still needs a working connection and supported media.
- A schedule does not guarantee publication; check results.
Contact Infinity3 with the recurring post and affected dates if the repetition is incorrect.
