Qserve — Field-service operations platform
Problem
A single field-service request touches a customer, a technician, a franchise operator and an admin before it closes — and each of them needs a different, correct view of the same underlying ticket.
What we built
An explicit state machine for the technician journey — assigned, en route, arrived, OTP-verified start, in service, OTP-verified completion — coordinated with workforce scheduling, evidence capture and role-based permissions shared across all four actor types.
Impact
Turned a process that depended on phone calls and manual coordination into an auditable, state-driven workflow: every ticket has one source of truth for where it is and who is accountable for the next step.
Technology
- Flutter
- Node.js
- React
- SQL