# Open Service | Open Mercato Case Study

Source: https://www.openmercato.com/case-studies/open-service

# Open Service

A centralized field service platform replacing scattered tickets, spreadsheets, and tribal knowledge with one system for intake, machine history, and technician scheduling.

Delivered by

[ScaleOMasvg]:block [&>svg]:size-full [&_[stroke-width]]:[stroke-width:var(--icon-stroke)] [&>svg]:[stroke-width:var(--icon-stroke)] mt-1.5 size-3" style="--icon-stroke:2.4">](https://www.openmercato.com/certified-partners/scaleoma)

Client

Demo — field service management

Industry

Field Service Management

Timeline

Hackathon build

Type

Vertical operations system (demo)

Stack

Open Mercato core — auth, multi-tenancy, audit logs, module APIsOmnichannel ticket intake (email, phone, SMS, web)Machine + technician data model

Want to build something similar? Start with Open Mercato.

## About this build

Open Service is a demo application built on Open Mercato for field service management teams. It shows how the framework can become the foundation for a vertical operations system covering ticket intake, equipment records, and technician scheduling.

## What it does

Open Service consolidates the field service workflow into one platform: omnichannel ticket intake across email, phone, SMS, and web forms; a machine database with serial numbers, location, warranty status, and repair history; and technician profiles with competencies and certifications. Scheduling and assignment run through a five-step flow — customer report, machine lookup, technician assignment, visit scheduling, and service history documentation.

## Why it matters

Field service teams often run on fragmented systems: customer reports scatter across email, phone, and SMS, machine data lives in downloads folders, and technician availability exists only in one person's head. That works for a small team and breaks down as the operation scales past a spreadsheet.

## Built on Open Mercato

Open Mercato provided the AI-Engineering Foundation Framework — authentication, multi-tenancy, audit logs, and module APIs — so the team could focus on field-service logic instead of platform plumbing.

**Team:** Bartosz Wysocki, Łukasz Chruściel, Łukasz Kurasiński, Jarek Kałasz, Robert Starecki, Dawid Posała.

Screenshots

## Discover more projects

### [Senior Care Operations](https://www.openmercato.com/case-studies/senior-care-operations)

A demo for German non-medical senior care providers — dashboards, scheduling, and signed service-confirmation workflows, built on Open Mercato.

### [MRP System](https://www.openmercato.com/case-studies/tracecore)

An on-premise MRP system giving food and pharma manufacturers integrated production, warehouse, and sales operations with native LOT traceability and GMP-ready audit trails.

## Software is about to be built completely differently.