SERVICE

Who is going where, settled by dragging.

Service calls arrive all week and rarely in a helpful order. The dispatch board puts every technician on a row, every open job in a rail, and lets you sort out the week by moving cards.

Request a demo Talk to us

Day and week views
Assign by dragging
Skills and zones

Technicians are rows, days are columns, and the rail on the right is work nobody is going to yet.

Drag to assign Rail to a cell books it. Cell to cell moves it.

Skills and zones The board suggests who is qualified and nearby.

Warnings, not gates It tells you what is wrong and still lets you do it.

Through to the invoice A completed visit is a job ready to bill.

Field service, request to invoice

Four moves, and the thing each one hands the next. Everything below is a detail of one of them.

A request that nobody approved never reaches the board, and a visit that never happened never reaches the invoice.

Technician scheduling by dragging

There is no scheduling form. Every arrangement of the week is made by moving a card, and every move is the same instruction the work order screen would have sent.

The day view. Each card is as wide as the job is long, so a day that is over — Alvarez at 9h against 8h — looks over before anyone adds it up.

Rail to a cell assigns it

The rail holds open work nobody is going to — all of it, not only the jobs that fall inside the week on screen. Drag one onto a technician’s day and it is booked.

Cell to cell moves it

Dropping a card on another technician, or another day, reassigns and reschedules it in one gesture rather than two edits on two screens.

Back to the rail unassigns

Plans change on Friday morning. Pull the card back and the job returns to the queue with its priority and due date intact.

Or let it suggest

Ask for a suggestion and the board ranks technicians by the skills the job needs and how close it is to their patch — then you still choose.

A day laid out in half hours

The day view runs 07:00 to 18:00 in thirty-minute slots, and each card is as wide as the job is long, so a full day looks full.

Work already under way stays put

Once somebody has travelled, or the order is closed, the card stops being draggable. The board will not quietly rewrite a job that has already happened.

It warns. It never refuses.

A missing skill, a double booking, a technician already at capacity — the board colours the drop, tells you what is wrong, and lets you do it anyway.

The four things it says after a drop, in the words it uses. Said after the move, never instead of it.

Not qualifiedIt names the category the technician is missing, because “not qualified” on its own is not something a dispatcher can act on.

Over capacityIt says how far past a 8-hour day the drop would put them, so you know what you are choosing.

Still your callThe dispatcher usually knows something the data does not. A Friday-afternoon emergency has to be coverable by whoever can actually get there.

Work orders, technicians and price books

The board is the part you look at every morning. It sits on top of the records that make the scheduling mean something.

One work order: lines priced from the customer’s service book, and the visits made against it — a failed first fix is a fact on the record, not a rescheduled appointment.

Service requests

What the customer asked for, before anyone commits to it — logged, acknowledged, then approved or turned down, with the reason recorded either way.

Work orders

The job itself: lines for labour and parts, a priority from low to emergency, and a status that runs draft, scheduled, in progress, on hold, completed or cancelled.

Technicians and skills

A technician is a user, so work reaches them through the login they already have. Skills are service categories, and a home zone feeds the board’s suggestions.

Service locations

One customer, several sites. The job is raised against the address the engineer actually has to reach, not the one that gets the invoice.

Service price books

Labour and parts priced per customer or contract, with quantity tiers, and a book that can be drafted, scheduled to start, active, then expired.

Visits

Each trip against the job — planned, in progress, completed, failed or cancelled — so a second visit is a fact on the record rather than a rescheduled first one.

It shares the platform’s spine

Service is not a separate system with its own customer list. It reads and writes the same records the rest of the operation runs on.

Route Send a technician’s day to their round and it is navigated like any other. Back office A completed job is a job ready to bill, against the customer it belongs to. Presales The same customers and price books the sales side already uses. AI Dashboard Ask how the service week went and keep the answer as a widget. B2B ecommerce Customers raise their own requests instead of ringing the office. Custom development The open API reaches work orders and the board the same way.

Frequently asked questions

Can I assign a job to someone who is not qualified for it?

Yes. The board colours the drop, names the skill they are missing and asks you to confirm — but it does not refuse. Skill gaps, double bookings and over-capacity are all advice, on the view that a dispatcher usually knows something the data does not.

Does the board schedule differently from the work order screen?

No, and that is deliberate. Every drag lands on exactly the same assign and unassign instructions the work order screen sends. The board is a faster way to reach them, never a second way to schedule, so the two can never disagree.

Can I see a single day rather than a week?

Yes. The day view lays out 07:00 to 18:00 in thirty-minute slots, and each card is drawn as wide as the job is long, so an overfull day is visible rather than implied.

What happens to a job somebody has already started?

It stops being draggable. Once a technician has travelled, or the order is closed, the card is fixed on the board — changing it goes through the work order, where the change is recorded.

How does the work reach the technician?

A technician is always a user, so the job appears under the login they already have. There is no separate app account to issue or to forget to revoke.

Can a technician’s day become a route?

Yes. A day of calls can be dispatched to that technician’s round, so a service run is navigated and tracked like a delivery run rather than being a list of addresses in a message.

How is service work priced?

From service price books, which hold labour and parts per customer or contract, with quantity tiers. A book can be drafted, scheduled to take effect, active, or expired, so next year’s rates can be loaded before they apply.

Can one customer have several sites?

Yes. Service locations sit under the customer, so the job is raised against the site the technician has to reach while the invoice still goes to the account that pays.

Does a failed visit close the job?

No. A visit can be completed or failed in its own right, and the work order stays open, so a second trip is a recorded fact rather than a quietly rescheduled first one.

Bring us a week that went wrong

The week with the emergency, the no-show and the two jobs nobody was qualified for. We will lay it out on the board and you can watch it get sorted.

Request a demo Talk to us