How to connect Email as a shared inbox
Turn your support mailbox into a shared inbox inside Omnifox so your whole team can reply from one place.
With the Email channel you can receive and reply to messages from your support mailbox (for example, [email protected]) right inside Omnifox. Each thread becomes a conversation your team can assign, tag, and resolve like any other message.
Before you start
- Administrator access in Omnifox.
- An account with an email API provider (SendGrid, Mailgun, or Postmark) and its API key, or the SMTP credentials of your mailbox.
- Access to your email provider to set up inbound forwarding to Omnifox.
Step 1: Add the Email channel
- Go to Settings → Channels.
- Click Connect channel and choose Email.
- In the Provider field pick the sending method: SendGrid, Mailgun, Postmark (by API key) or SMTP.
Step 2: Connect your mailbox
If you use an API provider (SendGrid / Mailgun / Postmark):
- Paste your provider API Key.
- Fill in From Email (the sender address) and From Name (the name customers will see).
If you use SMTP:
- Enter the SMTP Host, Port (usually
587), Username, Password, and Encryption (TLSorSSL). - Fill in From Email and From Name.
Step 3: Set up inbound (receiving)
- Copy the Inbound Webhook URL shown in the channel form.
- Paste it into your provider's inbound settings (SendGrid Inbound Parse, Mailgun Routes, etc.) so customer replies come back into Omnifox.
- Point your receiving domain or subdomain to that URL following your provider's instructions.
Step 4: Test the shared inbox
- Send a test email to your support mailbox from another account.
- Confirm the message shows up as a conversation in Omnifox.
- Reply from Omnifox and check the email reaches the sender correctly.
- Assign the conversation to an agent to test the team flow.
Best practices
- Use tags and assignments so two agents don't reply to the same email.
- Enable auto-replies or an AI agent for instant acknowledgements.
- Configure your sending domain (SPF/DKIM) to improve deliverability.
Final tip: stop the team from using the old mail client in parallel. Centralizing everything in Omnifox prevents duplicate replies and keeps the full customer history in one place.
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.