Front Channels Explained (2026): Email, Chat, SMS, Social & Voice in One Inbox

What a channel actually is

In Front, a channel and an inbox are not the same thing — and understanding the split is the key to everything else. Per Front's guide to shared inboxes, an inbox is "an organizational space where you can categorize or sort conversations," and it "can have channels such as email, Instagram, or SMS feeding into it, or can have no channels and be an empty inbox."

So the channel is the pipe; the inbox is the bucket it pours into. When you connect a channel, Front asks you to "select the inbox to connect to your channel," and from then on "all messages from your channel will route to this inbox by default." One inbox can gather several channels — your support inbox might take email, SMS, and Instagram at once — which is exactly how Front collapses an omnichannel workload into a single collaborative surface.

You manage all of this in one place: Settings → Channels → Connect channel. That screen shows the channels you already have connected and cards for every channel type you can add.

The full channel map

Front's omnichannel inbox supports a wide spread of channel types. Here's the map, grouped by kind.

Email is the foundation, and it connects two ways (covered in the next section): native sync for Google/Gmail and Microsoft/Office 365, or forwarding for any other provider.

Front Chat is Front's own live-chat channel — a widget you embed on your site or app, with support for chatbots so you can capture and triage conversations before a human picks them up. It's a native channel, not a third-party bolt-on.

SMS and voice run through Twilio. You connect your Twilio account and phone number, and inbound texts (and calls) land in the inbox alongside everything else, with the same reply, assign, and comment tooling.

WhatsApp lets you send and receive on a WhatsApp Business number inside Front, using approved message templates for outbound. Note the commercial detail up front: Front positions WhatsApp as a paid premium add-on, not something bundled into a standard plan.

Social covers Facebook, Instagram, and X — posts, comments, and direct messages flow into the inbox so social replies live next to email and chat rather than in a separate tool.

Slack can be handled as a support channel too, for teams who field structured requests through Slack.

Custom channels cover everything else. Front exposes an open Channels API so you can build a channel for any source that isn't natively supported and push messages into an inbox programmatically — the same mechanism partners use to ship their own Front channels.

Native connect vs forwarding

This is the distinction that decides how well a channel behaves, and it's easiest to see on email.

Native connect means Front talks directly to the source's API. For Gmail/Google and Microsoft/Office 365, Front syncs your mailbox two ways — inbound and sent — so replies you send from Front, and even replies sent from the native app, stay in sync. Twilio SMS, WhatsApp, and the social channels are all native in the same spirit: a live, two-way link with full collaboration on top.

Forwarding is the fallback for email providers Front doesn't sync natively. As the getting-started walkthrough describes, you pick Other emails on the channel setup screen, Front hands you a unique forwarding address, and you configure your mailbox to auto-forward mail to it. Messages then land in the inbox — but the link is one-directional at the source, so you'll typically also configure custom SMTP (your own outbound server, authenticated with SPF/DKIM/DMARC) so sent mail is delivered and retained correctly rather than going out through Front's default servers.

The practical rule: native connect gives you clean two-way sync and less setup; forwarding gives you reach into providers Front can't sync, at the cost of more moving parts. If you're on Gmail or Microsoft, connect natively. If you're on anything else, forwarding plus custom SMTP is the supported path.

The per-channel quirks worth knowing

Channels look uniform once they're in the inbox, but a few have setup gotchas that are worth naming before you commit.

SMS via Twilio is Professional-tier and up. Per Front's Twilio SMS setup guide, you connect using your Twilio Account SID and Auth Token and a phone number or shortcode. Three quirks matter: Front imports only "100 of the most recent" Twilio messages into the Archived tab on connect, so older history won't appear; Twilio allows only one webhook per number, meaning if another app is already pointed at that number, connecting Front can override it (or be overridden); and you can broadcast to up to 200 contacts at once, but group SMS threads aren't supported. If you're using A2P 10DLC numbers, your Messaging Service must be set to "Defer to Sender's Webhook" or messages won't route.

