Automated Scheduling
Luke Brewin avatar
Written by Luke Brewin
Updated over a week ago

SoAmpli makes posting great content to your own social channels extremely easy. But we understand that finding time each day to log on and post can be hard to do. This is why we created an automated scheduling tool to help you save time. Now, anyone can log on, and in 10 minutes they could have set up their outgoing social posts for the entire week! 

In order to start using automated scheduling, you need to add some time slots so that SoAmpli knows what time you would like your posts to be shared. 

Here's how you can do it:

  1. Head to the queue tab and click the 'Manage automated queue' button

2. Pick any slot you like, whether once a week or Monday through Friday

3. Save every slot you create

You can have multiple time slots so it’s best to set up a few throughout the week. Try to think about when your followers are most likely to be active on social media; in our experience, morning commute, lunch time and evenings work really well, but don’t be afraid of trying different times and playing around with the schedule! 

When setting your automated slots, keep in mind that each social media channel is different. On SoAmpli, each slot you create will work for all channels (Twitter, LinkedIn and Facebook) so make sure you consider this when setting the frequency of your time slots.

Now that your automated queue is set up, you can start enjoying one-click scheduling! Simply select the 'Add to queue' option in the drop down menu when sharing a post, as shown here:

You can see all your scheduled posts at all times in the 'Queue' tab on SoAmpli. If you ever make a mistake and you realise something is going out at the wrong time, then there is the option to reschedule. In your queue, you can click on the little calendar icon to either remove the post from your queue or reschedule it

If you want to see what content you have scheduled for a particular platform, you can also filter by channel at the top of the page, as shown below:

Did this answer your question?