Reference · built on requestOperator by FibricOrders & fulfillment

WISMO Deflection

Answers where-is-my-order contacts from the shipment's latest scan, with a revised arrival date, for an agent to approve.

Request accessPricing ↗

About

A where-is-my-order contact is a question the carrier has usually already answered. This operator reads new tickets or conversations in your help desk, matches each to the order and its fulfillment, and pulls the shipment's latest scan, delivery status, and estimated delivery date from the carrier or tracking service. It drafts a reply in your voice: where the package is, what the carrier expects, and when to check back.

The agent sees the draft beside the scan history and approves, edits, or discards it. A ticket with no tracking number, a shipment with no scan, or a status of exception or expired goes to a person with an internal note rather than a reply. Every reply keeps the ticket id, the scan it quoted, and who approved it.

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

  • New tickets and conversations in Gorgias, Kustomer, or Zendesk whose text asks about an order's whereabouts, with the customer's email and order number
  • Fulfillments on the Shopify order, including trackingInfo (company, number, URL), displayStatus, and estimatedDeliveryAt
  • The latest checkpoint, delivery status tag, and estimated delivery date for the tracking number in AfterShip
  • USPS scan events with date, time, and location from Tracking 3.2 for domestic packages
  • FedEx delayDetail status and the estimatedDeliveryTimeWindow from the Track API
  • Earlier replies on the same ticket, so a customer who already heard from you is not sent the same answer

Proposed actions

  • Target capability: propose a public reply on the ticket with the latest scan, the carrier's expected delivery date, and the tracking link
  • Target capability: propose an internal note when the shipment has no scan, an exception, or an expired tracking, so a person takes it
  • Target capability: propose tagging the ticket wismo and setting its status once the approved reply is sent
  • Target capability: propose a second message when the carrier revises the delivery date after the first reply

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

What you can build

  • Answer the first-contact WISMO from the scan

    Match the Gorgias ticket to the Shopify order, read the AfterShip checkpoint, and put a drafted reply in front of the agent with the scan and date it quotes.

    With Gorgias, Shopify, AfterShip

  • Keep USPS questions off the phone queue

    For domestic parcels, quote the latest USPS scan event and location in the reply, and hand the ticket to a person when the tracking shows no movement.

    With USPS, Kustomer

  • Warn about a FedEx delay before the customer asks twice

    When the Track API reports a DELAYED status with a reason, propose a follow-up on the open Zendesk ticket with the new window.

    With FedEx, Zendesk

Requirements

  • A help desk connector with ticket read and message write access: Gorgias, Kustomer, or Zendesk
  • A store connector that exposes each order's fulfillments and tracking numbers, such as Shopify
  • A tracking source for the carriers you ship with: AfterShip, USPS Tracking 3.2, or the FedEx Track API
  • A reply template per language and a rule for how far a revised date may slip before an agent must speak first
Authentication
Runs under the API credentials of the help desk, store, and tracking connectors it is built on; it holds no login of its own.

Limits

  • A ticket without an order number or a matching email is left to the agent; the operator does not guess the order
  • It reports what the carrier reports. A stale scan produces a reply that says the scan is stale, not an invented location
  • Replies go out only after approval. It never closes a ticket or promises a concession on its own
  • Estimated delivery dates come from the carrier or tracking service and change; the reply quotes the date and its source

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 WISMO Deflection ↗

Questions and answers

What does the agent approve?
A drafted public reply that quotes one scan, one delivery status, and one estimated date, each with its source. The agent can edit the text, send it as written, or discard it. Nothing reaches the customer until that choice is made.
What record is left after a reply goes out?
The ticket keeps the sent message. Beside it, the operator records the tracking number, the scan and date it quoted, the time the carrier reported them, and the person who approved. If the date was later revised, the follow-up proposal links back to the first reply.
What will it never do on its own?
Send a message, close a ticket, change an order, or offer a refund or credit. When the tracking shows an exception, a failed attempt, or no scan at all, it writes an internal note and stops.
Ask about WISMO Deflection

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