TSTracker Automated Engineering Change Alerts
Every hour, WebRun checks TSTracker for newly logged engineering changes, drafts a short acknowledgment email to the customer in Gmail confirming the change was received, leaves it unsent for the account manager to review, and alerts your tooling team in Slack so the change gets scoped before it holds up the build.
How do I get notified the moment an engineering change is logged against a tool?
WebRun checks TSTracker every hour for newly logged engineering changes. It drafts a short acknowledgment email to the customer in Gmail, left unsent for the account manager to review and send, and posts a Slack alert to the tooling team flagging changes on tools already in build, so nothing slips through before it affects the ship date.
- Every engineering change reaches the tooling team within the hour
- Changes on tools already in build get flagged as higher risk
- Customer acknowledgments are ready to send, not written from scratch
Built for tool and die shops · tooling engineers · mold shop account managers · die shop project managers
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
tst-software.comin a real browser with your saved login - no setup, no API keys. -
1
TSTracker - find newly logged engineering changes
tst-software.com
WebRun opens TSTracker to find newly logged engineering changes. - Open TSTracker and check the Engineering Change log for entries added since the last run
- Capture the tool number, customer, requested change, and the engineer who logged it
- Note which stage the affected tool is currently in, since a change mid build carries more risk
Done when Every new engineering change is listed with the tool, customer, and requested detail.
-
2
Gmail - draft a customer acknowledgment
gmail.com
WebRun opens Gmail to draft a customer acknowledgment. - Draft a short acknowledgment email to the customer contact confirming the change request was received
- Reference the specific tool and the change requested so the customer knows it was read correctly
- Leave the email as an unsent Gmail draft for the account manager to review and send
Done when An unsent Gmail acknowledgment draft exists for every new engineering change.
-
3
Slack - alert the tooling team
slack.com
WebRun opens Slack to alert the tooling team. - Post an alert to the tooling channel for every new engineering change
- Flag any change affecting a tool already in Machining, Assembly, or Tryout as higher risk
- Tag the assigned tooling engineer so scoping starts the same day
Done when The tooling team has seen every new engineering change and its build risk.
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 email the customer without approval?
No. Every acknowledgment is saved as an unsent Gmail draft. WebRun writes and readies the reply, but your account manager decides whether and when it actually goes to the customer.
How does it decide a change is higher risk?
It reads the affected tool's current build stage in TSTracker. A change requested while a tool is already in Machining, Assembly, or Tryout gets flagged so it gets scoped before it holds up the build.
Will it miss a change logged outside business hours?
No. It checks TSTracker every hour, so a change logged overnight or over a weekend is caught and alerted at the next scheduled run.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.