Field Service

Interventions at your customers scheduled, time tracked, parts recorded, customer agreement signed and lines to invoice prepared.

In preparation Create an account

Field Service follows interventions at customers' premises: repairs, maintenance, installation. A dispatcher creates the intervention, assigns it to a technician and schedules it. The technician leaves, starts, tracks working and travel time, records the parts used, writes a report, has the customer sign and completes. The dispatcher then prepares the lines to invoice and keeps the reference of the invoice issued in another tool, Business for example.

The life cycle is checked by the services and by the database: draft, scheduled, on the way, in progress, completed, invoiced, or cancelled with a reason. A technician has only one open time entry at a time. Each intervention keeps a log of what was done, by whom and when.

The customer's signature is a simple electronic signature, a proof of agreement on the work: it is not a qualified signature within the meaning of the eIDAS regulation, and it does not identify its author. The image is checked, limited to 200 KB, accompanied by a SHA-256 fingerprint, and can no longer be modified.

No rates are supplied: as long as the hourly rate is not set, invoicing preparation refuses working time. Field Service does not invoice by itself and has no live link with CRM or Business.

It is a web application, designed for a phone's browser in the field, with no offline mode and no desktop or Android application. AI agents reach it through MCP tools, and the main changes are sent to Workflows as events.

Field Service is in preparation. It will join the Etrebil subscription catalogue when it is released.

Every feature of Field Service

61 features in 10 areas

Interventions and scheduling

Creates an intervention for a customer: title, description of the work, priority (low, normal, high, urgent) and address, taken from the customer's when left empty.
Gives each intervention a yearly code, for example INT-2026-001, whose prefix can be set.
Schedules by assigning an active technician, a planned start and end; reschedules an intervention that is already scheduled.
Moves the intervention from draft to scheduled, on the way, in progress, completed then invoiced; the only step back is suspension, by a dispatcher.
Cancels with a reason as long as the work is not completed; invoiced and cancelled are final states.
Checks the life cycle in the services and in the database: a completed intervention keeps its description, assignment and dates.
Lists interventions, filtered by state, by technician and by a search on the code, title or customer; the same search is in the header bar.
Displays and enters times in the organization's time zone, Europe/Paris at the start; dates are stored in UTC.

Customers

Customer record: name, address, on-site contact, phone, email and an external reference in free text (CRM, Business).
Searches customers; a customer with interventions cannot be deleted, to keep the history.
The full list is reserved for dispatchers; a technician sees the customer on the page of each of their interventions.

In the field: round and time tracking

The My interventions page shows as cards, with large buttons, what awaits the technician, what is in progress and what has just been finished.
The customer's phone number is a call link there.
The technician leaves for the site, starts and completes from this page or from the intervention's page.
Tracks working time during the intervention, and travel time on the way or on site.
A technician has only one open time entry at a time, which the database also guarantees, and their time entries do not overlap.
Starting closes the travel entry left open; completing, cancelling or suspending closes the intervention's open time entries.
A forgotten time entry can be entered afterwards, never in the future; a dispatcher removes a wrong time entry during the intervention.
The technician's report is written during the work and can still be refined once the intervention is completed.

Parts and customer signature

Records the parts used: reference, description, quantity and unit price excluding tax, editable as long as the intervention is not completed.
Collects the customer's signature, drawn with a finger or a mouse, with the signatory's name, during the intervention or just after it ends.
Checks the image received: PNG verified block by block with its checksums, 200 KB at most, 4,096 pixels per side at most.
Computes the SHA-256 fingerprint of the image itself and displays it with the signatory's name and the date.
A single signature per intervention, never modified or deleted: the database refuses it.
It is a simple electronic signature, a proof of agreement on the work; it is not a qualified signature within the meaning of the eIDAS regulation, and it does not identify its author.

Invoicing preparation

Prepares the lines to invoice for a completed intervention: labour, travel flat fee, one line per part, total excluding tax.
Rounds each intervention's working time up, to the minute, the quarter hour or the half hour.
Counts the travel flat fee only once per intervention that has at least one travel time entry.
Calculates in decimal, without floating point, with amounts rounded to two decimals; each line recalculates identically.
Adds VAT and the total including tax only if a VAT rate is set.
Refuses to prepare time to invoice as long as the hourly rate is 0, and says where to set it.
Marks the intervention as invoiced, keeping the number of the invoice issued elsewhere, Business for example; it no longer changes afterwards.
Settings and rates can be read by everyone and changed only by an administrator: hourly rate, flat fee, VAT, rounding, code prefix, time zone.

Roles, access and log

Three roles: technician, who sees and carries out their interventions; dispatcher, who sees everything, creates, schedules, assigns, cancels and prepares invoicing; administrator, who also manages roles and rates.
A technician does not see drafts: an intervention appears to them once it is scheduled.
Rights are checked by the services, not only by the interface; a dispatcher can perform the field actions on behalf of a technician.
The first person of an organization to arrive, and any Etrebil owner or administrator, is administrator by default; the others start as technicians.
Colleagues and roles page: change a role, suspend or restore access; suspended access becomes read-only.
Without a license covering the application, everything can be read and nothing can be written.
Each intervention has its log, who did what and when, from creation to invoicing; it can neither be modified nor deleted.

AI agents and Workflows

MCP access point for AI agents, with an Etrebil agent token; the tools go through the same services and the same rights as the pages.
Reading tools: list interventions (state, technician, period, text), read an intervention with its time entries, parts and signature without the image, prepare invoicing, list customers and colleagues.
Writing tools: create, schedule and complete an intervention, then mark it as invoiced.
No tool cancels, signs or tracks time: these actions stay on screen.
Sends Workflows the creation, scheduling, start, completion, cancellation and invoicing events, written in the same transaction as the change; neither description, address nor report leaves with them.
No public REST API: programs go through the MCP access point.

Tutorials

Create an intervention, from draft to assigned code.
Set your rates: hourly rate and travel flat fee.
Each tutorial guides step by step on the application's screens.

On your devices

Web: the complete application, designed for a phone's browser in the field as well as for the dispatcher's workstation.
Single sign-on with your Etrebil account; each organization sees only its own data.
No desktop application and no Android application for now.
No offline mode: a time entry or a signature needs a connection at the moment it is entered.

Good to know

Field Service does not invoice: it prepares lines, and the invoice issued in another tool is authoritative.
No rates are supplied; the prepared amounts follow the current rates and are not frozen.
No live link with CRM or Business: the customer keeps an external reference as text, the invoice a reference as text.
No geolocation, map, route optimization or notification.
No photo or attachment, no parts catalogue or stock.
No data import or export for now.
Signatures are kept in the database with no retention period or purge planned, and cannot be erased today.
Has only been tried on a development workstation, with a simulated sign-in: no real phone, no hand drawing, no real Etrebil sign-in, no real Workflows, no MCP tools over the protocol.