SITE VISITS

Track the visit and what happens after it.

Keep the buyer, project, appointment and assigned person on one visit record. Record the available check-in evidence, the outcome and the follow-up the team needs next.

Conceptual entrance to an Indian residential development.

From the gate to the follow-up

Make the next visit easier to hand over.

The customer should not have to repeat the plan at the gate. Give the person handling the visit the context needed to carry it forward.

  1. Before arrivalConfirm the buyer, project, appointment time and site instructions.
  2. At the siteRecord the available check-in evidence and review any location warning.
  3. Before the next callLeave the visit outcome, buyer feedback and a clear next action.

Plan, check in, review and follow up.

  1. Schedule with the right context

    Choose the buyer, project, time and assigned person. Confirm the site instructions with the customer using an available contact channel.

  2. Record the arrival

    Use the check-in action and available location evidence. A photo may be attached where the workflow supports it; a check-in is not automatically proof of attendance.

  3. Review the location result

    The record distinguishes verified, flagged and unverified check-ins. Missing or unusable location data remains unverified; a mismatch can require review.

  4. Close with an outcome

    Record feedback, the visit result and the next action. Review any flagged check-in or check-out instead of erasing the original evidence.

A GPS result has a meaning.

Verified

The recorded location met the configured checks. Review the timestamp and available evidence alongside that result.

Flagged

The record needs attention, such as a location mismatch. A manager can record a review without making the original flag disappear.

Unverified

A usable location fix or required project location was unavailable. The result must not be presented as a GPS-verified visit.

When the site has poor signal

Supported field actions can queue on the device. Keep the pending queue visible and check the saved result after reconnecting. Queued work is not confirmation that the manager already has the update.

Phone permissions, location accuracy and project settings affect the evidence available. This page does not promise a three-second update or universal GPS verification.

Keep communication and attribution separate.

Sending a confirmation or reminder depends on the configured channel, available template and delivery result. Do not assume a WhatsApp message arrived because a visit was scheduled.

For partner visits, retain the registration and attribution evidence. A visit or phone call alone does not replace the lead-ownership rule.

Channel partners, the commission ledger, CP Connect and Buyer Connect require Professional Team or Custom.

Try a visit with the evidence visible.

Review the planned visit, a checked arrival, a flagged result and the follow-up record in the demo.