Question 1

How does the system verify that a visit really happened?

Accepted Answer

The check-in captures GPS coordinates and validates them against the geofence of the customer being visited. A check-in outside the boundary is flagged, so the difference between an on-site visit and a nearby one is visible in the data rather than left to trust.

Question 2

Can we design our own visit report format?

Accepted Answer

Yes. Visit forms are built from your own fields, and different visit types can use different forms — a stock check, a collection call and a demo all capture different things. Once a form version is in use it is preserved, so historical reports keep the structure they were submitted under.

Question 3

What happens when a rep has no network at the customer site?

Accepted Answer

The visit is captured on the device and synced when connectivity returns. The record keeps the original visit time, and the sync is idempotent so a retry cannot create duplicate visits.

Question 4

Does this replace our CRM?

Accepted Answer

No, and it is not trying to. CRM manages the pipeline and the customer relationship; this manages whether the field activity behind that pipeline actually took place and what was observed on site. Companies commonly run both.

Question 5

Can field visits be linked to attendance and expenses?

Accepted Answer

Yes — that is a large part of the value. A rep's attendance, verified visits, travelled distance and expense claims sit in one system, so a claimed day of eight visits and 120km can be checked against what was actually recorded.