Utility

What these bots do

This is the least glamorous category and the most useful one. Utility bots solve small, concrete problems: setting reminders, converting time zones, encoding strings, converting colours, expanding shortened links, scheduling a message, looking up information about a member.

They do not replace a workflow, they shorten it. The gain comes from nobody having to leave the server to look something up, and from the answer landing in the channel where everyone can see it.

Features that actually matter

One bot per job, or one bot for everything. Both are defensible. An all-in-one saves invites and command clutter but takes everything down with it when it fails. Several small bots are more resilient and harder to keep track of. Below a thousand members, a good all-in-one is usually the right call.

Slash commands, not prefixes. A utility gets used rarely, which is exactly why nobody remembers the command. Slash commands announce themselves as you type, with descriptions and fields. A utility bot without them stops being used within a fortnight because nobody recalls its name.

Reminders that survive. Check whether reminders outlive a bot restart. Bots that hold them only in memory lose them, and you find out when an important one fails to arrive.

Time zones done properly. A bot that handles times without zones creates misunderstandings instead of resolving them. Good implementations ask once and then convert per member.

Permissions worth checking

Most utilities need only Send Messages, Read Message History, Attach Files and Use External Emojis. Some all-in-ones ask for considerably more, because they moderate on the side.

That is precisely where a look pays off: if a bot presents itself as a toolbox and requests Ban Members, Manage Channels and Manage Roles, it is not a toolbox — it is a moderation bot with extras. That is not wrong, but you should know what you are inviting and judge the permissions accordingly.

Nothing in this category needs Administrator.

Where server owners go wrong

The first mistake is the bot that does everything and nothing well. All-in-ones with two hundred commands typically have twenty maintained ones and a hundred and eighty untouched for years. Check when anything last changed.

The second is prefix collisions. Two bots on the same character produce duplicate replies. Check before inviting whether the prefix can be changed — or pick bots built on slash commands and skip the problem.

The third is no documentation inside the server. A tool nobody knows about does not get used. A pinned post listing the five commands you actually need beats any help page.