A van salesman, a service engineer and a delivery driver all have the same problem with attendance: there is no gate to walk through. tBiz checks them in where they actually are, against the site they were supposed to be at.
A check-in outside the site’s radius is flagged with the distance, rather than being silently accepted or bluntly refused.
What was done at each stop — order taken, payment collected, complaint logged — against the party in the ledger.
Where somebody actually went, in order, so a route can be planned better next week rather than argued about this one.
Take the order on the phone against live stock and the customer’s credit position, and it is in the system before the van moves.
A receipt entered at the customer’s premises settles against their open invoices immediately.
Tracking requires the employee’s own consent as well as the company’s setting, and it runs while the app is open — not silently in the background.
No. Location is captured while the app is open — at check-in, at each visit and at check-out. Continuous background tracking needs a native build and is not what ships today, and we would rather say so than let you assume otherwise.
The check-in is recorded and flagged with the distance from the site. It is not refused, because a genuine reason is common — the customer moved the meeting — and a flag that a supervisor reviews is more useful than a block that gets worked around.
Yes. There are two switches: the company enables it and the employee consents on their own device. Without both, no location is captured.
They can take an order wherever there is a signal, against live stock and the customer’s credit limit. A patchy signal delays the sync rather than losing the order.
Start free, map one customer site, and see a geofenced check-in land in the attendance register.