Visit

One stop inside a journey plan: which customer, which employee, which date, and what actually happened when the employee arrived.

Stored in the VISIT layer.

---

Fields

Field	Required	What it is
visit_target_guid	Yes	The customer being visited
visit_assignee_username	Yes	Employee carrying out the visit
visit_date	Yes	Scheduled date
visit_status	Yes	1 To do, 2 Checked in, 3 Done, 4 Cancelled
visit_priority	Yes	1 Lowest, 2 Low, 3 Medium, 4 High, 5 Highest
visit_objective	Yes	What the visit is meant to achieve
visit_estiamte_time		Expected duration in minutes. Defaults to 30
visit_address	Yes	Where the visit happens, normally copied from the customer
visit_location		GeoJSON Point (WGS84) of where the visit should happen
visit_boundary		GeoJSON Polygon (WGS84) used to check the visit happened in the right area
visit_postal_code	Yes	Postal code of the visit address
visit_administrative_1	Yes	State of the visit address
visit_administrative_2	Yes	District of the visit address
visit_administrative_3	Yes	Tehsil of the visit address
visit_contact_full_name	Yes	Who to meet, normally the customer contact
visit_contact_phone_number		Contact phone number
visit_contact_email		Contact email
visit_ticket_no		Ticket number generated per customer when the plan is created
visit_checkin_time		Written by the platform when the assignee checks in
visit_checkin_by		Who checked in
visit_checkin_location		Where the check-in happened
visit_checkout_time		Written by the platform at checkout
visit_checkout_by		Who checked out
visit_checkout_location		Where the checkout happened
visit_checkout_form		Form completed at checkout
visit_cancel_time		When the visit was cancelled
visit_cancel_by		Who cancelled it
visit_cancel_reason		Why it was cancelled
visit_time_tracking		Time spent on the visit
visit_order		Position of the visit inside the plan
visit_type		Type of visit, which can decide the form to submit
visit_guid		Assigned by the platform
visit_plan_guid		The plan this visit belongs to

---

Used by

• PJP API