v2026.7.5
Release date: July 10, 2026
✨ New Features
Restrict channels when starting a conversation
You can now define who can use each channel when starting a new conversation with a customer. The company controls which numbers or support accounts appear for each user profile — reducing risk and organizing the communication flow.
What is it for?
- Show in the channel list only those allowed for the logged-in user's profile
- Restrict a channel to everyone, to specific roles (e.g. managers only), or to specific users
- Automatically hide auxiliary channels when starting a conversation — only the primary channel appears
- Prevent unauthorized users from starting a conversation on a restricted channel, even if they try to force access
How to configure?
- Go to Channels and open the desired channel
- In Settings, find Who can start a conversation on this channel
- Choose one of the options:
- Everyone — any organization member (default)
- By role — select authorized roles (agent, manager, sales, etc.)
- Users — select specific people
- Save the settings
How it works day to day?
- When starting a conversation from a contact (phone, WhatsApp, Instagram, etc.), the platform lists only channels that are compatible and allowed for that user
- Owners and admins still see all primary channels (for operations and configuration)
- If no channel is available for the profile, a clear message is shown
Full guide: Restrict channels when starting a conversation
🔒 Security
Server-side validation when creating a conversation
In addition to hiding channels in the interface, the server validates permission when creating the conversation. Users without access get an error and the operation is blocked — even if someone tries to bypass the on-screen list.
🎯 Benefits
- ✅ More control over who uses each support channel
- ✅ Less risk of sending via unauthorized numbers or accounts
- ✅ Cleaner list when starting a conversation (no auxiliary channels)
- ✅ Server-side protection, not only in the interface
- ✅ Existing channels stay open to everyone until you configure a restriction