Meta's Muse started placing real phone calls to US businesses on November 12, and a Reddit developer got Claude Code to order dinner by phone the same week: here is what that changes about the line your team answers, and about the calls you make.
Your phone just became an agent-to-agent channel
On Wednesday, somebody on r/ClaudeCode posted four words that should reorganize your week: "I asked Claude Code to order my dinner." It phoned the restaurant. The developer published the receipt. Eighty-nine seconds. Eleven cents. The agent disclosed it was AI, gave the recording notice, and worked through the IVR menu without help.
The same day, TechCrunch reported that Meta turned on outbound calling for Muse, its consumer agent, for paying US subscribers. Alexandr Wang, Meta's chief AI officer, framed it as the calls nobody wants to make. Insurance. Cable. The DMV. A restaurant with no online booking.
Here is the direct answer. Your business phone is now a channel where software talks to software, in both directions at once. Inbound, some share of your callers are no longer people, they are agents working for people who still have money and still want to buy. Outbound, you can place AI calls to your own list for about the price of a stamp. The correct response is not to pick a side. It is to write down, this month, what your team does when a caller discloses it is an AI, and to decide separately whether your business will place those calls itself.
Most owners will do neither. They will let the front desk improvise. That improvisation is going to cost somebody real bookings before Christmas.
Key Takeaways
- Your main line is now an agent-to-agent channel in both directions, and the agent on it carries a real customer's real intent.
- Meta tested human contractors on Muse calls after merchants hung up on the AI, so the hang-up reflex is already widespread.
- The FCC's February 2024 ruling put AI voices under the TCPA, making outbound a consent problem before a technology problem.
- Agent transaction volume is still tiny: Uber reported four agent-booked rides out of 320 million trips in a peak week.
- Write the inbound rule first, because it costs nothing and protects revenue you already earned.
The problem nobody at your front desk has been briefed on
I have watched this pattern three times now in the AI cycle, and it goes the same way. A capability ships. Builders get excited. The people who answer phones get nothing: no memo, no script, no policy. Then a customer has a bad experience, the owner blames the technology, and the business ends up with an informal rule invented by whoever was on shift that Tuesday.
That is where we are with agent phone calls. The capability is here. The briefing never happened.
And the practitioner pushback is not stupid. Go read the comments under that Reddit post. Two objections come up repeatedly, and both are fair. First: restaurants are going to start hanging up on AI callers once bot-placed reservations produce no-shows. Second: writing a prompt detailed enough to make an agent call useful takes longer than picking up the phone and making the call yourself.
The second objection is correct more often than AI people admit. If you are calling one restaurant one time, the prompt is a worse deal than the call. The economics only flip when the task is repetitive, when the hold time is long, or when you are placing the same call to forty people instead of one.
The first objection is the one that should worry you if you own the business being called. It is already happening, and the hang-ups are not coming from Luddites. They are coming from receptionists who got burned.
I will admit my own blind spot. For most of this year I treated voice AI as the least interesting corner of the field. Text agents could do real work; voice felt like a demo. I was watching the outbound story, the "AI replaces your call center" story, and dismissing it on quality. I was watching the wrong direction. The inbound story, the one where your own customers start sending software to talk to you, arrived first and arrived without warning. That is on me.
So reframe it. The question is not "do I trust AI on the phone." The question is: when an agent calls my business carrying a real customer's real intent and a real credit card, what does my team do in the next eight seconds?
What the evidence actually says
Five things are worth knowing before you set policy.
1. The hang-up reflex is real enough that Meta tried to engineer around it. Reuters reported on September 22, 2026 that Meta tested having human contractors handle some Muse phone calls after users reported businesses hanging up once they realized the caller was AI. Meta spokesperson Daniel Roberts said the company would roll the feature out "when it's ready and with the proper disclosures." Employees pushed back internally over exposing users' sensitive information, and the test ended. Sit with that: a company with Meta's resources could not solve the hang-up problem with technology, so it briefly tried solving it with people. Source: PYMNTS, reporting on Reuters.
2. The volume is still small, which means you have time, not permission to ignore it. Uber reported that AI agents accounted for 500 food orders and four ride bookings out of 320 million trips during a peak week, cited in Wall Street Journal reporting covered by PYMNTS on November 11, 2026. Four rides out of 320 million. Anyone selling you urgency on agentic commerce volume is selling you something. What that number buys is a quiet quarter to get your policy right.
3. Large merchants are already drawing hard lines, in different places. United Airlines now blocks personal AI agents from completing flight bookings, while still letting them search and display fares. CEO Scott Kirby put the reason plainly at an industry event in Chicago: "To be honest, I don't want to create another middleman." United says its back-end can tell whether a booking came from a consumer, a travel agency, or an AI agent. Delta, by contrast, permits authenticated AI assistants to book under safeguards. Same industry, same quarter, opposite calls. Source: PYMNTS, reporting on The Wall Street Journal, November 11, 2026.
4. On the restaurant side, the no-show math is the whole argument. Resy's own data shows no-show rates for accounts it flags as bots and brokers running at four times its general user base. Resy says it does not permit unapproved third-party bots or agents to independently access its platform, and it has deactivated accounts, including some belonging to well-known tech founders. That is company-reported data, not independent research, so weigh it accordingly. It explains the hostility precisely: the restaurant is not afraid of the robot, it is afraid of the empty four-top at 7:30.
5. The legal picture for outbound is settled enough to plan around, and stricter than most vendors tell you. On February 8, 2024, the FCC adopted a declaratory ruling in CG Docket No. 23-362 holding that calls using AI-generated voices are "artificial" under the Telephone Consumer Protection Act. That is not a ban. It means your AI voice calls carry the same consent obligations as any prerecorded call, including prior express written consent for telemarketing, with statutory damages of $500 per violating call and up to $1,500 if the violation is willful or knowing. The separate FCC proposal requiring an AI disclosure at the start of each call was floated in 2024 and never adopted. Disclose anyway. Meta's own language about "proper disclosures" tells you where this lands.
One more number on the customer side. Gartner surveyed 5,728 customers and reported in July 2024 that 64% would prefer companies did not use AI for customer service, and 53% would consider switching to a competitor over it. The top concern, at 60%, was that reaching a person would get harder. That is not an argument against AI on your phones. It is a specification for how to build it.
The two-lane approach
Stop thinking of this as one decision. It is two, and they have almost nothing to do with each other.
Lane one is inbound: what happens when an agent calls you. This lane costs nothing and protects revenue that already exists. The agent on your line is not a spammer. It is a customer who delegated the call. Hanging up on it is hanging up on them, except they will never know why, and they will book with the shop down the road that answered.
The operating principle: treat an agent caller as a qualified lead with a verification requirement. You are not required to transact with software. You are required to capture the human behind it. Get a callback number tied to a person, confirm by text or email to that person, and for anything with a cancellation cost, attach a deposit. Resy's four-times no-show number is an argument for a deposit policy, not a hang-up policy.
Lane two is outbound: whether your business places AI calls. This lane costs money and carries legal exposure, so it gets a higher bar. The honest test is whether the call is repetitive enough that a prompt beats a dial. Reactivating 300 lapsed customers, confirming next week's appointments, following up on 80 unreturned quotes: those pass. Calling one prospect you actually want to close: that fails. Pick up the phone.
The tooling has gotten respectable fast. On Product Hunt this week, Insight7 Voice AI Agents launched a campaign builder: describe the outbound campaign in one sentence, it drafts the opening line, the questions and the rules in plain English, then makes you take the test call yourself before a real customer is dialed. Each call returns one report of outcomes, patterns, and which customers need a human. Neura HQ launched the same day for Shopify, WooCommerce, Magento and BigCommerce brands, handling stock checks, tracking and returns on the website or WhatsApp.
Steal that "take the test call yourself" step regardless of vendor. If you will not sit through your own AI call, do not inflict it on a customer. That is not a compliance rule, it is a decency rule, and it is the fastest quality check in the category.
The mid-call human handoff is the other non-negotiable. Gartner's 60% told you exactly what they fear. Build the exit they are asking for and most of the objection evaporates.
Six steps to take before the end of the month
1. Call your own main line from your cell phone and time it. Do it at your busiest hour. Count the rings, the menu layers, the seconds to a human. That number is your real exposure, because an AI caller with infinite patience will sit through it and your human customers will not.
2. Write the inbound rule and put it where the phone is. One page: what your team says when a caller discloses it is an AI, what you will tell a non-human caller, what you will not, the three things you capture before holding a slot, and when to transfer to a manager. Tape it next to the handset. A policy living in a shared drive is not a policy.
3. Use this prompt to draft that rule sheet.
[The Job]
Draft a one-page phone policy for handling calls from AI agents that are calling on behalf of a customer.
This is for: [JOB TITLE, for example front desk staff and anyone who answers the main line] at [BUSINESS NAME], a [INDUSTRY] business in [CITY, STATE].
It matters because: [WHAT YOU LOSE IF THIS GOES WRONG, for example we miss real bookings from customers who sent an agent instead of calling themselves].[The Background]
Here is what you need to know: we answer about [NUMBER] calls per week on [NUMBER] lines. Our bookable services are [LIST OF SERVICES]. Information we will give out over the phone: [LIST]. Information we will not give to a caller we cannot verify as a person: [LIST]. Our no-show rate is [NUMBER] percent and our deposit policy is [POLICY, or "none today"]. Call recording consent in [STATE] is [ONE PARTY or TWO PARTY].
Do not use: legal advice, scare language about AI, or any step needing software we do not own.[The Deliverable]
Return: a one-page rule sheet, under 400 words, in numbered steps a new hire can follow on day two.
Must include: the exact words to say when a caller discloses it is an AI, the three questions we ask before holding a slot for an agent-placed booking, what we do when the agent will not provide a callback number tied to a person, and the trigger for transferring to a human manager.
Optimize for: accuracy.
Written from the perspective of a [FRONT-OF-HOUSE OPERATIONS MANAGER] speaking to [A NEW HIRE WITH NO INDUSTRY EXPERIENCE].[The Questions]
Ask me any questions you have.
4. Attach a deposit to anything with a cancellation cost. This is the biggest win on the list and it has nothing to do with AI. A deposit makes the source of the booking irrelevant. You stop policing who called and start pricing the risk.
5. Pick one outbound call type and only one. Appointment confirmations, lapsed-customer reactivation, or unreturned quote follow-up. Run it manually for two weeks and write down the five questions that came up most. Those are your script, and skipping this is why most voice pilots ship a bot that cannot answer what people ask.
6. Clear the consent question before you dial. Under the FCC's 2024 ruling, your AI voice calls sit under the TCPA's artificial-voice rules: written consent for telemarketing, $500 to $1,500 per violating call. Confirm what each contact consented to and when, separate service calls from sales calls, and run the list past your own attorney rather than a vendor's compliance page.
Frequently Asked Questions
Is it legal for an AI agent to call my business on a customer's behalf?
Generally yes. The TCPA's artificial-voice restrictions exist to protect called parties from unwanted marketing, and a customer-initiated call to your published business line is a different animal from a telemarketing robocall. You can still decline to transact with an unverified caller. Confirm specifics with your attorney.
Can my business use an AI voice agent to call my own customers?
Yes, with consent. The FCC's February 2024 declaratory ruling treats AI-generated voices as "artificial" under the TCPA, so your calls carry prerecorded-call obligations, including prior express written consent for telemarketing. Damages run $500 per violating call, up to $1,500 if willful. Service and sales calls follow different rules.
How do I know whether the caller is an AI?
Most legitimate agents disclose it, and some add a recording notice. The practical tells are unusual patience through your phone tree, a slight response delay, and answers that stay oddly on-script. Rather than guessing, ask for a callback number and a name, then confirm by text to that person.
Should I just block AI callers the way United and Resy did?
Only if you have their problem. United is defending customer relationships worth billions; Resy is defending against reservation scalping. A six-chair salon has neither. Blocking costs you bookings from customers who delegated a call. Verification and deposits handle the same risk without turning away revenue.
What does an AI phone call cost to place?
The open-source Smitline demo on Reddit this week reported 89 seconds and 11 cents for one completed restaurant call, which is the developer's own figure, not an audited benchmark. Commercial platforms price higher. The real comparison is not cents per call, it is cents per call against the loaded cost of the staff minute you are replacing.
The call you are not going to make
Go back to that eighty-nine second phone call.
An agent dialed a restaurant, announced itself as AI, navigated a menu tree, placed an order, and hung up, for eleven cents. Nobody at that restaurant had been told this was coming. Whoever answered made a judgment call in real time on behalf of the whole business, and whatever they decided is now the policy.
That is the situation on your line. The difference between the businesses that come out of this quarter ahead and the ones that come out confused is not budget and it is not technology. It is whether somebody wrote the rule down.
You have a quiet window. Uber counted four agent-booked rides out of 320 million. That is your runway, and it will not be this quiet in six months. Use it: time your own hold music, write one page, tape it to the wall, attach a deposit to the bookings that can hurt you.
Do not spend the window arguing about whether AI on the phone is good. Nobody is asking your permission. The agents are already dialing, and your people are already deciding, one call at a time, with no guidance from you.
Give them the page. That is the whole job this month.
If you want the rest of the operating system behind this, the frameworks, the prompts, and the training replays that walk entrepreneurs through building it, that is what the White Beard Strategies membership is for.
About the author. Jonathan Mast is the founder of White Beard Strategies, where he teaches entrepreneurs to use AI practically instead of theoretically. He created the Perfect Prompt Framework, speaks regularly on applied AI for small business, and runs a free community of more than 500,000 entrepreneurs. He spent thirty years in sales before founding WBS, which is why he still believes the most underrated piece of technology in your business is the phone somebody answers on the second ring.
