Custom Bot Account

By default, AveloBot posts in your chat under the shared AveloBot account that the operator runs. With the Custom Bot Pro feature you connect your own dedicated Twitch account and AveloBot will post under that name in your channel — useful for branding (e.g. @yournamebot instead of @avelobot) or to keep messaging under credentials you control.

The page lives at /pro/custom-bot. Only the workspace Owner sees it (because the connection affects the whole workspace and uses the broadcaster's auth context to authorize OAuth).

Prerequisites

• Your workspace has the pro.custom-bot entitlement. If not, the page shows a "Pro required" card with a link back to the Pro overview.
• A separate Twitch account for the bot. Twitch won't let you sign the same account in twice, so the bot account must be different from your broadcaster account. Any unused or fresh Twitch account works.

Connecting your bot account

1. Sign into Twitch in a separate browser session (or incognito window) using the bot account.
2. Back in AveloBot, on /pro/custom-bot, click Connect Bot Account.
3. Twitch's OAuth screen appears. Pick the bot account, not your broadcaster. AveloBot forces the account picker so you can't accidentally sign the broadcaster in by mistake.
4. Grant the requested scopes — they're the same scopes the shared bot uses (chat read/send + a few helpers).
5. You're redirected back; the page now says Connected as <bot_login> with the display name, the granted scopes, the connect time, and the token expiry.

The connection is verified server-side — AveloBot rejects it if you accidentally signed the same account that's the broadcaster, or if Twitch didn't grant all required scopes. In either case you'll see an error banner and the connection isn't saved.

What changes after connecting

• New chat messages from AveloBot in your channel show your bot's name and avatar.
• Your audit log records tenant.custom-bot.connected for the action.
• Existing built-in commands, custom commands, counters, timers, and event responses continue to work — only the identity posting them changes.

Reauthorizing

Twitch tokens expire and AveloBot refreshes them automatically. If a refresh fails (because the bot account was revoked or its password changed), the page shows Bot connection needs re-authorization in red. Until you reconnect:

• AveloBot falls back to the shared bot so your chat keeps working.
• Click Reconnect on the page to re-run the OAuth flow.

Disconnecting

Click Disconnect on the page and confirm. AveloBot revokes the Twitch tokens, drops the connection record, and audits the action. Chat posting goes back to the shared bot immediately.

When your Pro entitlement ends

Your stored connection isn't deleted. AveloBot just stops using it and posts under the shared bot again. If you reactivate Pro later, the bot connection wakes back up — no need to reconnect.

Troubleshooting

Symptom	Likely cause	Fix
OAuth screen shows your broadcaster, not the bot.	You're signed into Twitch with the broadcaster in the same browser session.	Use an incognito window for the bot OAuth, or sign out of Twitch in the main window first.
"Bot account must differ from broadcaster" error.	You picked the broadcaster account on the Twitch screen.	Restart Connect with the correct account.
"Missing scopes" error.	You unticked a scope on the Twitch grant screen.	Reconnect and accept all requested scopes.
Bot connection in red ("needs reauthorization").	Refresh token rejected — usually a password change or app revocation on the bot account.	Click Reconnect.
Chat messages still come from AveloBot.	The Pro entitlement isn't active for your workspace, or the connection is in the "needs reauth" state.	Check /pro for entitlement status; check /pro/custom-bot for connection status.