Manage return visits when work requires multiple trips.
When an incident or incomplete status requires the provider to return, a Revisit is created.
GET /workorders/{id}/site-revisits
{
"results": [
{
"id": 301,
"reason": {
"id": 10,
"name": "Parts not delivered"
},
"notes": "Returning with correct router model",
"scheduled": { "utc": "2024-01-17 09:00:00" },
"status": "scheduled",
"created": { "utc": "2024-01-15 16:00:00" }
}
],
"count": 1
}POST /workorders/{id}/site-revisits
{
"revisit_reason_id": 10,
"notes": "Returning with correct parts.",
"scheduled": { "utc": "2024-01-17 09:00:00" }
}Get available revisit reasons for your company:
GET /company/{company_id}/reasons/revisit
{
"results": [
{ "id": 10, "name": "Parts not delivered" },
{ "id": 11, "name": "Customer requested callback" },
{ "id": 12, "name": "Scope change" },
{ "id": 13, "name": "Site not ready" }
]
}An Incident flags that something went wrong (e.g., "Equipment failure"). It is often the reason why a revisit is needed.
PUT /workorders/{id}/incident
{
"incident_id": 12
}Track the current state of work:
GET /workorders/{id}/job-status
{
"status": "incomplete",
"reason": "Parts missing",
"revisit_scheduled": true
}Revisits extend the work order lifecycle. Pay may be adjusted based on revisit circumstances.
Last updated on