WhatsApp is an add-on, not a plan feature. Budget for it separately — it's licensed as a premium add-on on top of your plan, and outbound messaging outside the 24-hour window requires pre-approved templates, which is a WhatsApp platform rule, not a Front limitation.

Front Chat brings chatbot behaviour that the other channels don't. It's the one channel where you're designing a pre-human capture flow, so it needs its own thought about routing and business hours.

Email forwarding needs SMTP hygiene. Forwarded email works, but without custom SMTP your outbound deliverability and sent-mail retention can suffer — this is the single most common "why did my reply not send properly" surprise for teams not on native Gmail/Microsoft sync.

The honest limits — and where an AI layer fits

Front's channel model is genuinely strong: consolidating email, chat, SMS, social, and voice into one collaborative inbox is exactly what most teams juggling five tools actually need, and the native connectors are solid. Credit where it's due.

But two honest caveats. First, the good stuff is tiered. SMS/voice sits behind Professional+, WhatsApp is a paid add-on, and richer routing lives higher up the plan ladder — a small team can find that the omnichannel picture they signed up for costs more than the base price implied. Front's pricing tiers lay out what unlocks where. Second — and this is the structural one — a channel delivers a message; it doesn't answer it. Front routes an Instagram DM and an SMS into the inbox flawlessly, but a human still has to read each one and write the reply. Across five channels, that reply volume is exactly the same whether it arrives by email or WhatsApp.

That's the seam an AI agent layer fills — not by replacing your channels, but by working across all of them once they're unified. The category of AI agents for customer service exists for precisely the read-and-respond work a channel connector structurally can't do. Macha is one such layer: it runs on top of the Front you already use through the live Macha–Front connector — it does not replace Front, your inboxes, or your channels. Because every channel already funnels into one inbox, Macha's agent can read any incoming conversation regardless of whether it arrived by email, chat, SMS, or Instagram, and draft or send a grounded reply — pulling a real order or account status through a custom tool that turns your REST API into something the agent can call. The channel gets the message to the inbox in seconds; the agent then actually resolves it. If you want the mechanics, connecting Front to Macha to route conversations to AI walks through it, and Macha's credits are consumed per AI action, never per resolution — moving a message and reasoning about it are different jobs with different costs, and it's honest to price them that way.

The clean division of labour: let Front's channels be the omnichannel front door, let Front rules and tags organise what arrives, and layer an agent on top to read and answer across every channel at once. For how the inbox itself works underneath all of this, see the Front shared inbox model.

FAQ

What channels does Front support? Email (via native Gmail/Microsoft sync or forwarding), Front Chat live chat, SMS and voice through Twilio, WhatsApp, social channels (Facebook, Instagram, X), Slack, and any custom channel you build on Front's open Channels API. All of them can feed one or more shared inboxes.

How do I add a channel in Front? Go to Settings → Channels → Connect channel, pick the channel type, follow the provider-specific setup, and choose which inbox the channel routes to. By default every message from that channel lands in the inbox you select; one inbox can hold several channels, and an inbox can also have no channels at all.

What's the difference between connecting a channel natively and forwarding? Native connect is a direct, two-way API link — used for Gmail/Google, Microsoft/Office 365, Twilio SMS, WhatsApp, and social — with full sync of inbound and sent messages. Forwarding is the fallback for email providers Front doesn't sync natively: you auto-forward mail to a Front-provided address (the "Other emails" option) and usually add custom SMTP for reliable outbound.

Is WhatsApp included in Front? No — Front offers WhatsApp as a paid premium add-on on top of your plan rather than a bundled channel, and outbound messages outside the 24-hour window use WhatsApp-approved templates. SMS and voice via Twilio require a Professional-tier plan or higher.

Can I add AI across all my Front channels without replacing Front? Yes. An AI agent layer like Macha connects to Front as a live connector and works on top of your existing inboxes and channels. Because email, chat, SMS, and social already funnel into Front, the agent can read any incoming conversation regardless of channel and draft or send a grounded reply — your channels and routing stay exactly as they are.

Ready to answer across every Front channel from one AI layer? Start a free trial of Macha and connect it to your Front in minutes.