Loading
Because the job sheet is paper or a photo. It reaches the office days later, somebody types a summary, and parts and time get rounded or missed.
Out-of-contract work is absorbed because reconstructing it days afterwards is not worth the argument.
The request becomes a ticket carrying its entitlement, scheduled against real availability from Nest. The visit is a task in Loop with its own time and parts.
What was done is recorded on site: parts consume stock in Books, time becomes billable where the contract says so.
It will not optimise routes. Scheduling respects skills and availability; geography stays a scheduler's judgement.
Offline capture syncs on reconnection, which is a delay rather than a loss.
Entitlement is visible before the engineer travels, so out-of-contract work is a conversation beforehand rather than an awkward invoice after.
Billing reflects the visit because it was captured where it happened.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Capture does, syncing when reconnected.
Yes, recorded against the visit.
Yes, as stock locations in Books.
Half an hour on your own numbers is usually enough to say whether Desk is the right place to start.