Get started
OperationsLive · in the productQueue & board

FieldService

Breakdown, PM and installation tickets on an SLA clock, the engineer’s phone visit report with spares and sign-off, and repairs sent to the maker.

Installs with InstalledBase, whose screen it works on
Get FieldServiceOpen the appAvailable nowHow pricing works →

What it is

Service tickets on InstalledBase units: a breakdown, a PM visit from ContractCare, an installation, or a repair sent to the maker. The clock is the covering contract’s response and resolution targets, or else your own target for the ticket’s priority, with where it comes from; a ticket with neither is shown as untimed rather than measured against a figure nobody chose. Dispatch names an engineer. On their phone the engineer opens their jobs, nearest deadline first, taps I’m here (the response clock stops), records the spares fitted from stock — free under a contract that covers parts, otherwise chargeable: on the bill for a person’s unit, and for a trade customer’s checked as OrderBook checks a sale and invoiced on TradeLedger when the visit is reported — writes what was done and the outcome, and takes the customer’s sign-off by name; fixed needs the sign-off and resolves the ticket, and a PM ticket settles its PM visit. A unit sent to the maker or a service centre records where, when, the claim reference and whether it was under warranty on the day it went; it is away for repair until it is back and handed over. Opticians and hearing-aid shops use the same repair path for anything on their installed base.

Who uses it
Built for: Every specialty
Reads
InstalledBase units, ContractCare contracts and PM visits, StoreStock spares
Writes
Service tickets, engineer visits and sign-offs, spares used, TradeLedger invoices for a trade customer’s spares, repairs at the maker
Never
It ships no response or resolution target, and does not repair anything: the engineer or the maker does.
Access
Only people whose role includes it — the clinic owner decides who
Your data
PHI-lite. Hosted in Boston, United States. On uninstall: The ticket list stops; every ticket, visit, spare and repair is kept.

In the product

Who uses it
Operations manager — the demo profile it is best tried as
Where it opens
Operations › Field service /field-service
Permission
fieldservice.read
Every operations app in the handbook →

How it works

  1. Open the ticketThe unit, the problem, the priority; the clock starts.
  2. Dispatch an engineerThey see the job on their phone.
  3. Visit, fit spares, sign offFrom the phone, with the customer’s name.
  4. Send to the maker if neededAway until it is back and handed over.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It ships no response or resolution target, and does not repair anything: the engineer or the maker does.
A hearing aid fitted in AudioLab keeps AudioLab’s own service jobs.

AI in FieldService

AskQuestions about what is on screen — “What needs attention in FieldService today?” — answered with the records it read.
DraftSummaries and notes for the team, marked as drafts until a person signs.
Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

Live product
01Field service — Run service tickets on an SLA clock, with engineer visits from the phoneCaptured from the running demo clinic
FieldService — Field service — Run service tickets on an SLA clock, with engineer visits from the phone
1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

See the whole clinic →

Questions clinics ask

What does FieldService do?
Breakdown, PM and installation tickets on an SLA clock, the engineer’s phone visit report with spares and sign-off, and repairs sent to the maker. Service tickets on InstalledBase units: a breakdown, a PM visit from ContractCare, an installation, or a repair sent to the maker. The clock is the covering contract’s response and resolution targets, or else your own target for the ticket’s priority, with where it comes from; a ticket with neither is shown as untimed rather than measured against a figure nobody chose. Dispatch names an engineer. On their phone the engineer opens their jobs, nearest deadline first, taps I’m here (the response clock stops), records the spares fitted from stock — free under a contract that covers parts, otherwise chargeable: on the bill for a person’s unit, and for a trade customer’s checked as OrderBook checks a sale and invoiced on TradeLedger when the visit is reported — writes what was done and the outcome, and takes the customer’s sign-off by name; fixed needs the sign-off and resolves the ticket, and a PM ticket settles its PM visit. A unit sent to the maker or a service centre records where, when, the claim reference and whether it was under warranty on the day it went; it is away for repair until it is back and handed over. Opticians and hearing-aid shops use the same repair path for anything on their installed base.
What data does FieldService read and write?
FieldService reads InstalledBase units, ContractCare contracts and PM visits, StoreStock spares and writes service tickets, engineer visits and sign-offs, spares used, TradeLedger invoices for a trade customer’s spares, repairs at the maker. Its data class is PHI-lite. Every app works on the same patient record — nothing is copied into a silo.
What does FieldService deliberately not do?
It ships no response or resolution target, and does not repair anything: the engineer or the maker does. A hearing aid fitted in AudioLab keeps AudioLab’s own service jobs.
What happens to our data if we uninstall FieldService?
The ticket list stops; every ticket, visit, spare and repair is kept.
Is FieldService available today?
Yes — FieldService is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see FieldService running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

We use your name, phone number and clinic name for one thing: to answer this enquiry about MedAppz. It is stored on our own server, in the single region our trust centre names, and it is not sold or passed to anyone else.

Email us

You can withdraw either at any time: write to hello@medappz.com, or tell whoever calls you, and we will delete what you gave us.

More in Operations

All 97 →