Reference · built on requestOperator by FibricOrders & fulfillment

Missed Delivery

Turns a failed delivery attempt into a redelivery instruction, a hold at a pickup point, or a text to the customer.

Request accessPricing ↗

About

A failed delivery attempt starts a clock; after enough misses the carrier sends the package back. This operator reads attempt scans as they arrive: AfterShip AttemptFail, Shippo delivery_attempted or notice_left, or a UPS or FedEx attempt event. It reads the customer's phone and email from the order and the delivery instructions on file, and checks which options the carrier allows for that package.

It proposes the remedy: a redelivery on a named date, a hold at a nearby UPS Access Point, a FedEx Hold at Location, or a Post Office, or a text asking the customer which they want. A person approves. The order records the attempt, the choice, and the carrier's confirmation.

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

  • AfterShip trackings tagged AttemptFail and their failed_delivery_attempts count
  • Shippo tracking substatus delivery_attempted, notice_left, or pickup_available on the shipment
  • FedEx scan events for delivery attempts and the estimatedDeliveryTimeWindow from the Track API
  • UPS package activity from the Tracking API and nearby UPS Access Point locations from the Locator API
  • The customer's phone, email, and delivery instructions on the Shopify order, and their consent to be texted
  • Inbound replies and delivery status per message from Twilio, so a customer's answer closes the case

Proposed actions

  • Target capability: propose a UPS Delivery Intercept with request type FD (future delivery) or WC (will call) for the package
  • Target capability: propose a FedEx Hold at Location redirect to a named pickup point while the package is still in transit
  • Target capability: propose a Twilio text offering redelivery on a date or pickup at a location, with reply keywords
  • Target capability: propose a help desk note or ticket when the customer answers by another channel
  • Target capability: propose accepting the return to sender and the refund request when the customer does not respond by your deadline

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

What you can build

  • Text after the first miss

    When AfterShip reports AttemptFail, propose a Twilio text with the next attempt date and a keyword to hold the package instead.

    With AfterShip, Twilio

  • Hold at the nearest UPS Access Point

    Find the closest Access Point through the Locator API and propose the will call intercept with the address the customer will see.

    With UPS, Shopify

  • Redirect FedEx to Hold at Location

    When Shippo shows notice_left on a FedEx shipment, propose the Hold at Location redirect and the message naming the store and its hours.

    With Shippo, FedEx

Requirements

  • A tracking source that reports attempt scans: AfterShip, Shippo, or the carrier's own tracking API
  • A UPS account with Delivery Intercept, or FedEx Delivery Manager access, for the carrier-side options
  • A messaging connector with a number the customer recognizes, such as Twilio, and a consent record for texts
  • A store connector for the order's contact details and instructions, such as Shopify
Authentication
Uses the carrier, store, and messaging credentials already granted to the connected listings and adds no account of its own.

Limits

  • Carrier options differ: FedEx holds a package up to 7 days before returning it; UPS quotes intercept charges per request
  • Some shippers' settings stop recipients changing the destination in transit; the operator proposes only what that package allows
  • Texts require the customer's consent under your messaging policy; without it the proposal is an email or a ticket
  • It cannot make a carrier attempt again; it can only file the instruction the carrier offers and tell the customer

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 Delivery ↗

Questions and answers

What does the person approve?
The remedy for one package: a redelivery date, a hold location, or the text that asks the customer to choose. Each shows the attempt scan, the options the carrier allows for that package, and any charge.
What record remains?
The order holds the attempt scan and time, the option proposed, the customer's reply if any, the carrier's confirmation number, the approver, and the delivery or return scan that closed it.
What does it never do on its own?
Send a text, file an intercept or hold, accept a return, or refund. If the customer replies with something it does not recognize, it opens a ticket for a person rather than guessing.
Ask about Missed Delivery

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