The agent that books the job on your site and answers for it until it is done
No heating on a Sunday night, a plan that may or may not cover it, and a contractor who does not work for you. Those are lookups and bookings, and Algomo runs them against the systems your own repair and policy pages already use, in the homeowner's own session while she is on the page. She types, the plan is read, the windows come out of the live diary, and the confirmation, the engineer's name and the time land in the chat and on the booking page the agent opens beside her. When she comes back for the reschedule, the part or the claim, the same thread is waiting.
Booked on the page she was already reading, before the visit and without a form
A form on a repair page makes a homeowner retype a postcode your policy record already holds and then tells her nothing until somebody reads it on Monday. Algomo runs the chat and the booking page as one session: while she is still typing, the window, the address it already holds on the policy and the engineer's name appear in the chat and on the booking page it opens beside her, and a click confirms all three. The slots come out of the same booking endpoint your own repair page uses, so a window it offers is a window a contractor has actually got, and the booking is in the diary before she closes the tab.
- The chat and the booking page are one session
- Address and access confirmed with a click, never retyped
- Windows read from the live diary, not from a copy
- Sunday night, storm week and Boxing Day, at full strength
Coverage answered at intake, in the words of the contract
The expensive conversation in warranty is the second one: the one that comes after an engineer has been, when the homeowner finds out the part was excluded. Algomo reads the plan her account page shows, quotes the excess and the exclusions back in the contract's own language, and says what is not covered before anybody is booked. What it will not do is decide a borderline case. Whether a fifteen year old boiler counts as a pre-existing fault is a contractual judgement with money behind it, so the agent stops, says so, and hands the whole conversation to a claims handler with the plan, the history and the thread attached.
- Plan, excess and exclusions read at intake, not after the visit
- The clause quoted back in the contract's own words
- A borderline exclusion handed to a claims handler, never guessed
- The handover carries the plan, the history and the whole thread
Reads the job, the plan and the parts lookup so nobody has to ask around
A warranty job runs through people who mostly do not work for you: a subcontracted engineer, a merchant's trade counter, a manufacturer's warranty desk, an adjuster with a queue of his own. Each keeps its own record and none of them tells the homeowner anything. Algomo reads what each of those systems shows, in the session of whoever is asking: the engineer signed into the trade portal sees the parts stock and the claim limit, the homeowner on her job page sees the new time, and the pieces that need a person, the approval above the limit or the adjuster's decision, go to your team with the case assembled.
- Homeowner, contractor and adjuster each reading the same job
- Parts stock and the claim limit read from the lookups your portal uses
- The homeowner sees the change the moment she asks
- What needs a person goes to your team with the case, not a note
The renewal and the overdue service, sorted when the homeowner logs in
Every closed job leaves something behind: a plan that lapses in six weeks, an estimate the homeowner never came back on, a boiler two years past its service. None of it is urgent, which is why it never gets done and why the same household comes back as an emergency in November instead. Algomo does not message anyone who has left the site. What it does is notice all of it the moment the homeowner logs in to check something else, at twenty to eleven on a Tuesday with nobody on the desk, and book what the account page lets her book, then and there. It is the same agent on the same policy data, so the offer it makes is one the household is actually eligible for.
- Renewals quoted off the plan the household actually holds
- Service history read from the account page, overdue visits offered a slot
- Renewal and service booked in the same conversation
- At 22:40 on a Tuesday, with nobody on the desk
What it closes, and what it hands to a person
Home services is not a regulated conversation, but a warranty is a contract, and a contract has a line in it. What is covered, what is excluded and what counts as pre-existing are decisions with money behind them. The agent runs everything up to that line, all of it, and stops there holding the whole case rather than a ticket about it.
Is this covered
The plan on the record read at intake, with the excess and the exclusions written out in the chat before an engineer is booked, which is the thing that stops the second visit.
When can somebody come
Windows read from the diary your booking page uses and confirmed on that page in the same session, so the slot the homeowner is given is a slot that is in the diary.
Where is my engineer
The question that fills a desk on a bad morning, answered off the same job status your own portal reads, at half past six if that is when it gets asked.
The part has not come
The part's stock and the claim's parts limit read from the lookups your portal uses, and the homeowner told what her job record shows. Chasing a merchant is a person's job, and it goes to your team with the thread.
Renew my cover
Renewals, overdue services and open estimates picked up the moment a homeowner comes back to the account page, priced off the plan the household actually holds rather than a generic one.
Is that a pre-existing fault
It does not decide that. A borderline exclusion, a goodwill decision or a replacement above the limit goes to a claims handler with the plan, the whole history and the thread.
What a home services operation gets out of it
The same agent takes the questions that decide whether a job is booked at all and the exceptions that decide whether the household renews.
Bookings that survive the visit
Nobody abandons the booking halfway through retyping an address, and nobody waits until Monday to learn whether the slot was real. The booking is finished on the page the homeowner was already reading, and the window on it is the window the engineer arrives in.
The second visit that never happens
Coverage and excess explained before the visit rather than discovered after it. A bill nobody expected is the conversation that costs you the renewal, not the repair.
Storm weeks without a hiring plan
A cold snap that triples the people on your repair page is answered at the speed of an ordinary Tuesday, because the thing that answers has no rota and no queue.
Renewals that get asked for
Lapsed maintenance, overdue services and open estimates offered every time a homeowner logs in, instead of whenever somebody on the desk has a quiet afternoon to do it.
Three differences, one loop
It connects itself
Algomo discovers the endpoints your own booking and policy pages use. That is why a window it offers is a window in the diary and the cover it quotes is the cover on the record, rather than a line from a spreadsheet exported on Monday.
So its actions are real
Because it holds those endpoints, confirming a window means the window is booked, through the same endpoint your booking page uses and into the diary your coordinators see, in the second the homeowner clicks it.
And you run it by talking to it
A new contractor on the network, a postcode that needs a two hour window, a plan that must never be quoted without its excess: say it in plain language and the next conversation follows it.
Never put a vulnerable customer into a four hour window.
Done. They will be offered two hour windows only, and told why the choice is shorter.
Discovery gives it live data. Live data makes real actions safe. Plain-language control keeps the coverage decisions yours.
Questions, answered
What it does
**What is a home services AI agent?**
Web chat on your own repair and policy pages that checks what the plan covers, books the visit against the diary your booking page uses, and answers for the job whenever the homeowner comes back: the part, the reschedule, the claim. Algomo does that against your live systems, in the homeowner's own session, rather than describing what they contain.
**How is this different from the form on our repair page?**
A form asks the homeowner to retype what your policy record already holds and tells her nothing until somebody reads it on Monday. Algomo reads the plan, quotes the excess, offers only the windows the diary actually has, and confirms the booking on the page beside the chat, in the same session. Nothing is retyped and nothing waits for a person.
**Will it chase renewals and old estimates?**
It does not message anyone who has left your site. What it does is read the plan, the renewal price, the service history and any open estimate the moment a homeowner logs in, and offer them in the chat. That is how a renewal gets asked for at twenty to eleven on a Tuesday rather than when the desk has a quiet afternoon.
**Can it handle a storm week?**
A cold snap or a named storm triples the people on your repair page overnight, and the agent answers the four hundredth conversation the way it answered the first. There is no rota to fill and no queue to build, and the bookings that come out of it are confirmed against real diaries rather than promised and sorted out later.
Contracts and claims
**Can it tell a homeowner what their plan covers?**
Yes, and at intake rather than after the visit. It reads the plan the account page shows, quotes the excess and the named exclusions, and says plainly where the job falls outside cover before an engineer is booked. The conversation that costs you a renewal is the one about a bill nobody expected.
**Does it decide claims?**
No, and it says so in the chat. Whether a fault is pre-existing, whether an exclusion applies at the edge of the wording, whether goodwill is warranted: those are contractual judgements with money behind them, so they go to a claims handler with the plan, the visit history, the engineer's report and the whole conversation attached. The agent hands over the case, not a ticket asking somebody to go and find it.
**Can it spend money or commit us to anything?**
Only what you allow, and each of those is a separate permission. An operator that wants the agent to book but never cancel, to quote a part against the claim limit but never order one, or to show the renewal price but never take payment, can have exactly that.
Your engineers and your systems
**Our engineers are subcontractors. Does that work?**
That is the normal case here. The agent offers only the windows the diary behind your booking page shows as free, so a slot it confirms is a slot a contractor has. An engineer signed into your trade portal can ask it the same questions a homeowner does, and get the parts lookup and the claim limit in the same session. Chasing a contractor who has gone quiet is a person's job, and it goes to your team with the job and the thread rather than sitting in somebody's inbox.
**What happens when a part is on back-order?**
It reads what the parts lookup and the job record show and tells whoever is asking exactly that: which merchant has one, the date on the order, whether the claim limit covers it. Chasing the merchant or the manufacturer's warranty desk is done by a person, and it goes to your team with the case assembled rather than a note to go and find it.
**Does it work with ServiceTitan, Housecall Pro or our own system?**
It works against whatever your website and customer portal already talk to. If a page a homeowner or a contractor can open shows a policy, a job status, a parts lookup or a booking window, the agent reads it in their session and acts where the page lets them act. Anything a signed-in customer can already see on your site, the agent reads in their own session. Anything only your staff can reach, we connect with you.
**What record do we get of a conversation?**
The whole conversation is kept and goes with the handover. When a claims handler or a coordinator picks up a case, they get the thread word for word alongside the plan and the job it was about, and your team is told by email or Slack the moment it lands.
Setting it up
**What languages does it work in?**
Whatever language the homeowner or the contractor types in, and it stays in it for the whole conversation. On a network with subcontracted crews that is routinely three languages against one case, which is exactly where a desk falls over.
**How long does setup take?**
Minutes for the public side, because Algomo finds the endpoints your own booking and policy pages call and builds its own tools to use them. You can try it against your live booking flow before a homeowner ever does. Anything a signed-in customer can already see on your site, the agent reads in their own session. Anything only your staff can reach, we connect with you. You build and change it from Claude Code, Codex or any other tool that speaks MCP, the open protocol AI tools use to talk to each other, or from the dashboard.
**What does it cost?**
You pick a monthly amount and it buys credits: a conversation that actually helped someone costs five, one that went nowhere costs nothing, and the amount is the most any one charge can be, so a storm that triples the people on your repair page never raises the bill on its own. There is no overage: run out early and you renew early, or wait for the month to turn. Every number is on [this site's pricing page](/pricing).
Explore more from Algomo
Why Algomo
Why we built an agent that does its own integration work.
[Why Algomo](/resources/why-algomo)
Comparisons
See how Algomo compares to Sierra, Intercom Fin, Decagon and Gorgias.
[Comparisons](/resources/comparisons)
Product
How it connects itself, works your pages with the visitor, and takes instructions in plain language.
[Product overview](/product)