Meta Muse for Front: how Meta's AI fits your WhatsApp inbox in 2026

What "Meta Muse for Front" actually means

I spend a good share of my week inside other companies' developer docs, and Meta's 2026 naming is the part that needs the most untangling. There are three Meta products in play here, and only one of them is actually talking to your customers:

1. Muse, the personal AI agent Meta launched in September for consumer errands. It is not built to answer a business's customers.
2. Muse Spark 1.3, the model, sold through the Meta Model API. You can build a Front bot on top of it, which is a route I cover further below. The Muse Spark 1.3 overview has the model detail.
3. Meta Business Agent, which Meta launched in June as the AI that answers your customers on WhatsApp, Messenger and Instagram. This one is the product a Front team is really weighing up.

The three-way breakdown lives in my Meta Muse for customer support guide. Here I zoom in on the Front side, meaning what happens to your WhatsApp channel and your shared inbox, and also to your bill, once Meta's agent joins. If you run a different helpdesk, the Meta Muse for Zendesk and Meta Muse for Gorgias posts cover those.

How WhatsApp works in Front today

Before Meta's agent enters the picture, it helps to know first what your Front WhatsApp channel already is. Front's native WhatsApp channel connects numbers "directly to Front, without going through third-party providers." You connect through Meta's embedded signup (Settings, Inboxes, Channels, Connect channel), pick an inbox, then each new WhatsApp chat lands as a Front conversation that your team can assign and comment on, or archive, the same as an email.

There are a few details in Front's own docs that shape everything after this:

• WhatsApp is a paid add-on on Professional and above. Per Front's pricing page, that means $65 per seat per month or the $105 Enterprise plan before the add-on. The add-on is billed as "total monthly WhatsApp cost billed from Meta plus a 20% administrative fee", and there is a 14-day trial which covers 100 conversations.
• Front can already put an AI on the number. Front's Autopilot docs list WhatsApp (native), WhatsApp via Twilio and Yalo WhatsApp as supported channels. So it's possible your number already has an AI answering on it.
• History doesn't come over. "Historical messages will not be imported into Front", and neither WhatsApp Flows nor group chats are supported.
• It's the Platform, not the app. Front integrates with the WhatsApp Business Platform only. Moving from the free WhatsApp Business app "can involve loss of data", per the same article.

For the wider Front feature set my Front review walks through it, and the Front pricing post has every plan and add-on.

The number itself is quite sticky too. Front's migration guide asks you to switch off two-step verification and re-register the number, and if your provider owns the WhatsApp Business Account, "you will have to contact them." So whichever AI ends up getting the seat, make the pick on purpose.

What happens when Meta Business Agent joins your Front number

Meta's docs got a lot more detailed in September, and for a shared-inbox team the new detail changes the picture by quite a bit.

It becomes the first responder, and Front moves to standby

Meta's Conversation Routing decides which app answers each message when more than one app is connected to a number. Your Front channel counts as one of those apps. When you turn on Business Agent, "The agent becomes the sole primary for messaging entry points" and "Previous primary destinations move to standby so they retain context", per Meta's routing setup guide.

Put in plain terms, new WhatsApp messages reach Meta's agent first and not your Front inbox. You can split this by entry point, for example keeping Front as primary for direct messages and putting the AI on click-to-WhatsApp ads. That setup only lives inside Meta Business Suite though, and Meta is quite blunt on this: "There is no public API for configuring Conversation Routing."

One AI per number, so Autopilot and Business Agent can't share

Meta's Platform overview spells out the eligibility rule: the number must be "Not already running another AI agent on that number", because "an active authorized-agent integration blocks Meta Business Agent."

Meta doesn't define what counts as an "authorized-agent integration". The plain reading, which is also the one I'd plan around, is that Autopilot answering on the number counts. So it's a choice, not a stack. If Autopilot handles your WhatsApp conversations today, adding Meta's agent means you switch Autopilot off on that number first, then your Playbooks stop running there.

Handoff goes back through the thread, and Front isn't a named partner

When Business Agent hands off, the chat doesn't move to some Meta inbox. The conversation stays in the same WhatsApp thread, and what passes to another app on the number is only the ownership. Meta's customer support guide lists "A staffed destination for handed-off conversations" as a prerequisite. A plain handoff goes to whichever app you set as the "escalation partner", per the thread control docs.

For a Front team the escalation partner would be Front's own WhatsApp app, as Front is the provider on the number. When Meta introduced Business AI (the earlier name for Business Agent), it named its handoff partners: "Salesforce, Microsoft Dynamics 365 Contact Center, ServiceNow, Zendesk, Gorgias and Klaviyo Service." Front isn't on that list, and I couldn't find any Front help article which mentions Business Agent at all. Going by Meta's routing docs, a handoff should still land in your Front inbox as a normal conversation, as long as Front is the escalation partner. Nobody on either side has documented that flow yet, so I would test it on a spare number before trusting it.

