Automated Narvar Delayed Shipment Alerts
Every morning, WebRun opens Narvar, checks every active shipment's tracking status against its estimated delivery date, posts the list of delayed shipments to Slack, and escalates anything more than three days late to Telegram so the support team can get ahead of it.
How do I catch delayed shipments before customers start asking?
WebRun checks every active Narvar shipment each morning against its estimated delivery date, posts the delayed ones to Slack grouped by carrier, and escalates anything more than three days late to Telegram. Support teams see a shipping problem before the customer emails about it, with the carrier pattern already visible instead of buried in individual tickets.
- Shipping problems surface before the customer emails support
- Carrier delay patterns are visible in one place
- The worst delays reach the team fast through a second channel
Built for ecommerce support teams · post purchase operations · customer experience teams · logistics coordinators
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
narvar.comin a real browser with your saved login - no setup, no API keys. -
1
Narvar - check shipments against their estimated delivery date
- Open Narvar and list every active tracked shipment
- Compare each one's current carrier status against its estimated delivery date
- Flag any shipment past its estimated date with no delivery scan
Done when Every active shipment has been checked against its estimated delivery date.
-
2
Slack - post the delay list
slack.com
WebRun opens Slack to post the delay list. - Post every delayed shipment with order number and days late
- Group by carrier so patterns are easy to see
- Note the original estimated delivery date
Done when Today's delayed shipments are posted to the support channel.
-
3
Telegram - escalate the worst delays
telegram.org
WebRun opens Telegram to escalate the worst delays. - Check for shipments delayed more than three days
- Post those separately with the order number and carrier
- Flag any carrier showing more than one severe delay
Done when Every severely delayed shipment has been escalated to Telegram.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it contact the customer about the delay?
No. WebRun only alerts your internal team through Slack and Telegram. Any proactive message to the customer is sent by your team, not by WebRun.
How is a shipment marked as delayed?
It compares the carrier status Narvar is already tracking against the estimated delivery date on the order, and flags anything past that date with no delivery scan.
Why do some delays go to Telegram as well as Slack?
Shipments delayed more than three days are the ones most likely to turn into a support ticket or a refund request, so they get a second, faster channel.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.