The field service agent that answers the stalled job
A part that never came, a customer who has taken the day off for a four-hour window, an engineer standing in a kitchen who does not know whether the depot has it. Those are lookups against the systems your own booking and stock pages already call, and Algomo runs them in web chat on your website and your customer portal, in the visitor's own signed-in session. A dispatcher answers one person at a time. The agent answers the engineer, the customer and the client at once, and hands your dispatcher whatever needs a person, with the whole thread.
Read every system at once, from the minute the job stops
A stalled job is four lookups that a dispatcher can only do in order: van stock, depot stock, the supplier catalogue, and the diary the engineer and the customer both depend on. Algomo reads all four at once, in the dispatcher's own portal session, off the endpoints your own booking and stock pages call, so a part it says is there is a part that is there. What it can settle from those lookups it settles in the chat. What needs a decision it lays out with the lookup behind each line, and the dispatcher decides from one screen.
- Van stock, depot stock, suppliers and the diary read in parallel
- Off the same lookups your booking and stock pages already call
- Answers when the dispatcher signs in, not when the office opens
- What needs a person is handed over with the case assembled
It answers the customer at night and the engineer before the office opens
Most of what stalls a job is a question nobody could answer at the time it was asked: the customer at 22:40 wanting to know whether tomorrow's window still stands, the engineer at 07:10 wanting to know whether the part is on the van or at the depot. Algomo answers both, in web chat on your website and your portal, in the person's own signed-in session, off the same diary and the same stock lookup your pages use. The customer sees where the appointment stands and moves it if your portal lets them. The engineer sees which depot has the part and reserves it there. Nothing waits for the office to open.
- Answers at 22:40 and at 07:10, before anyone is at a desk
- Van stock or depot stock, off the parts lookup, with the part number
- Where the window stands, from the same diary as the booking page
- A returning customer picks up the thread where they left it
Every window defended, from the record your portal already shows
A missed appointment window turns into an argument about what was said and when, six weeks after anybody can remember. The record exists: the engineer's arrival time, the no-access note, the photograph, all on the job your portal shows. Algomo reads it when the client asks, in their own signed-in session, and lays it out minute by minute. Then it offers what is genuinely free in the diary rather than an apology. So when a client opens an SLA claim, the answer is on the screen in front of them, and it does not have to be reconstructed out of three inboxes and a dispatcher's memory.
- Arrival, access and photographs read off the job as your portal shows it
- Rebooked against the live diary, not a guess
- Where is my engineer, answered from the live job at 06:30 if that is when it is asked
- SLA claims answered from the record, not from memory
It runs inside your rules, and it knows where they end
Your ops team decides what the agent may say, what it may read, and what it may commit to on your behalf: a slot, a reserved part, a part in the basket for a dispatcher to confirm. What it may not decide is whether an unhappy customer gets money back. Goodwill, a warranty judgement that could go either way, a contract a branch manager would rather not lose. Those stop, and the whole case goes to a person with the whole conversation attached, in order, rather than a ticket asking them to go and find it.
- Permissions set by your ops team, not by us
- Commitments limited to what you have approved
- Goodwill and warranty judgements handed to a person
- Handover carries the whole thread, not a summary of it
What it closes, and what it hands to a person
Field service is not a regulated conversation, so the line here is not a legal one. It is commercial, and it is drawn where a decision costs money or costs a customer. The agent answers the coordination, all of it, and stops at that line with the whole case in its hands.
Where is my engineer
The question that fills a dispatch desk on a bad morning, answered on your site off the same job tracking your own portal reads, at half past six if that is when it gets asked.
Have we got the part
Van stock, depot stock and supplier availability read off the live lookup, then reserved in the engineer's name where your portal has a reserve button, rather than promised and hoped for.
Is it under warranty
Install date and serial read off the job record, so an engineer standing in the kitchen knows whether the part is covered before the customer asks. The claim form stays with your office, handed over with the codes.
Move my appointment
Windows read, swapped and confirmed against the real diary, in the customer's own session, so the slot they pick is a slot an engineer can actually reach.
What happened on the 14th
Arrival times, access failures and photographs, as your portal recorded them, laid out in the chat so the SLA record is finished before the dispute has started.
I want my money back
It does not decide that. Goodwill, a borderline warranty judgement or a customer worth more than the bill goes to whoever owns the account, with the whole thread.
What a service business gets out of it
The same agent takes the questions that decide whether an engineer rolls twice and the exceptions that decide whether a contract renews.
Fewer second visits
A return visit booked only once the part shows in stock, the access is written on the booking and the customer has picked the slot themselves. The truck roll nobody should have paid for is the expensive one.
Windows that hold
A customer who asks at 22:40 gets the diary as it stands, and moves the slot themselves if the morning no longer works, which is the difference between a rebooked window and a lost day.
SLA claims answered
Arrival times and access failures, as your own system recorded them, laid out in the chat, so a claim six weeks later is answered from the record rather than argued from memory.
Dispatchers on the jobs that need one
Where is the part, is the engineer still coming and can I move Thursday stop reaching a person at all, so the jobs that do reach one are the jobs worth a person.
Three differences, one loop
It connects itself
Algomo discovers the endpoints your own booking and stock pages call. That is why a part it reserves is a part your branch system shows, rather than a line from a stock report somebody exported on Monday.
So its actions are real
Because it holds those endpoints, booking a window means the window is held, in the diary, on the screen the dispatcher is looking at, in the session of the person who asked.
And you run it by talking to it
New supplier, a site that needs an escort, a client who must never be offered a four-hour window: say it in plain language and the next job follows it.
Never promise a same-day return visit without a reserved part.
Done. It will offer the next confirmed slot instead, and say why.
Discovery gives it live data. Live data makes real actions safe. Plain-language control keeps the commercial decisions yours.
Questions, answered
What it is
**What is a field service AI agent?**
An agent that answers the coordination half of field service in web chat on your website and customer portal: which depot has the part, whether tomorrow's window still stands, what happened on the 14th, whether the serial is in warranty, and moving the slot where your portal allows it. Algomo does that against your live systems, in the visitor's own signed-in session, rather than describing what they contain.
**How is this different from our FSM platform?**
An FSM platform records that a job is on hold. It is a very good record, and nobody can ask it a question at 22:40. Algomo is the thing your customers and engineers talk to on your site: it reads the job, the diary and the stock the FSM holds, answers from them, and hands what needs a person to your dispatcher with the whole thread. One holds the state, the other answers for it.
**Does it replace our dispatchers?**
No. It takes the questions off them: where is the part, is the engineer still coming, can I move Thursday. What reaches a dispatcher after that is the jobs that genuinely need deciding, each with the conversation attached, which is the part the job was supposed to be.
Working a job
**Does it really check everything at once?**
Yes, and that is the whole point. A dispatcher can only open one screen at a time, so a stalled job is four sequential lookups. The agent reads van stock, depot stock, the supplier catalogue and the diary in parallel, and comes back to whoever is asking with an answer rather than a promise to find out. What it cannot read, it says so, and hands over.
**Can it stop a second visit that should not have been needed?**
That is the case it is built for. It will not offer a return window until the part shows in stock, the access requirement is written on the booking, and the customer has picked the slot themselves. Where one of those is missing it says so, rather than booking the visit and hoping.
**When does a person get involved?**
When judgement or money is at stake: a goodwill credit, a warranty judgement that could go either way, a repeat failure on a contract worth keeping, or a customer who has simply had enough. The handover carries the whole case, in order, so nobody re-reads three weeks of thread to catch up.
**Is the conversation kept?**
The whole conversation is kept and goes with the handover, in order, so a dispatcher or a service manager reads what was said rather than a summary of it. The job record itself stays in your FSM, where your portal already shows it.
Parts and appointments
**Can it order parts and spend money?**
Only what your portal lets the signed-in person do, and only what you allow on top of that. A business that wants the agent to reserve stock but never raise a purchase order, or to put a part in the basket and leave the confirm to a dispatcher, can have exactly that.
**Can it book and move appointment windows?**
Yes, against your real diary rather than a copy of it, in the customer's own session, which is why the window it offers is one an engineer can reach. Reading slots and moving them are separate permissions, so a branch that wants the agent to look but never touch can have that too.
Your systems and setup
**Does it work with ServiceTitan, Salesforce Field Service or our own system?**
It works against whatever your website and customer portal already talk to. If a page a customer or an engineer can open shows a job status, a stock level or a booking slot, the agent can read it in their session. Systems reachable only from inside your network are connected with us.
**What languages does it work in?**
Whatever language the customer or the engineer opens in, and it stays in it for the whole thread. On a site with a subcontracted crew that is often three languages against one case, and every one of them reads the same diary.
**How long does setup take?**
Minutes for the public side, because Algomo finds the endpoints your own booking and tracking pages call and builds its own tools to use them. You can try it against your live booking flow before a customer 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 cold snap that triples your traffic 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)