Requests as tracked tickets
Every request becomes a ticket with a status, so jobs are tracked to closure.
Service requests, technicians, and parts that meet on the job.
Maintenance services ERP that runs the reactive and recurring work — requests as tracked tickets, the technicians and spare parts to close them, procurement to replenish, and cost against the client.
Maintenance work arrives from everywhere and gets closed with parts nobody logged. A request comes by phone, a technician fixes it with a part off the van, and the connection between the job, the labour, and the spare used is never made — so recurring jobs slip, parts run out unnoticed, and the cost of serving a client is a mystery. Farexa makes the ticket the anchor: every request is tracked with a status, the technician is assigned to it, and the parts used are issued against it from stock.
Reactive and recurring work live in the same system. A breakdown and a scheduled service are both tickets in one queue, so planned maintenance doesn't get crowded out by firefighting. Spare parts are issued against the job from inventory and replenished through controlled procurement, and workforce deployment records which technician did what — so the labour, the parts, and the job are one record, and cost rolls up against the client.
It's the difference between a maintenance operation that reacts and one that's run: requests tracked to closure, technicians and parts coordinated on the job, recurring service scheduled, and the cost of serving each client visible instead of guessed.
Key features
How Farexa maps to maintenance services.
Technician assignment
Assign technicians to jobs and see who's on what.
Spare parts from stock
Issue parts against the ticket from inventory, so material use is on the job.
Reactive and recurring in one queue
Breakdowns and scheduled service are both tickets, so planned work isn't crowded out.
Procurement for parts
Replenish spares through controlled purchasing when stock runs down.
Workforce deployment
Record which technician did what, with attendance behind the hours.
Cost against the client
Labour and parts roll up per client, so the cost of service is visible.
Guest-raised requests
Clients can raise a request and follow it without an account.
How it works
From request to cost per client.
01
Set up clients and parts. Create client sites, service categories, technicians, and spare parts.
02
Capture the request. Requests from any channel become tracked tickets with a status and priority.
03
Assign and fix. Assign a technician, issue parts from stock, and record completion on the ticket.
04
Replenish and schedule. Replenish parts through procurement, and schedule recurring maintenance.
05
Read cost per client. Labour and parts roll up per client, so the cost of service is visible.
Who it's for
Who maintains with it.
- Maintenance and repair companies — Reactive and recurring jobs tracked with parts and labour on the ticket.
- MEP and equipment service firms — Technician and spare-part coordination on every job.
- Appliance and AMC providers — Annual maintenance contracts run as recurring tickets.
- Service managers and owners — Managers run the queue; owners read cost per client.
Works with
The app cluster for maintenance.
- Support Tickets — The tracked request queue at the centre.
- Inventory — Spare parts issued against the job.
- Procurement — Controlled replenishment of spares.
- Workforce — Technician deployment, with attendance.
- Analytics — Cost-per-client and service reporting.
FAQ
What maintenance firms ask.
Does it handle both breakdowns and scheduled maintenance?
Yes. Reactive breakdowns and recurring scheduled service are both tickets in one queue, so planned maintenance isn't crowded out by firefighting — they're run in the same system.
Are spare parts tracked against the job?
Yes. Parts are issued against the ticket from inventory, so the spare used is recorded on the job, and procurement replenishes stock through controlled purchasing when it runs down — no more parts vanishing off the van unlogged.
Can I see the cost of serving each client?
Yes. Labour and parts roll up per client, so the cost of service is visible rather than a mystery — which is what tells you whether an annual maintenance contract is priced right.
Can clients raise and follow requests?
Yes. Requests from any channel become tracked tickets, and guests can raise and follow a request without an account, so nothing depends on someone remembering a phone call.
Which apps does a maintenance company start with?
Usually Support Tickets and Inventory to get the request queue and spare parts in order, then Workforce, Procurement, and Analytics as technician deployment and cost-per-client fill in.
Bring the job, the tech, and the part together.
Book a walkthrough with your own clients and parts, and see requests tracked to closure with cost per client.