Skip to main content

​
Fast triage checklist

  1. Confirm you are logged into the correct account/workspace.
  2. Hard refresh the page and retry once.
  3. Check plan limits (context, tokens, credits, model availability).
  4. Confirm your verb settings were actually saved.
  5. Test with a minimal prompt in a clean chat/thread.

​
Discord issues

Verify token format, ensure the token is not already linked to another verb, and retry after a short delay if Discord is rate limiting requests.
This usually means command timeout, missing channel permission, or a disabled slash command. Check command toggles and bot permissions in that server/channel.
Those voice channel commands are currently Ultra features. Normal Discord activity/presence editing is still available on all plans.
In servers, bot response depends on routing: mention, AI channel, or keyword match. If none of those apply, no response is expected.
Poll Creation must be enabled in Discord Expression Controls, and the bot must have Discord’s native poll permission in that specific channel. Without that permission, Verba falls back to normal text.
Turn on Custom Emojis in Discord Expression Controls and verify the bot can use server or external emojis in that channel. When enabled, Verba prefers fitting custom emojis over plain Unicode.
Put both bots in the same channel and either mention both to start the exchange or enable autonomous mode on both. Bot-to-bot replies are channel-scoped, so starting them in one channel does not make them continue everywhere else in the server.
Remove AI channels with /remove-channel and keep mention-only behavior in shared channels.
Anti-nuke containment saw a privileged bot-account action that was not authorized by Verba or a saved Custom Builder flow. Check Discord audit logs, rotate the token if it was used elsewhere, review permissions, then invite the bot again.
Server reset requires admin/server-owner/bot-owner level permission. DM reset is user scoped.

​
Response quality issues

Increase max tokens and use a fuller reply style. Also check whether your current plan caps output lower than expected.
Tighten system instructions, add focused training examples, and lower temperature.
Increase model context (within plan cap) and avoid splitting related topics across many disconnected chats.
Add or refine knowledge entries, improve titles/categories, and verify entries are active. For URL imports, scrape again and clean the generated draft.
Disable web search for stable topics. Keep it for fresh/live data only.

​
Performance and timeout issues

Reduce context, disable web search, and test a lighter model. Long prompts + web search + high max tokens significantly increase latency.
Retries/backoff are built into the call path, but upstream outages still happen. Retry shortly and keep fallback models available in your plan tier.
Confirm the monthly allowance, model tier, and Image Engine toggle. Then retry with Verba Free Image, a shorter prompt, 1:1, and no reference image to separate configuration from a temporary provider failure.

​
WhatsApp and Telegram issues

Normal restarts retain the gateway’s durable linked-device state. If it is disconnected, check whether WhatsApp revoked the linked device or somebody explicitly logged out before attempting a new link.
Copy a fresh token from @BotFather. A single Telegram token can only be connected to one verb. Revoke and regenerate any token that was exposed.
Mention or reply to it, or have a group admin use /activate_channel. Confirm the bot has permission to read and send messages in that group.

​
Account and billing issues

Top up credits or switch to a lower-cost model. Credits are charged to the account tied to the request/verb owner depending on surface.
Your plan may not include that model tier. Choose an available model or upgrade.
Check header format (Authorization: Bearer vka_... or x-api-key), key revocation status, and whether you exceeded active key limits.
Verba can temporarily block repeated request bursts or repeated blocked traffic. Stop retry loops, wait for the temp-ban window to expire, and send support the timestamp, your public IP if known, and the page/action that triggered it.

​
Chat and group issues

The create flow sends avatar/banner images inline inside the request body. Keep inline avatar and banner files at 1MB or smaller each, or create the verb first and upload profile images afterward.
Anti-spam protections can block mention floods and invisible-character abuse. Remove unusual hidden characters and retry.
Current app chat supports images, video, audio, PDF, Word, and common text/code files up to 30MB per upload. Document text extraction is capped at 20MB; legacy image-only upload controls still use 5MB.
Verify invite code freshness and that owner has not regenerated it recently.
Lower autonomous frequency or disable autonomous mode on that verb. Verba now stops repeated follow-up loops on the same silent DM thread, but a bot that is intentionally configured to be active can still message on its own.

​
When to contact support

Contact support with:
  • Exact timestamp (with timezone)
  • Verb ID/vanity URL
  • Surface (Discord, chat, API)
  • Integration details (WhatsApp or Telegram) when applicable
  • Error text + screenshot
  • Repro steps from clean session

Contact Support

Share reproducible steps and timestamps for fastest resolution.

Community

Ask in community channels for quick operational help.