Scenario: leaky tap
A leaky tap stays structured intake — not an invented emergency visit or a dispatched van.
Pre-launch. Not a public live service yet.
From maintenance request to controlled follow-up.
See how MaintenanceOS is designed to capture a request, structure the work, escalate critical cases, and keep human oversight. The website path is Website → Check → Choose → Configure → Review & Try, followed by an optional saved reference. Website learning only uses extracted public facts; it does not invent bookings or a live phone number.
Website → Check → Choose → Configure → Review & Try
The same steps as the website setup preview. Typical shape: website URL → validate → choose role → configure → review → interactive receptionist demo → optional save. We do not invent crawl results or a live phone number.
- 1
Website
PREVIEWStart with a public business URL
Paste a public site URL and email to prepare the receptionist preview. Checking the website does not assign a live phone number.
Status: The public /create funnel exists today and ends in a browser voice receptionist preview.
- 2
Check
PREVIEWValidate the URL and prepare a reviewable draft
We read a small, bounded set of public HTTPS pages and extract reviewable business facts. Missing hours, services, or FAQs stay empty when they are not found.
Status: Website learning is read-only and bounded, and it follows robots.txt. Extracted facts are reviewable before the receptionist uses them.
- 3
Choose
PREVIEWChoose the job you want the AI to do
Pick one bounded starting role: receptionist, maintenance desk, booking assistant, customer service, sales/enquiry, or custom. The choice creates a draft AgentBlueprint; it does not activate a live agent.
Status: Role selection is configuration only. Provider, phone number, credentials, and live routing stay untouched.
- 4
Configure
PREVIEWConfigure the agent within the selected role
Choose a voice preference, narrow the approved role actions, set human-transfer behaviour where the role permits it, and review the business facts and greeting.
Status: Configuration can only narrow the selected role. It cannot add unsupported permissions or alter live phone routing.
- 5
Review & Try
PREVIEWReview the final configuration and pack
The reviewed configuration becomes a knowledge pack and protected system prompt. Missing hours or services stay missing, and the reviewed configuration becomes the input to the browser voice preview.
Status: The browser voice receptionist is available after review. Speak through the browser microphone and hear the response aloud when browser voice is supported; it is not a live public telephone call.
UK maintenance playbooks
Labelled scenarios from product design — not customer stories, and not a sample of a real call. How intake is designed to treat common UK jobs.
Scenario: no heat
Collect who, what, where, and access. Rules must not invent a booking, a slot, or “someone is on the way.”
Scenario: access
Who can let someone in, and when. Intake is designed to capture access — not to invent a contractor visit.
Scenario: contractor chase
Follow-up stays a structured job note. The model must not invent a dispatch, an ETA, or a promise that a van is coming.
Scenario: 999 latch
UK 999 guidance (never 911). Emergency services stay emergency services; critical safety is designed to latch for a person.
Product tour
A short walkthrough of website learning → review → pack, then how intake and rules are designed to work. Click to play — nothing autoplays. Captions are English (UK). The browser voice call is tested separately in Create and is not a live public phone number.
Fixed rules and an authorised person keep control of safety and money. Read the safety controls
Designed so marketing never outruns the product.
The browser voice receptionist is available after the reviewed configuration is generated. It uses the browser microphone and spoken replies when supported. Live always-on phone remains separate — frozen production telephony is not used here. Further controlled live testing is still required before we claim a public always-on receptionist.
Straight answers before you start
Pre-launch honesty — not a live phone, not peer feature parity.
Is there a live always-on phone line I can call now?
No. Voice intake exists in product source and remains in commissioning preview. Public always-on commercial phone is not on this site until controlled-call gates pass. Path today: request an early demo — not “call the AI now.”
Can it book or reschedule calendar appointments?
Not as a present claim. Live calendar book/reschedule is not on this site; it’s tracked with product. We don’t market peer-style appointment booking until the register upgrades.
Will MaintenanceOS invent bookings, dispatches, or refunds?
No. The product must not invent bookings, dispatches, refunds, compensation, account information, or safety assurances. Fixed rules own safety and money — the model does not execute client-money or invent a van.
What about emergencies vs routine jobs (UK)?
UK 999 guidance (never 911) is VERIFIED. Emergency services stay emergency services; a leaky tap stays structured intake. Critical safety is designed to latch for a person.
Why only seven features on /features?
Those are the cards we can stand behind today: 4 VERIFIED and 3 PREVIEW. Items other products advertise stay off the marketing page.