A few more handoff details worth knowing:

• Context travels in a 2,000-character note. The handoff event carries a free-text metadata field that Meta suggests using "to carry the ticket or order reference". What your team gets is either an AI summary of the chat or a live copy of it, never both.
• You don't control the triggers. On the Platform, handoff fires on low confidence or on integrity issues, plus when the customer asks for a human, and "You do not configure the triggers," per Meta's capabilities page. The Zendesk side of this is covered in my Zendesk WhatsApp handoff post.
• Meta warns about the 2am handoff. Its own guide says: "An agent that hands off at 02:00 into an unstaffed queue produces a worse outcome than one that says when the team is next available and raises a ticket."

One BSP consultant who had early Platform access summed up the controls like this:

"The harness is very basic. You only get 4 controls - knowledge, personality, audience, handoff. Fine for a simple FAQ or catalog bot. But if you want real step-by-step logic, you hit the wall fast."

u/Kira_SENPAI_1, Reddit

Front's API token fits Meta's connector auth, its MCP server doesn't

Business Agent takes actions through connectors, which is to say HTTP APIs or remote MCP servers that you define yourself. Meta's support guide even shows a worked create_support_ticket tool. On the Freshdesk and Gorgias posts, this is the place where things broke, because those APIs want Basic auth, and Meta's connectors reference says "only OAUTH2_CLIENT_CREDENTIALS, API_KEY, and NONE are supported."

Front is different. The Front Core API takes an API token as a bearer header, and Meta's API_KEY type lets you name the header and set a prefix. So an Authorization header with a Bearer prefix should work, at least on paper. That makes Front one of the easier helpdesks to wire to Business Agent. You could for example add an internal comment, or tag a conversation, before the handoff lands.

Front's MCP server is the opposite story. It uses OAuth 2.1 with PKCE, and every token is bound to one Front teammate, which is the right design for an assistant but it doesn't match with Meta's client-credentials flow. The Claude for Front post goes deeper on what that server can do.

There are two things to keep in mind if you are building the connector. Front's API rate limits run 50, 100 or 200 requests per minute by plan, shared across the whole company. Meta itself also flags the silent-failure risk: "A failed ticket is invisible: the agent has already said a colleague will be in touch, the shopper waits, and nobody finds out until they message again angrier."

What it costs: Meta Business Agent vs Front Autopilot on WhatsApp

The two AIs bill in completely different units, and both of them sit on top of the WhatsApp fees you already pay through Front.

So on a pure per-conversation basis, Meta's agent comes out cheaper than an Autopilot resolution in every example that Meta publishes. The gap only narrows when a customer keeps on asking follow-ups, because Meta's bill grows per message while the Autopilot one stays flat per outcome. Early users noticed the per-message part fast:

"My concern is that the per-message cost is insanely high at approximately 5 cents per message."

u/Aromatic-Surround167, Reddit

On the Autopilot side, Front's outcome rules also move the number. You aren't charged when a teammate cancels an automation or the customer asks for a human, and the same goes when Autopilot fails on Front's side. That is a fairer model than per-reply billing, and it's worth reading in full. The Front Autopilot deep dive covers Playbooks and setup, and my Front AI overview has the rest of the AI lineup.

October 1 hits the human side of your inbox

The change that most Front teams will actually feel is not the AI price. From October 1, 2026, Meta charges service messages per message after 1,000 free per phone number per month. Service messages in this context means the replies from a person or from a third-party AI, and Meta's pricing page says each message is billed "either as a Meta Business Agent message or as a service message, never both."

In practice, every WhatsApp reply your team sends from Front after a handoff is a service message, and so is every reply Autopilot writes, then Front's 20% goes on top. Picking Meta's agent doesn't dodge that line, it only changes who is writing the first few replies. My WhatsApp API pricing explainer has the full rate history, and the earlier Meta policy changes post covers what Meta did to third-party bots.

Building your own Front bot on Muse Spark

The third route skips Business Agent entirely and builds straight on the model. It's the closest one to my day job, so here's what it involves in reality.

On the model side, Muse Spark 1.3 costs $1.25 input and $4.25 output per 1M tokens on the standard tier (Meta Model API docs), with tool calling and structured output. The cheaper contributor tier is off the table for support, because Meta's terms say "You must not submit sensitive, confidential, or personal information to the Discounted Services." A Front conversation is full of names and emails, and order numbers too. My Muse Spark 1.3 review covers where the model is strong.

