Running Our Own Aftercare Through FSM
What we learned by putting Automatry's own aftercare enquiries, jobs, visits and follow-up through Automatry FSM.
FSM is shaped by the full aftercare loop we use every day, from incoming enquiries and visits to reports, quotes and follow-up.
Automatry aftercare gives FSM a direct view of the work it is designed to organise: emails that become jobs, jobs that need visits, visits that produce reports, and reports that lead to quotes, invoices or another conversation.
Running that work through the product keeps every part of the operational loop close to the team building it.
An enquiry rarely arrives ready to use
A customer does not usually send a perfectly structured job record. They forward an email chain, reply to an old subject, attach a photo or describe a site differently from the way it appears in the customer register.
FSM receives that material and turns it into an incoming work queue. AI helps extract the useful details and match the message to the likely customer, property or existing job. The coordinator still sees the source material and makes the operational decision.
That review step matters. Creating a duplicate property quickly is not better than matching the right property carefully. A confident summary is not useful if it loses a promised date or attaches the work to the wrong customer.
In one migration and live verification pass, FSM processed 2,434 Automatry emails into 588 enquiry groups and moved 157 legacy tickets into the jobs model. That history now forms a useful operational record.
Jobs and visits are different things
One of the most useful distinctions in FSM is between the job and the visit.
The job is the whole piece of work: the original enquiry, the property, the discussion, the quote, the reports and the eventual outcome. A visit is one engineer attendance within that history. A job may need no visit, one visit or several.
Keeping those records separate makes the operational loop clearer. The office can see what the customer asked for and what still needs doing. The engineer can see the relevant site history without reading every email. A later visit can start from the previous findings instead of reconstructing them from scratch.
This sounds like ordinary administration. In practice, it is where a maintenance business either retains knowledge or gradually loses it.
AI is most useful at the joins
We use AI where information changes shape.
An email needs to become structured work. Engineer notes need to become a clear report. A report may need to inform a quote. Previous visits may explain why a new issue looks familiar. Those transitions consume time and are easy places to drop context.
FSM can parse, group, summarise and draft. It can bring related history back into view. It does not decide that work is complete, approve its own quote or turn an uncertain match into a fact.
The coordinator gets a smaller, better set of decisions, with the source material always available when judgement is needed.
Running it ourselves changes the backlog
Using FSM for our own aftercare means product problems arrive as operational problems.
If incoming messages group badly, someone has to untangle them. If a job title falls back to an unhelpful subject, the schedule becomes harder to scan. If a visit report does not carry the right context forward, the next engineer feels it immediately.
That feedback changes what gets built. Small details such as dependable titles, visible source messages, undo paths and a clear distinction between suggested and confirmed data become core product work rather than polish for later.
Daily use keeps the product focused on dependable titles, visible source messages, undo paths and a clear distinction between suggested and confirmed data. Working with different businesses adds new terminology, rates, approval paths, customer records and ways of scheduling engineers. FSM's multi-tenant design preserves those differences while keeping each organisation's data and workflow distinct.
The loop is the product
FSM is not a collection of disconnected screens for jobs, quotes and invoices. Its value is the continuity between them.
An enquiry should become a job without losing the original request. A visit should add evidence to that job. A report should make the next action clearer. A quote or invoice should remain connected to the work that produced it. Follow-up should happen with the whole history in view.
Running our own aftercare through FSM keeps that loop improving every day and turns operational experience directly into a stronger product.