Why groups end up with too many bots
Bots are usually added one problem at a time. Spam appears, so an anti-spam bot arrives. New members ask the same questions, so a welcome bot is added. Someone wants statistics, and a third bot joins. Each one has its own settings page, its own commands and its own messages in the chat.
The trouble starts when they overlap. Two bots both greet a new member. One deletes a message that another one was about to warn about. A member types a command and three bots answer. Nobody remembers which bot does what.
Step 1: write down what each bot does
Open each bot's settings and make a short list: welcome text, CAPTCHA type, which links are blocked, warning limits, banned words, any scheduled posts. This is the list you will rebuild, and it often shows that half the settings were set once and forgotten.
Step 2: rebuild it as modules
In BotLaunch you add one bot to the group as an admin and turn on modules from the web dashboard: welcome messages, CAPTCHA verification, anti-spam and anti-flood, link protection, forbidden words, warnings and bans, scheduled posts and analytics. Each module takes the settings from your list. Try it first in a small test group with a second account, so you can see the welcome, pass the CAPTCHA and post a test link.
Step 3: switch over one bot at a time
Do not remove everything at once. Turn on one module in the real group, then remove the old bot that did the same job. Watch the group for a day, then move to the next. This way there is never a gap where new members join without a check, and never a period where two bots fight over the same message.
Step 4: tell the members
Post a short message explaining that the bots changed and which commands still work. Update the pinned rules if the warning limits or the banned list changed. A clear note prevents a week of "why did my message disappear?"
What you gain
One set of rules, one place to change them, and one bot's messages in the chat instead of three. When something is removed, there is one log to check.