If you often use the same set of hashtags in your messages, you can save them to make it quicker and more accurate when adding them to your posts.

Frequently used hashtags

Using a Content Library to store frequently used hashtags allows you to streamline the process of composing messages with hashtags in the Compose Box, especially for profiles that support hashtags such as X (Twitter), Instagram, Facebook, and LinkedIn.

Once the hashtags have been saved, they can be added directly from within the Compose Box and will appear in the body of the message you are composing. This means you no longer need to recall frequently used hashtags from memory or copy and paste them from a saved document elsewhere.

Creating a set of saved hashtags

1. Go to Content > My Content from the drop-down or the left sidebar
2. Click Add Content
3. Select Social Media
4. Create a title, for example, "Saved Hashtags" or "Saved Hashtags - Client X", etc.
5. Enter the hashtags you regularly use and wish to save, separating each with a space. Be sure to enter a '#' (hashtag) at the start of the word.

6. Once you have entered all of the hashtags which you would like to save for this particular group, click Add Content to save. You can repeat this process for additional sets of hashtags or clients.

   

Composing a message using saved hashtags

1. To use the hashtags you've created, navigate to the Compose Box by selecting the Compose button from the top right-hand corner of the dashboard.

2. Insert your saved hashtags by clicking on the book icon.

   

3. You can filter by the Content Library, the title, or the tags you created previously. Once you've located the desired content, click the Insert button.

   

4. The saved hashtags will then appear in the body of the Compose Box, and from here you can create and schedule your message as usual.

   

Still an issue?

No worries! We can take it from here.

Please submit a support ticket and be sure to mention you have gone through the typical troubleshooting steps. In addition, providing screenshots and including where you were and the steps you took when the issue happened will help us resolve it more quickly!