Multi-Session & Account Limits
BotWave supports running multiple sessions in parallel — useful for managing several WhatsApp numbers, multiple Telegram bots, or one-of-each.
Per-Plan Limits
| Plan | WhatsApp sessions | Telegram bots | Telegram userbots |
|---|---|---|---|
| Free | 1 | 1 | 0 |
| Pro | 3 | 5 | 1 |
| Business | 10 | 25 | 5 |
| Custom | Negotiated | Negotiated | Negotiated |
Session Isolation
Each session is fully isolated:
- Separate auth state
- Separate command toggles
- Separate analytics
- Independent rate-limit buckets
Disconnecting one session does not affect any other session.
Naming Sessions
Sessions get auto-generated IDs (e.g. sess_abc123). You can also give each one a friendly name (e.g. "Support line", "Marketing bot") in the session settings.
Group Overlap
If two of your sessions are in the same group, only one will respond to a given command (the session with the longest uptime in that group). This prevents double-replies.
Best Practices
- Use one session per use-case, not per group. A single session can serve many groups.
- Don't connect the same WhatsApp number on multiple browsers or devices outside BotWave — it can corrupt auth state.
- For multiple personalities, use per-group system prompts (see AI Providers) instead of separate sessions.