The job after the sale. A customer rings about a window that won't latch; Onsite turns the call into a ticket against the BisTrack order it came from, puts a technician in front of it with an app that works in a basement, and files what they saw back onto the order where your counter staff already look.
Service is the part of the business that falls out of the ERP. The order is in BisTrack; what went wrong with it ends up in a shared mailbox, a spreadsheet, or a help desk that knows nothing about your orders. Onsite puts it back — a ticket that starts from the real sales order, a technician who gets the job on their own phone, and everything they recorded filed against that order in BisTrack's own document store.
Search the customer, the address or the postcode — you're searching BisTrack, so what you find is what BisTrack knows. Pick the sales order the complaint is about, and the ticket is anchored to it for good.
Describe what's wrong as structured issues: a category, a location on the site, a note. Your categories, your locations, your service types, your statuses — Onsite ships with none of them and no status name is written into the software.
The schedule board is the day as columns of technicians, one department at a time — which is the only view that's usable when a branch runs five to ten technicians in a department and no real crossover between them.
Book a visit, drag it to somebody else, move it to tomorrow. The technician's phone has it on its next sync, and the homeowner can be told automatically if you want them to be.
Technicians install it to their home screen from a link you email them — no app store, no device management, no profile. It opens full screen and holds the day's work on the phone.
The address, what's wrong, the order lines and the spec sheets the office attached are all there with the phone in airplane mode. Notes, photographs and video queue up and send themselves when signal comes back. The documents are the part that matters: a drawing is wanted precisely where there's no coverage, which is why it's downloaded before the technician leaves the yard rather than fetched when they need it.
A photograph of the damage, a short clip of the sash that binds, and what they actually did — recorded on the phone, at the house, rather than written up from memory at five o'clock.
If the job needs a part, the technician records it and the ticket moves to the status you nominated for it. Onsite doesn't order anything: a service part gets ordered differently at every branch, and automating the wrong one is worse than automating none.
Photographs, video and PDFs are filed into the BisTrack attachment folder you nominate, through BisTrack's own procedures, under a service identity you choose — so they appear in Related Documents and your audit log reads the way it always has.
The technician's account of the job goes onto the sales order's notepad, which is where counter staff already look when a customer rings back. A note can carry a follow-up that lands on a BisTrack user's own calendar.
Onsite does not create or change an order, an invoice or a purchase order, and it does not move an order's status. Everything it writes is a document or a note filed against a transaction.
That's a design rule, not a setting — which is why a service desk can be given it without a change-control conversation, and why nothing it does can arrive at the rest of your systems looking like an order having changed.
Not "works offline" as a feature bullet — built for it. The work list, the addresses, the faults and the documents are held on the handset, and everything recorded is held there until there's signal to send it.
A document that isn't on the phone says so, in words, on the visit — "2 documents not on the phone yet" — while the technician is still in the yard, which is the only moment it can be fixed. A silently missing drawing is the failure the whole thing exists to prevent.
Statuses, service types, issue categories, site locations, departments — every list a ticket is described with is yours to define, and no status name appears anywhere in the software.
A status carries a colour and a state; the state is what Onsite reasons about, the name is what your people read. Rename it on a Tuesday and nothing breaks.
Forty technicians with the field app, a service desk, and the sales reps who raise tickets for their own customers — all on one licence. Nobody has to decide who is worth a seat.
Which is usually the conversation that starts this one: a per-seat help desk gets rationed until the people who most need it are the ones without it.
Onsite is licensed on its own and runs on the Hook-Tech One hub, alongside whichever other applications you own. Licensing is per company, not per seat — which matters when forty technicians need the field app.
Build your suite Convoy for BisTrack →