Channel best practices: names, multiple of the same type, and credential security
Recommendations for naming your channels clearly, running several channels of the same type without confusion, and keeping each connection's credentials secure.
As you add more channels, good organization prevents routing mistakes, replies from the wrong number, and security leaks. These are the practices we recommend to keep your channels tidy, scalable, and secure.
Name your channels clearly
The channel name appears in the Channels list, in the Inbox filters, and next to every conversation. A good name tells you at a glance what it's for.
- Open Channels from your workspace settings.
- Click the channel name (you'll see the Click to edit the name tooltip).
- Use a consistent pattern: area + type, for example
Sales · WhatsApp,Support · WhatsApp,Marketing · Instagram. - Avoid generic names like "WhatsApp 1" or "New channel".
Multiple channels of the same type
Omnifox lets you connect several channels of the same type (for example, two WhatsApp numbers or two Instagram accounts). To keep them from clashing:
- Give each one a name that distinguishes its purpose (Sales vs. Support).
- Assign them to different teams so each conversation reaches the right group.
- In the Inbox, use the Specific channel filter to work one number at a time.
- Check that templates and workflows point to the correct channel before turning them on.
Credential security
Each channel stores sensitive credentials (access tokens, webhook secrets, API keys). Protect them like this:
- Don't reuse tokens between Omnifox and other tools: if you revoke the token elsewhere, the channel will go into Error.
- Connect through the official flow (Meta Embedded Signup, Telegram BotFather) instead of pasting manual tokens when possible — managed tokens refresh themselves.
- Limit who manages channels: only roles with the settings permission should connect, edit, or disconnect channels.
- Rotate credentials if you suspect a leak, then reconnect the channel.
Verification
After organizing your channels, open the Inbox and confirm the Channel filter shows clear, distinct names. Each channel should read Connected (green) after the next health check.
If it isn't working
- Two channels get confused in routing: make sure each has its own team and workflows; similar names alone aren't enough.
- A channel goes into Error after you change credentials: reconnect it through the official flow to refresh the token.
- You can't edit a channel: your role probably lacks the settings permission; ask an administrator.
Tips
Put the owning team in the channel name: it makes it easy to audit who handles what as you grow.
Before disconnecting a channel, pause it first and watch for a few days: sometimes the problem was temporary and you avoid losing the configuration history.
Related articles
Related articles
-
WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.