Field notes for a web that acts.

Field note 01

The customer may now arrive through an agent.

A customer journey can begin with a person asking an AI agent to find a suitable business, check the details, and complete the next step. The website still matters, but it may no longer be used only by a human visitor.

On September 8, 2026, Meta introduced Muse, a personal AI agent that can use its own browser, fill out forms, book appointments, and ask for approval before actions such as purchases. Associated Press coverage described the launch as available in the United States through the Muse app and WhatsApp.

This does not mean every customer will delegate every task to an agent. It does mean that an agent completing a real customer journey is no longer only a product demonstration or future prediction.

What changes for a service business?

Consider a customer looking for an HVAC repair or a kitchen remodeling consultation. The customer may ask an agent to identify suitable providers, confirm coverage, compare stated services, and reach a quote or booking path.

For that journey to work, several ordinary website details have to form one coherent path:

• The service must be stated clearly rather than implied by imagery.
• The service area must be explicit and connected to the correct location.
• Hours, availability, and contact details must agree across relevant pages.
• Forms must label required choices and expose a usable next step.
• The agent must be able to stop before payment, agreement, or another irreversible action unless the user authorizes it.

A site can look polished and still fail one of these tasks. A form may work for a human who understands an image-only choice but remain ambiguous to an agent. A coverage area may be obvious to a local customer but never stated in a way that supports a reliable answer.

What Agent Readiness does not mean

It does not mean redesigning a website for one named AI product. ViaLayer does not claim an integration with Muse and does not test against Muse specifically. Muse is a public example of a wider shift toward agents that use websites on a person’s behalf.

It also does not replace SEO, accessibility, analytics, security review, or human usability testing. Those disciplines answer different questions. Agent Readiness asks whether a defined agent can complete a defined customer task under recorded conditions.

A useful first check

Start with one task tied to a real business outcome. Avoid trying to label the entire website “ready” or “not ready.” A useful first task might be:

• Confirm whether a named service is available in a specific postcode.
• Find current emergency-service hours.
• Reach the review step of a quote request without unsupported guesses.
• Open the correct consultation or appointment path.

Define what success means, run the task more than once, record what happened, and preserve mixed results as mixed. If a correction is made, repeat the original task rather than treating the code change itself as proof.

The immediate question

The practical question is not whether every customer will use an agent tomorrow. It is whether an agent acting for a customer can understand enough of your business to take the next useful step today.