Automated Ocean Freight Delay Exception Alerts
Around the clock, WebRun monitors Terminal49 for any container that develops a delay exception: a revised ETA more than 24 hours later than the prior ETA, a missed transshipment, a customs or port hold, or a vessel blanked sailing. It posts an immediate alert to Slack with the container, the exception type, and the impact on the expected delivery date.
How do I get instant alerts when an ocean freight container has a delay or exception?
WebRun monitors Terminal49 around the clock for containers that develop a delay or exception: an ETA slippage of more than 24 hours, a new customs or port hold, a missed transshipment, or a blanked sailing. It posts an immediate alert to your Slack ops channel with the exception type, container details, and delay impact so your team can respond within minutes.
- Delay exceptions are visible in Slack within minutes of Terminal49 updating, not hours later
- Your team can notify customers and adjust warehouse or production plans before the delay compounds
- Customs holds are flagged immediately so clearance action starts as soon as the hold is imposed
Built for ocean freight importers · logistics operations managers · freight forwarders · supply chain teams
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
app.terminal49.comin a real browser with your saved login - no setup, no API keys. -
1
Terminal49 - detect delay exceptions and ETA changes on active containers
terminal49.com
WebRun opens Terminal49 to detect delay exceptions and ETA changes on active containers. - Poll Terminal49 every few minutes for changes on active in-transit containers
- Flag any container whose ETA has moved later by more than 24 hours since the prior check
- Flag any container with a new customs hold, CBP, USDA, or port hold not present in the prior check
- Flag any container with a missed transshipment or blanked vessel sailing
- Capture container number, B/L, carrier, prior ETA, new ETA, exception type, and days of delay impact
Done when Every newly developed exception or ETA slippage since the last check is captured with its impact details.
-
2
Slack - post immediate exception alert to the ops channel
slack.com
WebRun opens Slack to post immediate exception alert to the ops channel. - Post an exception alert to the freight operations Slack channel for each new exception
- Lead with the exception type and severity: critical for customs holds, high for ETA slippage over 5 days, standard for shorter delays
- Include the container number, carrier, prior ETA, new ETA, days of delay, and a link to the shipment in Terminal49
- Batch alerts from the same polling cycle into a single digest when multiple containers are affected
Done when The ops channel has an alert for every newly developed exception with severity, delay impact, and shipment details.
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
Will it notify customers automatically when a delay is detected?
No. WebRun only posts internal alerts to your Slack ops channel. Any customer communication about a delay is handled by your team after reviewing the alert, so you control the message and timing.
What counts as a delay exception worthy of an alert?
An ETA that moves later by more than 24 hours, a new customs or port hold, a missed transshipment, or a blanked sailing. You can adjust the ETA threshold when you set up the automation.
What if the ETA improves and comes back earlier?
ETA improvements are also captured and posted as a positive update in Slack, so your team knows when a delayed shipment is recovering and can adjust plans accordingly.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.