Service management system built on Open Mercato. Centralizes tickets, machine data, technician scheduling, and repair history, so coordinators stop juggling spreadsheets, email, and phone calls to keep customers moving.
Field service teams shouldn’t be chasing customer reports across email, phone, and SMS while machine data lives in someone’s downloads folder and technician availability lives in one person’s head. Open Service consolidates the whole loop into one workflow.
What it does
Every service request lands in a single inbox (email, phone, SMS, web form) and gets matched against a machine record (serial number, location, warranty status, complete repair history) and a technician profile (competencies, certifications, current schedule). Coordinators assign the right person, book the visit, and the system writes the history back to both the customer and the equipment.
The workflow runs in five steps: customer report → machine lookup → technician assignment → visit scheduling → service history documentation. No spreadsheet handoffs, no “ask the dispatcher when she gets back.”
Why it matters
Spreadsheet-driven service operations break the moment you grow past a handful of techs. Coordinators become the bottleneck; repair history gets lost between notes apps; warranty calls get billed by mistake. Open Service replaces the patchwork with one source of truth across customer, machine, ticket, technician, schedule, and history.
Built on Open Mercato
Open Service ships on top of Open Mercato, the AI-Engineering Foundation Framework that starts you with 80% done. Auth, multi-tenancy, audit log, and module APIs come from the platform, so ScaleOMa focused the build on the service workflow itself: omnichannel intake, the machine database, technician skill matching, and the scheduling primitives.
The result is a system an in-house service team can extend with custom fields, ERP integrations, or SMS providers, without touching the foundations. Open source, full control, zero vendor lock-in.
