herbe service: questions and answers

No. Orders, dispatch, worksheets and checklists run on their own, and a company without an ERP can issue its own invoices. Van stock is the exception: it reads levels from your ERP. The connection is switched on when you are ready, not as a precondition.

Yes, two-way, with Excellent Books and with Standard ERP by HansaWorld, known as Excellent ERP in the Baltics, Finland and Norway. Customers, items, prices, contracts and equipment come from the ERP; approved worksheets go back and the invoice returns linked to the order.

All of the technician app does, including airplane mode. The briefcase downloads the next days' work; the outbox sends queued actions when the network returns; conflicts become visible tasks instead of silent overwrites.

The phone is paired once, with a link from an admin or with herbe ID. After that, a PIN opens it. No email and no password, day to day.

Yes. An admin switches herbe ID on for your account. Office staff then sign in with it, and technicians can pair their phone with it. Once AI is switched on for a person, they can connect Claude, ChatGPT or Codex through herbe assist and ask about orders, the board, worksheets, quotes and customers. The assistant works with that person's own role and companies. A quote or invoice for a customer, or a worksheet approval, is finished by the person with an approval link in herbe service.

On site, by signing on the phone, or in herbe portal, with one report per order and an e-signature through Dokobit or eParaksts. No portal? The report goes by email as a PDF. A rejection keeps the order open: fix the gap, present it again, sign again.

Yes. With herbe calendar connected, service jobs also appear there next to the rest of your team's day, and the dispatch board shows each technician's calendar events and away days.

Yes, per unit type: numbers with an expected range, required questions, photo questions. A reading outside its range is flagged for the office, not refused. Every unit's readings collect on its record, one row per visit.

Yes. The dispatch board has a Map view: one day's jobs, one pin per site, with waiting work as outlined squares. It is a switch per company.

With an ERP, the ERP issues the invoice. Approval pushes the work facts, each row with its charge type (invoiceable, warranty, contract or goodwill), and only invoiceable is charged. Without an ERP, you issue the invoice here. A mistake found after invoicing becomes a correction worksheet, never an edit.

No. Parts and hours are settled when a manager approves each worksheet, whatever the customer has or has not signed or accepted.

They hand it back to the office with a reason. The job returns to the dispatcher's list carrying that reason, and what was recorded stays on the sheet.

Switch on Show queue and it gets its own tab on the board. Nothing moves by itself; you plan the next visit and the same booking moves to it.

No. Levels are a read-only copy, each row shows when it was read, and booking a transfer stays in the ERP.

Open the office demo or the field demo, leave your email and a one-tap link takes you in. Prefer a walkthrough built around your own service process? Book a demo.