Reference · built on requestOperator by FibricFleet, routes & field

Missed Stop

Detects planned stops with no geofence arrival or completion scan and proposes a same-day re-attempt or a rescheduled delivery.

Request accessPricing ↗

About

A stop can be skipped without anyone marking it. Missed Stop reads the day's planned stops from Onfleet or Route4Me, the arrival evidence from telematics, and the completion record. In Onfleet a task past completeBefore still in state 1 or 2, or completed with success false and a failureReason, is a miss. In Route4Me an address past its time window with is_visited false is a miss. Samsara's RouteStopArrival and GeofenceEntry events say whether the vehicle ever reached the address.

For each miss it proposes a same-day re-attempt on a driver still out, or a rescheduled delivery with a message to the customer, and the matching tracking event on the order. A dispatcher approves.

This is a reference listing. It documents what Fibric would read from Missed Stop and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Onfleet tasks with state, completeBefore, and completionDetails.success and failureReason, plus the taskFailed and taskDelayed webhook triggers
  • Route4Me route addresses with sequence_no, time_window_start, time_window_end, is_visited, and is_departed, and Activity Feed entries such as driver-arrived-late
  • Samsara RouteStopArrival, RouteStopDeparture, GeofenceEntry, and GeofenceExit events, and gps from the vehicle stats feed, as the arrival evidence
  • The order behind the stop in Shopify, with its fulfillment, so the tracking timeline can carry the attempt
  • Customer replies to a reschedule message through Twilio's inbound message webhook
  • Which drivers are still on duty and where, from Onfleet's Workers endpoints, for a same-day re-attempt

Proposed actions

  • Target capability: propose a same-day re-attempt through POST /api/v2/tasks/{id}/clone with overrides on completeAfter, completeBefore, and notes, assigned to a driver still out
  • Target capability: propose moving the address to another route through Route4Me's move_route_destination.php, or a new optimization with the address inserted
  • Target capability: propose a Twilio message to the customer offering delivery slots, with the reply captured for a person to act on
  • Target capability: propose a Shopify fulfillmentEventCreate with status ATTEMPTED_DELIVERY or FAILURE and a message, so the order timeline is true
  • Target capability: propose a Slack message to the dispatch channel listing the day's misses, each with its arrival evidence

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Re-attempt an Onfleet failure while the driver is nearby

    When taskFailed arrives with a failureReason and a driver is still on duty within reach, propose a cloned task with completeBefore set to end of shift and the failure notes carried over.

    With Onfleet

  • Prove the stop was never reached

    Join the Route4Me address with is_visited false to Samsara GeofenceEntry events for that vehicle and day; no entry means a missed stop, an entry with no scan means an unrecorded one.

    With Route4Me, Samsara

  • Keep the Shopify timeline honest

    For each confirmed miss, propose fulfillmentEventCreate with ATTEMPTED_DELIVERY and the time, so the customer's order page shows the attempt before they ask.

    With Shopify

  • Offer the customer a new day

    Propose a Twilio message with two slots; the reply is shown to the dispatcher, who approves the reschedule in Onfleet or Route4Me.

    With Twilio, Onfleet

Requirements

  • A route or task system with per-stop windows and completion state: Onfleet or Route4Me
  • Telematics with geofences at the addresses you deliver to, or route stop events: Samsara
  • For order timelines, the Shopify order and fulfillment behind each stop, linked by order id in the task metadata
  • A cutoff time after which a miss becomes a reschedule instead of a same-day re-attempt
Authentication
An Onfleet organization API key or a Route4Me API key, a Samsara API token with vehicle statistics and webhook scopes, a Shopify custom app token with write_fulfillments, a Twilio Account SID and auth token, and a Slack app with chat:write.

Limits

  • A stop with no geofence and no task event cannot be told apart from one that was served; it is listed as unknown
  • Onfleet's taskCreated trigger does not fire for a cloned task; the job listens for taskCloned
  • Shopify tracking events describe the fulfillment; the job does not change the order's fulfillment status itself
  • Route4Me publishes no webhooks; the Activity Feed and address flags are polled

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Missed Stop ↗

Questions and answers

What does the dispatcher see before approving?
The stop, the window it missed, the evidence: task state and failure reason, geofence entry or none, driver position at the window's end. Then the proposal: a cloned task with its new window, a route move, a customer message, or the order tracking event. Each is approved separately.
What does the log hold for a missed stop?
The task or address id, order id, window, the arrival evidence with timestamps, the classification (missed, failed, or unknown), each proposal, the decision, the approver, and the new task or event id created. Unknown stops are kept so a person can resolve them.
Will it create a second delivery attempt by itself?
No. A clone, a route move, a message, or a tracking event exists only after approval. The job proposes once per stop per day; if the original task is later completed, the open proposal is withdrawn.
Ask about Missed Stop

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy