Sticky Messages

Set up a sticky message

Use Discord > Sticky Messages when one reusable message should stay near the bottom of a busy channel. An OWNER or ADMIN manages the configuration; Community & Discord access and a connected server are required.

1. Create and save the desired content in Discord > Messages. Use a template whose variables can be resolved without a particular live member event.
2. Open Sticky Messages and start a new configuration. Choose Channel and the saved Template.
3. Set Repost delay and Status. Leave Status paused if you want to save without posting.
4. Click Save. Saving a new enabled sticky attempts its first Discord post immediately. Read any saved error; a saved configuration is not proof that Discord delivery succeeded.
5. Check the Discord channel. Subsequent activity triggers a debounced refresh rather than a post for every message.

Edit, refresh or pause

1. Select the sticky from the saved list. Edit its channel, template, delay or status and click Save.
2. Changing the channel, template or enabling a paused sticky can trigger a refresh. Changing only the referenced template's content in Messages does not immediately rewrite the sticky; use Refresh now after saving that template to apply it immediately.
3. To pause reposting, change Status to paused and Save. Pausing is not a request to delete the already-posted Discord message.
4. Use Refresh now on an enabled configuration when you want the bot to replace its tracked message now. Use Delete only when you want to remove the configuration and its tracked sticky message.

Troubleshooting

Only one sticky can be configured per workspace channel. If a refresh fails, read the last error and check the saved template, unresolved variables, bot channel access and message history. If the old bot message cannot be safely removed, CollabOS stops rather than adding another copy. Restore access before retrying Refresh now.

Behavior and settings reference

Sticky Messages keep one important CollabOS message at the bottom of a Discord channel without leaving repeated copies behind.

How it works

A sticky references an existing saved Message Builder template.

When new channel activity pushes the sticky upward:

1. CollabOS waits for the configured repost delay.
2. It removes the exact previous sticky message created by CollabOS.
3. It reposts the same saved template at the bottom.

Rapid messages are debounced into one refresh instead of causing a new Discord API request for every message. The default delay is 5 seconds and the configured delay can be adjusted.

Duplicate protection

CollabOS tracks the exact Discord message ID for the active sticky. It only attempts to delete the stored message and verifies that the message belongs to the CollabOS bot. If the previous sticky cannot be safely removed, CollabOS does not post another copy.

Mentions

Automatic sticky reposts suppress user, role, and @everyone mention parsing so a sticky cannot repeatedly ping members every time it moves. Normal channel mentions can still render as channel references.

Template compatibility

Sticky Messages reuse Message Builder content rather than copying the template into a second editor. Templates that depend on runtime member variables must have the required values available; unresolved variables prevent the sticky from being reposted.

Dashboard controls

Owners and admins can create, update, refresh, pause, move, or delete sticky configurations. Other permitted workspace roles can review configured stickies.

A sticky configuration includes:

• Discord channel
• saved Message Builder template
• enabled or paused status
• repost delay
• last posted message
• last error where applicable

Only one sticky configuration is allowed per workspace channel.

Permissions

The bot needs the normal channel access required to view and send messages. Removing the previous sticky also requires access to the message history and permission to delete the CollabOS bot's previous message.