On the Front side, everything else is yours to own:

1. Knowledge. Help center articles, message templates and past conversations, kept in sync. Front's API gives you conversations and messages, but pulling years of history against a 50 to 200 requests-per-minute limit takes planning.
2. The conversation loop. Reading the conversation, then drafting a reply or leaving a comment, also setting tags and assignees. Front's API has no edit or unsend for a sent message, so for a first version I'd ship it writing drafts only. Front's drafts:write and messages:send are separate scopes, so it's possible to mint a token that physically can't message a customer.
3. Escalation. Your own confidence threshold and routing rules. My AI agent handoff guide covers what a good one looks like.
4. Testing. Replaying real conversations before anything reaches a customer.
5. The WhatsApp side. Templates, the 24-hour window, and the October 1 service-message charges. Front does match template text automatically when you send through its channel API outside the window, which helps.

I've watched plenty of teams weigh up this path, and my advice every time is to count in the maintenance, not only the build. My build vs buy guide lays out the full list. For the same build on other models, see ChatGPT for Front and Grok for Front.

Front is also moving on this. Its external agents page has a beta waitlist for bringing agents "built with platforms like Claude and Codex, or come from providers like Sierra, Decagon, Forethought" into Front as teammates. Meta isn't on that list, but the direction is clear enough, Front wants outside AI to run inside the inbox and not beside it.

Where Meta's agent stops for a Front team

None of this is hidden, it's all in Meta's own docs, but it lands harder when your team works from a shared inbox:

• It only answers in Meta's apps. Your Front inbox carries email, chat, SMS and often Slack too. Business Agent covers none of them, so you would end up running two AIs with two sets of rules. My Front chatbot post covers the non-WhatsApp side.
• Your conversation history isn't a knowledge source. Meta's support guide tells you to "export the top drivers from your helpdesk for the last quarter" and write FAQ entries by hand. Your best answers, which are sitting in years of archived Front conversations, stay out of its reach.
• Regulated industries are excluded. Businesses in finance, health, government, alcohol or gambling can't use the Platform.
• English is strongest on both sides. Meta notes English performs best, and Front says of Autopilot that "Only English is officially supported at this time." If your WhatsApp audience is multilingual, it is worth testing hard either way. The Front AI Translate post covers Front's translation layer.
• Accuracy still needs grounding. Meta's help center warns "Some AI messages may be inaccurate or inappropriate", and an early tester saw "the same product come back at two different prices in two replies" (Reddit).

The ask I hear the most from support leads is the one that a CX lead at a direct-to-consumer brand, doing about 7,000 tickets a month, put to the eesel team:

"I need an AI who is only handling the tickets that it's confident to handle and all the other ones, leave them alone."

With Business Agent it is Meta who draws that confidence line, not you. For a lot of Front teams, that one detail is what decides it.

Which setup fits your Front team

Here's how I'd pick, based on where your customers write in and on how your team works.

For most of the Front teams I talk to, the second row is the real one. A customer writes on WhatsApp and follows up by email, then later replies to a CSAT survey, and your team needs all of that in one Front conversation, not split between Front and Meta. That's the reason the AI choice inside Front matters more than the Meta question does.

One commenter in r/SaaS made the same point, about where the value sits once Meta gives the basic automation away:

"When Meta ships the basic automation for free, SaaS value has to move up the workflow. The durable layer is cross-channel context, approval and exception handling, reporting tied to campaigns, and knowing when automation should stop and a human should take over."

u/ayecl, Reddit

If you're comparing those, my best AI for Front roundup and the Front AI alternatives list are good next reads. The head-to-head Front AI vs eesel post goes deeper on those two.

For WhatsApp across different tools, see the best AI for WhatsApp support.

Try eesel for WhatsApp in Front

eesel is an AI helpdesk teammate that joins Front like a new hire would, with no separate widget and no second inbox. It works your conversations inside Front and replies in whichever channel the customer used, and it also connects to WhatsApp directly. It learns from your past Front conversations and your help center, plus your message templates. Before it answers a single customer, it runs a simulation against hundreds of your past conversations, so you get to see which ones it would get right, and after that you choose the conversation types it's allowed to touch. It follows the inbox rules and assignments you already have, and your business hours too.

Pricing is a fixed monthly credit plan, where a ticket or chat counts as one credit however many replies it takes, so a customer asking five follow-ups doesn't multiply the bill. If you'd rather script the setup, the eesel CLI lets you, or a coding agent like Claude Code, connect Front and add knowledge, or approve actions, from a terminal, with JSON output for every command.

Try eesel free with 100 credits and no card, and see how it handles your Front WhatsApp conversations before the October 1 pricing change lands.