Reference · built on requestOperator by FibricFleet, routes & field

ETA Notice

Computes a delivery ETA from vehicle position and remaining stops and proposes a customer text or email when it leaves the promised window.

Request accessPricing ↗

About

ETA Notice is an operator job for the customer who was promised a window. It reads the vehicle's position, the stops ahead of a delivery, and the routing platform's own estimate for each. It reads the window the customer was given.

When the estimate for a stop moves outside that window, it drafts a message: the new arrival time, the order it concerns, and a way to reply. It proposes a text through Twilio or an email through Twilio SendGrid, using the customer's contact on the order and wording you approved in advance. A dispatcher approves each message before it goes. Each one is kept with the estimate it was based on and the delivery status the messaging platform reports, so a complaint can be answered from the record.

This is a reference listing. It documents what Fibric would read from ETA Notice 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

  • Vehicle position and speed from the Samsara stats feed or asset location stream, and route stops with scheduledArrivalTime and state
  • Onfleet taskEta, taskDelayed, and predictedTaskDelay triggers, fired against a threshold in seconds you set, plus estimatedArrivalTime on the task
  • Bringg way_point_eta_changed, task_late, and way_point_scheduled_arrival_updated webhooks on an order's waypoint
  • Trimble Maps trip ETAs per stop through GET /trip/{tripId} and GET /trip/routetonextstop, with ETA-change notifications on InProgress trips
  • The promised window on the order: Onfleet completeAfter and completeBefore, or the delivery window on the order record
  • Delivery status of each notice: Twilio Message status queued, sent, delivered, undelivered, or failed, and SendGrid delivered, bounce, and dropped events

Proposed actions

  • Target capability: propose an SMS through Twilio's Messages resource with the new arrival time, from a number or Messaging Service you own
  • Target capability: propose an email through SendGrid POST /v3/mail/send with a dynamic template and the order reference in custom_args
  • Target capability: propose an updated window on the order in the delivery platform, so the driver app and the customer notice agree
  • Target capability: propose a dispatcher note when the estimate misses the window by more than the route can recover
  • Target capability: propose an end-of-day list of stops delivered outside their window with the notices sent for each

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

What you can build

  • Text a customer when an Onfleet task is predicted late

    predictedTaskDelay fires past your threshold. The operator drafts a Twilio SMS with the task's estimatedArrivalTime and the order number, for the dispatcher to approve.

    With Onfleet, Twilio

  • Email a new window from a Bringg ETA change

    way_point_eta_changed moves the estimate past the window. The operator proposes a SendGrid dynamic-template email with the new time and the order reference in custom_args.

    With Bringg, Twilio SendGrid

  • Notify from Samsara position and stop times

    Position and the stops still scheduled give an estimate for each delivery. When it leaves the window on the order, a text is proposed and its delivery status is read back from Twilio.

    With Samsara, Twilio

  • Use Trimble Maps ETAs on long-haul trips

    ETA-change notifications on an InProgress trip update the estimate per stop. A consignee whose window is missed is proposed an email before the truck arrives.

    With Trimble Maps, Twilio SendGrid

Requirements

  • A routing or delivery connector with an ETA per stop: Samsara, Onfleet, Bringg, or Trimble Maps
  • The promised window on each order, in the delivery platform or the order system it came from
  • A Twilio account with a sending number or Messaging Service, or a SendGrid account with a dynamic template
  • Customer consent to be contacted by text where the law requires it, held on the order or the customer record
Authentication
Positions, routes, and windows are read through the connectors you bind; messages are proposed through your Twilio or SendGrid account under its own key. The operator sends nothing itself.

Limits

  • The ETA is the routing platform's estimate. Where a platform gives none, the operator uses remaining drive time and says so in the record
  • SMS bodies over 160 GSM-7 characters are split into segments and billed by Twilio as several messages
  • A customer with no phone or email on the order gets no notice; the stop is listed for the dispatcher instead
  • It notifies about time. It does not change the delivery date, cancel a stop, or offer a refund

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 ETA Notice ↗

Questions and answers

What does the dispatcher approve?
A message to one customer: the order, the window promised, the estimate now, the text or email as it will be sent, and the contact it goes to. The dispatcher sends it, edits it, or holds it. Nothing is sent without that.
What record is left?
The position and ETA read with their times, the window on the order, the message as sent, the approval with name and time, and the delivery status Twilio or SendGrid reported for it.
Will it text or email a customer without approval?
No. Each notice is proposed to a person first. The operator can list stops likely to miss their window, but it sends no text or email on its own.
Ask about ETA Notice

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