Automated Silo Trace-Back Recall Alerts
The moment a lot is flagged for trace-back in Silo, WebRun compiles its full one-up-one-down chain from grower or supplier through every shipment, texts your QA lead through Twilio, posts an immediate Slack alert to the recall channel with the affected customer list, and drafts a customer trace-back notice for your recall team to review before sending.
How do I get an immediate alert and identify every affected shipment when a produce lot is flagged for recall?
The moment a lot is flagged for trace-back in Silo, WebRun compiles its full one-up-one-down chain and identifies every affected customer and shipment. It texts your QA lead through Twilio and posts an immediate Slack alert to the recall channel, then drafts a customer trace-back notice and leaves it unsent for your recall team to review before anything goes out.
- Every affected shipment is identified within minutes of a flag, not hours
- QA lead is texted immediately so the recall clock starts right away
- A customer notice is already drafted and waiting when your recall team is ready to send it
Built for fresh-cut produce processors · food-safety and QA leads · produce packers and shippers · recall response 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
usesilo.comin a real browser with your saved login - no setup, no API keys. -
1
Silo - compile the affected lot's full trace chain
- Open Silo the moment a lot is flagged for trace-back or hold pending investigation
- Compile the full one-up-one-down chain: source lot or grower, every case or repack created from it, and every order it shipped on
- Capture the affected customer, ship date, and quantity for each shipment
Done when The flagged lot's complete trace chain and every affected customer are identified.
-
2
Twilio - text the QA lead immediately
twilio.com
WebRun opens Twilio to text the QA lead immediately. - Send an immediate SMS to your QA lead naming the flagged lot and the number of affected shipments
- Include a link to the full trace chain in Silo
Done when Your QA lead has been texted within minutes of the flag.
-
3
Slack - alert the recall channel with affected customers
slack.com
WebRun opens Slack to alert the recall channel with affected customers. - Post an alert to the recall channel with the lot, trace chain summary, and affected customer list
- Draft a customer trace-back notice for the recall team, and leave it unsent for review. Never notify a customer or regulator automatically
- Pin the alert until the recall team marks the investigation closed
Done when Your recall team has the affected customer list in Slack and a reviewable notice draft, with nothing sent externally yet.
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 or regulators on its own?
No. WebRun only alerts your internal QA and recall team by SMS and Slack. Any customer or regulator notice is drafted and left unsent for your recall team to review, approve, and issue.
How fast does the alert go out after a lot is flagged?
Within a few minutes. WebRun checks for a new trace-back flag continuously, so your QA lead is texted and the recall channel is posted almost as soon as the flag is set in Silo.
How does it find every affected shipment?
It follows the one-up-one-down chain recorded in Silo from the source lot through every case and order it touched, so no affected shipment is missed because it was repacked or relabeled.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.