Meta Opens Muse Business Calling to Paid U.S. Users | Zeniteq
Loading
Zeniteq is now available on mobile for iPhone, iPad and Apple Watch.Download nowLearn more
Meta Opens Muse Business Calling to Paid U.S. Users
Muse’s paid calling rollout lets subscribers delegate reservations, appointments and hold queues, while disclosure rules and usage limits remain unclear.
Meta has expanded its Muse AI agent to allow paid U.S. subscribers to delegate outbound business calls, such as scheduling appointments or waiting on hold. While this feature enhances productivity, it lacks transparency regarding usage limits, such as call duration or frequency caps, and provides no clear policy on whether the agent must disclose its AI identity to businesses. Users should exercise caution with tasks involving financial commitments, as Meta has not detailed how the agent handles potential cancellation fees or deposits during these automated, non-human interactions.
Meta has opened Muse’s business-calling feature to paid U.S. subscribers, allowing the AI agent to place outbound calls on their behalf. The access change covers tasks such as making restaurant reservations, scheduling appointments and waiting on hold.
Meta chief AI officer Alexandr Wang announced the update, describing the feature as a way to handle “calls you don't want to make,” according to Engadget’s November 12, 2026 report. Access requires a separate Muse subscription.
The news is the broader availability of calling, not Muse’s original launch. Meta introduced the agent in September, and at least one early user had already shared a calling example in October. Paying subscribers now have access to that capability, with an important boundary: this is outbound calling to businesses, not an announced service for answering a user’s incoming calls.
What Muse’s Calling Feature Covers
Muse can contact a business and conduct a conversation for its user. The reported examples include reservations and appointments, along with staying on the line while a business places the call on hold.
That last capability could be particularly useful. Waiting in a queue is a task where delegation can save time even when the eventual conversation is brief. Its value still depends on whether the agent reaches the right person, understands the answer and stays within the user’s instructions.
The announced scope is narrower than a general-purpose AI phone service:
Parameter
What the rollout covers
Access
A paid Muse subscription
Geography
U.S. subscribers calling U.S. businesses
Call direction
Outbound calls placed on the user’s behalf
Reported tasks
Reservations, appointments and waiting on hold
Incoming calls
Not part of the announced feature
Free-tier or wider international access
No expansion announced
A reservation and an appointment also involve different levels of authority. Asking a restaurant whether it has a table available is an information request. Accepting a reservation with a cancellation fee creates a commitment. Similarly, asking a service department for its next opening is different from authorizing paid work.
My view is that this distinction matters more than the number of business categories Muse can reach. A useful calling agent needs to understand both the desired outcome and the point where it should stop and ask permission.
What Changed Since Muse’s September Launch
Meta’s September 8 introduction described Muse as an agent that could open a browser, fill out forms and negotiate on a person’s behalf. Users could give it tasks through the Muse app or WhatsApp, and it could continue working after they closed the app.
Meta also said Muse would seek approval before sensitive actions such as sending an email or making a purchase. Those were part of the company’s published description of the broader agent.
Calling adds another way for Muse to complete work:
Published stage
What it tells readers
September 8 introduction
Muse could work through websites, forms and connected services, with approval described for certain sensitive actions.
October 9 user-shared example
A Meta employee showed an early example of Muse contacting a Volvo dealership.
November 12 rollout report
Business calling became available to paid subscribers.
The October example helps establish that calling existed before the November access announcement. It is not a newly invented capability appearing for the first time in this update.
The practical change is access. For a business that handles bookings or availability by phone, Muse now has a route that does not depend on a usable web form. That could let the agent carry a task further without handing the phone portion back to its user.
There is still a documentation gap between Meta’s general approval promises and telephone-specific behavior. The launch post explains approval for email and purchases, but the available calling announcement does not spell out how the agent handles a deposit, a cancellation charge or another commitment introduced during a live conversation. Those situations should not be treated as covered by a detailed phone policy simply because the wider agent has approval controls.
A Paid Subscription Is Not a Published Call Allowance
The available announcement and reporting leave several practical questions unanswered:
Call count: How many calls can a subscriber place within a given period?
Duration: Is there a maximum call length, and does time spent on hold count toward it?
Retries: What happens to the allowance when a business does not answer or a call disconnects?
Business coverage: Are particular categories supported, restricted or excluded?
Billing: Is calling included entirely within the subscription, or subject to additional usage rules?
Tokens are units used to process model input and output. A token allowance alone cannot tell a subscriber how many minutes of calling they receive without a published rule connecting the two.
I’d check the current calling terms before subscribing specifically to outsource long hold queues. A feature can be available while still having limits that make a particular use case impractical. A short reservation call and a lengthy customer-service queue place very different demands on a voice service.
No independent call-success benchmark accompanies the reporting, either. The announced examples explain what Muse is intended to do; they do not tell readers how consistently it completes those tasks.
The clearest published example comes from Matt Schlicht, a Meta Superintelligence employee and the creator of Moltbook. Engadget reports that Schlicht shared a recreation of a conversation in which his Muse called a Volvo dealership to ask about appointment availability.
Schlicht said the agent waited on the line for 15 minutes. His post is an individual account from someone employed by Meta, not an independent assessment of typical performance.
The disclosure detail is more consequential. According to Engadget’s account of the recreation, Muse said it was calling on Schlicht’s behalf and that it was transcribing the call, but it did not explicitly identify itself as an AI agent.
Those statements communicate different things:
Calling on someone’s behalf explains whose task the caller is handling.
Saying the call is being transcribed explains one way the conversation is being processed.
Identifying as AI explains what kind of caller the business is speaking with.
One statement does not necessarily communicate the others. A business employee could reasonably hear “calling on behalf of” and assume they are speaking to a human assistant.
The single recreation cannot establish Muse’s behavior across all calls. It also cannot establish a universal disclosure policy. The unresolved question is whether explicit AI identification is required on every call, varies by context or is handled another way.
My preference would be clear identification at the beginning of the conversation. It would give the business a straightforward basis for deciding whether to continue, transfer the call or request contact with the customer. That is a product-design judgment, not a claim about a legal requirement or Meta’s current policy.
How to Give a Calling Agent a Bounded Task
Meta’s broader Muse documentation describes a system that accepts instructions in ordinary conversation. It does not provide a detailed calling setup sequence in the material supporting this rollout, so there is no verified series of buttons or settings to reproduce here.
The useful preparation is to define the task precisely. A request to find an available appointment leaves several decisions open: which location, which dates, what price and whether the agent may confirm a booking.
A more bounded request would supply:
The destination: The business name, location and correct department.
The goal: Ask for information, request a reservation or confirm a particular appointment.
Acceptable alternatives: A date range, time window or spending limit.
Permission boundaries: Whether the agent may accept fees, change an existing booking or make a commitment.
The required result: The agreed date, location, price and any confirmation or cancellation terms.
These are suggested instruction practices, not tested safeguards or guarantees about Muse’s behavior.
For an initial task, I’d favor something reversible and easy to verify, such as asking a business for availability. The reasoning is straightforward: an incorrect answer can be checked before it becomes a missed appointment, an unwanted charge or a change to an account.
A completed call should also produce a useful outcome. “The business answered” is different from “the appointment is confirmed.” For bookings, the details worth checking include the correct location, date, time and any conditions the business attached.
Muse’s paid rollout makes voice delegation available to more users. The next useful detail from Meta would be a calling policy that connects access, spending authority, usage limits and disclosure, so subscribers can judge which tasks they can safely hand over.
Frequently Asked Questions
3 questions
1
Is Muse’s Business Calling Feature Free?
No. The announced rollout requires a paid Muse subscription. Free-tier calling access has not been announced.
2
Can Muse Answer Incoming Calls?
Incoming-call handling is not part of this announcement. The feature covers outbound calls to U.S. businesses on a subscriber’s behalf.
3
Does Muse Always Identify Itself as AI?
That remains unclear. Engadget described one user-shared call recreation without explicit AI identification, but that example does not establish how Muse behaves on every call.
