📍 Zoho based Client Appointment / Journey Plan (Beat Plan) – Mobile User
Overview
This module facilitates field representatives in logging their appointments or journey plans via mobile devices. It includes powerful features such as geofenced vs. non-geofenced check-ins, planned vs. unplanned journey differentiation, and dynamic partner location updating.
🔁 Key Functionalities
✅ 1. Appointment Check-in / Check-out
Each appointment or journey includes:
Check-in Information:
Checkin_LatitudeCheckin_LongitudeCheckin_TimeCheckin_State,Checkin_City,Checkin_Area
Check-out Information:
Checkout_LatitudeCheckout_LongitudeCheckout_TimeCheckout_State,Checkout_City,Checkout_Area
Outcome:
Out_Come(final result/feedback)
Additional Data (CRM Update):
Address, Locality, Country, Pincode
Status
Expense Flag:
isExpense
📍 Geofencing Logic
🔐 Geofenced vs Non-Geofenced Check-in
When Geofencing is enabled for a client:
The system checks if the partner’s coordinates (from the journey record) match the client’s location.
If matched:
✅ The check-in is marked as geofenced.
If not matched:
❌ The system:
Marks the first visit as non-geofenced.
Updates the partner's coordinates based on current user location for future visits.
This ensures accuracy and enables future check-ins to occur within the defined geofence.
📅 Journey Type
🔹 Planned Journey
Predefined and listed in the mobile app.
Subject to regular approval workflows.
🔸 Unplanned Journey
Created spontaneously by the mobile user.
Automatically approved upon submission.
Clearly distinguished in the system for reporting and tracking.
🧠 Smart Coordination Capture
Each journey captures the geolocation for both check-in and check-out to validate field visits, compute time spent, and track travel paths, helping optimize future routing and attendance policies.
💡 Notes
Geofencing logic is configurable per client.
Data captured in each appointment is synced to the CRM backend.
Integration supports dynamic behavior per visit, reducing manual coordination.