What the Engagement module covers

Engagement is the set of features that react to your members instead of policing them. Someone joins and gets greeted. A funny message gets pinned by popular vote. A member asks for a change and the server votes on it. A prize gets handed out. A birthday gets celebrated. A creator goes live and the server hears about it.

Where they live in the dashboard

Open your server on the dashboard and look at the left sidebar.

• Engagement holds Starboard, Giveaways, Suggestion and Birthday.
• Server Management holds Welcome & Goodbye.
• Notifications holds YouTube, Twitch, Kick and Reddit.

What every one of them has in common

Learning these five things once saves you reading them six times.

Choosing where a message goes

Every feature that posts a message asks for a channel, and the picker accepts more than a plain text channel: text channels, the built-in text chat of a voice or stage channel, forum channels and media channels all work.

Pick a forum or media channel and the feature opens a new thread per event instead of posting into the channel, because a forum has no channel body to post into. A welcome opens one thread per joiner, a starboard opens one thread per starred message, a YouTube subscription opens one thread per video. Several features let you name those threads with a template.

You can also point a feature at one specific thread or forum post inside the parent channel. Do that and everything lands in that single thread, with no new thread per event.

Plain text or a built embed

Most message fields offer two modes: Text (Legacy), a plain message you type in the box, or Template, an embed you built on the Embed Messages page and picked here by name. The template mode gives you colours, images, fields and buttons; the text mode is one box and is faster to set up.

Variables

Both modes support variables written in single braces, like {user} or {server.name}. Each feature exposes its own set, listed on that feature's page.

A variable that does not exist in the current context is left in the message exactly as you typed it, braces and all. It is never replaced by a blank. So if a goodbye message prints {member.joined_at} literally, that variable simply is not available there.

The bot needs the right permissions

Nothing posts if the bot cannot post. In every target channel the bot needs View Channel, Send Messages and Embed Links, plus Create Public Threads when the target is a forum. Features that hand out a role also need Manage Roles, and the role they hand out must sit below the bot's own highest role in the server settings list.

Auto-disable when something is permanently broken

Welcome and goodbye, starboard panels, birthdays and feed subscriptions track their own health: if one of them fails for a permanent reason (the channel was deleted, the bot lost a permission) 10 times in a row, FlaviBot switches it off and stamps the reason, and the dashboard shows a red banner on that feature's page telling you what broke and when, with a button to switch it back on once you have fixed it. Suggestions and giveaways have no auto-disable: they simply keep failing until you fix the configuration.

Any event where nothing failed permanently resets the counter, so an occasional failure never disables a feature that mostly works. Note that a single event can run several parts at once (a join runs the role, the message, the greet and the DM), and one part failing permanently still counts against the feature even when the others worked.

When a feature does not do quite what you want

These six features cover the common cases with a small number of settings. When you need a rule that is specific to your server, the autoresponder does the same kind of work with a trigger, filters and a list of actions you choose yourself.