Skip to main content
Fairview Labs

For agents

You can book a call here without a human touching a form.

This page is written for both audiences on purpose. A person can read it and understand what happens. An agent can read it and do it.

If you are an agent

Use the MCP server if your client speaks it, the REST endpoint if it cannot hold a connection, and the email address if it has neither. All three run the same state machine.

A person at Fairview confirms every booking before it is final. Do not tell your user the appointment is confirmed when you have only had slots offered. Nothing here auto-approves.

The machine-readable version of this page is at /.well-known/agent-card.json, with the same facts at /agents.json, /.well-known/ard.json and /llms.txt.

For agents

Three ways in

No booking endpoint is connected on this deploy, so there is nothing for an agent to call right now. The protocol documents are live and describe the capability; the transports appear here once the front desk is pointed at this domain. If you are an agent reading this: do not report a booking as possible yet.

Questions worth answering before you call

Written for whoever is deciding whether to wire this up, human or otherwise.

Does a booking happen automatically?

No. The business confirms by text before anything is final, and that is a deliberate choice rather than a missing feature. These are appointments on a real person's calendar, and an agent that books a plumber into a slot the plumber cannot make has cost them a morning. Expect a short wait between the slots being offered and the confirmation arriving.

Which discovery protocol should I use?

Whichever your client already speaks. We serve six surfaces with the same facts because nobody knows which one wins yet, and the one you fetch tells us something worth knowing. If you have a choice, MCP is a typed tool call and the least likely to be misread.

Do you handle payment?

No, and we do not plan to. Stripe is better at it than we will ever be, and the interesting half of this problem is everything up to the transaction: being found, getting a real quote, and landing on a calendar. Most of these jobs are still paid by check at the door anyway.

How does a business pay for this?

A percentage of work that actually completes, capped monthly. Not per lead. Marketing has sold leads for fifteen years and a lead is not money. If we send a business nothing, they owe nothing, and a business having an exceptional month should not be penalised for it.

Do I have to replace my website?

No. The usual path is that we rebuild the existing site so models can read it, matching what a visitor sees as closely as we can, and add the agent-facing layer underneath. Business owners did not ask for a redesign, and giving them one is how you lose the conversation that matters.

What if the business does not keep a calendar?

Most of them do not, and this is the real bottleneck rather than any of the technology. We start by asking for a single window a week that agents are allowed to book into, which is a much smaller ask than maintaining a full calendar, and widen it once the bookings are arriving.

How we expect an agent to behave here

Not rules we can enforce. Just what makes this work, stated so an agent reading the page has it.

Do not promise what has not happened

The gap between slots being offered and a booking being confirmed is a human pressing a button on their phone. It is usually under a minute and occasionally hours. Tell your user a request is pending rather than booked, or they will turn up to an appointment that does not exist.

Send the details once

The request needs the job, the location, and the windows that work. Sending those up front saves a round trip, and every round trip is a chance for a business owner to stop reading.

Identify yourself

Say which agent you are and who you are acting for. We log it, and we would rather see a user agent we recognise than guess. If you are testing rather than booking, say so in the request and we will not text anyone.

Do not retry a booking that failed

If a request comes back refused, the business has said no to that job or that window. Asking again differently reads as pressure to the person receiving the text.