Connect your sales, support, or billing inbox over SMTP and IMAP and stop passing around passwords. Your whole team replies from one screen, with the customer's full history right there: their emails, their WhatsApp messages, and their website chats on the same profile.
7 days free. No credit card. Included in every plan.
A shared inbox like sales@ or support@ usually ends up the same way: three people sharing one password, two of them answering the same message, and nobody sure whether someone already replied. Email becomes the one channel in the company with no assignment, no history, and no metrics.
Once that inbox is connected to Omnifox, every incoming email opens a conversation just like any other channel: it gets assigned to a person or a team, tagged, answered with canned replies, escalated, and closed. The difference is that the reply goes out as a plain, ordinary email, under your domain and your branding, not ours.
And the real payoff shows up when a customer reaches out through two channels: if the same contact sends you an email and then a WhatsApp message, your agent sees both in the same profile instead of treating them like two different people.
The same inbox you've always had, now backed by a team, assignment, history, and automation.
The same tools you already use for chat, applied to the oldest channel of all.
No one shares passwords or forwards emails by hand anymore. Every conversation is assigned to a person or a team, with automatic round-robin or workload-based routing.
We use the email's real headers to chain replies, so the customer sees a clean thread in their Gmail or Outlook, and we reopen the right conversation even if it had already been closed.
AI agents don't care which channel they're on: the same agent handling your WhatsApp can read, classify, and reply to emails, or draft a response and let a person approve it.
Tag by subject, route to the right team, request a satisfaction survey on close, or trigger a full workflow with the visual editor. No code required.
Emails go out with your business's name and logo in the header. The "sent with Omnifox" footer can be turned off per channel if you'd rather not have it.
We filter out auto-replies, newsletters, bounces, and delivery receipts so they don't clutter your inbox or reopen closed conversations. Hard bounces and complaints go straight to an automatic suppression list.
The same thing you already do, minus the parts that hurt.
| A regular shared inbox | Email channel in Omnifox | |
|---|---|---|
| Multiple people handling it | Shared password | Individual users and permissions |
| Knowing who's replying to what | ||
| Automatic routing | ||
| Unified history with WhatsApp | ||
| Saved replies | Copy and paste | Team canned replies |
| AI Agents | ||
| Visual automations | ||
| Satisfaction survey | ||
| Segmented campaigns | ||
| Response time metrics |
No migrating your email anywhere, and no switching providers.
SMTP server, port, username, and password. You can also use SendGrid or Mailgun with their API key. Credentials are stored encrypted.
IMAP with its folder, or a webhook if your provider offers one. There's a button to test the connection before you save.
You decide who handles that inbox, how conversations get routed, and which tags or workflows trigger when an email comes in.
If you want, turn on an AI agent to classify, reply, or draft a response for a person to review.
We'd rather you know this now than the day you need it.
The connection runs over SMTP and IMAP, which works with Gmail, Outlook, Zoho, cPanel, or any provider, but it asks for your server details instead of a "sign in with Google" button. If your inbox has two-step verification, you'll need an app password.
Today, replies go out to the sender only. If you need to loop in anyone else on the thread, you still have to do it from your own email client.
The header carries your business's name and logo, but there are no personal per-agent signatures at the bottom of the message.
Incoming emails over IMAP can show up in the inbox with up to a couple of minutes' delay. It's not an instant channel like chat, and with email that rarely matters.
Automatic message translation works in chat, not in email: an email carries a subject line, a signature, and quoted thread history along with it, and translating only the body leaves you with half a message. We'd rather not do it than do it badly.
This channel is built for support, not for uncontrolled bulk sending: there are per-minute, per-hour, and per-day limits, plus a separate cap for cold emails. For high volume, use campaigns, which come with their own unsubscribe and suppression handling.
Several of these are on our improvement list. If one of them is blocking you, tell us: knowing who needs it is what moves it up in priority.
Another question? [email protected]
Connect your inbox over SMTP and IMAP and handle it alongside WhatsApp, Instagram, and your website chat. Included in every plan. 7 days free, no card required.