Meta just opened an enterprise AI platform. For a service sub, the piece to watch is the agent that answers customer messages
Meta launched an enterprise platform on September 28 that bundles a customer-facing Business Agent, an API, and a coding agent. A mechanical or electrical service sub that takes calls through WhatsApp or Messenger should set the agent's limits before turning it on.
Meta launched an enterprise AI platform on September 28 that includes a Business Agent built to answer customer messages, qualify leads, and book appointments. For a mechanical, electrical, or plumbing service sub that already takes calls over WhatsApp or Messenger, that agent is the piece worth a look, and the piece that needs limits before it talks to a customer.
What did Meta actually announce?
Meta said it is starting an enterprise platform that puts its Muse models, agents, and developer tools under one business-facing effort. Zuckerberg called it a "next major pillar" of the company, and Chirantan "CJ" Desai, formerly CEO of MongoDB, will run it and report to him. The reported initial pieces:
- Muse: Meta's personal AI assistant.
- Meta Business Agent: answers customer questions, recommends products, books appointments, and qualifies leads on Meta's messaging platforms.
- Muse API: lets developers build Meta's models into their own software.
- Muse Code: a terminal and continuous-integration coding agent that plans tasks, edits files, and runs commands.
Coverage doesn't include enterprise pricing, customer commitments, or a delivery timeline for the platform as a whole. Treat it as a direction, not a product you can buy this week.
Which contractors does this touch?
Not most of them. A sub that gets work from bid invitations, GC portals, and phone calls with a few repeat GCs won't see much here. It matters for service and small-project work: a mechanical service company fielding "my rooftop unit is down" texts, an electrical contractor taking tenant-improvement requests, a restoration outfit answering after-hours messages.
| Task | Fit for a messaging agent | Keep a person on it |
|---|---|---|
| Collect address, equipment type, symptom, photos | Good | Review the summary |
| Book a non-emergency visit into open slots | Reasonable | Dispatch confirms |
| Quote a price or say "that's covered" | Poor | Always |
| Promise an arrival time on an emergency call | Poor | Always |
| Qualify a new-build inquiry by size and trade | Reasonable | Estimator follows up |
What could go wrong?
A customer-facing agent talks in your company's name. If it tells a facility manager "we'll have someone there within two hours" or "that's under warranty," you own that statement. Warranty language and response times are the two answers that most often turn into disputes. Set the agent up for intake only, and put anything involving price, time, or coverage behind a human.
Muse Code and the API are a separate question. The same tools that let a developer automate work could let a 30-person sub build small internal tools, such as a script that turns a service ticket into a work order. Nothing in the launch coverage shows anyone doing that on a jobsite, so don't plan around it yet.
What should a service sub do this week?
- Count how many inbound customer requests arrive on WhatsApp or Messenger, and how long each waits for a reply.
- Write down the five answers your dispatcher gives that a machine must never give (price, ETA, warranty, liability, safety advice).
- If you pilot any messaging agent, run it in a draft mode where a person approves each outbound message for two weeks and log every edit.
This is also the third major vendor pushing agents into ordinary business channels, following the untagged-agent problem we covered in this piece on chat agents and RFI authority. The rule is the same: decide what the agent may say before it says it.
- What did Meta launch for businesses on September 28, 2026?
- Meta announced an enterprise platform that groups its Muse models, agents, and developer tools for business customers. The initial lineup reported by several outlets is Muse, Meta Business Agent, the Muse API, and Muse Code. Former MongoDB CEO Chirantan Desai leads it and reports to Mark Zuckerberg.
- What is Meta Business Agent and could a contractor use it?
- It is an agent that answers customer questions, recommends products, books appointments, and qualifies leads across Meta's messaging apps. A service-oriented sub that gets requests through WhatsApp or Messenger is the natural fit. A sub that only works from bid invitations and GC portals has little use for it.
- Does Meta's platform have construction-specific features?
- Nothing in the launch coverage is construction-specific. Any fit comes from general capabilities such as customer messaging, an API, and a coding agent. Meta also hasn't published enterprise pricing or a delivery timeline for the unified platform.
- What should a subcontractor restrict an AI customer-messaging agent from doing?
- Block it from quoting prices, promising arrival times, or describing warranty coverage unless a person has approved that exact answer. Limit it to intake: collecting the address, the equipment, the symptom, and photos, then booking or handing off to dispatch.