Automated Branch Transfer Request Tracking
Every morning, WebRun opens Savance Enterprise (Klipboard), finds branch transfer requests still unfulfilled past your set SLA, logs the requesting branch, item, and days overdue to a tracking sheet, and posts each branch a Slack follow up list of what it still owes.
How do I chase overdue inter branch stock transfer requests automatically?
WebRun checks Savance Enterprise (Klipboard) every morning for branch transfer requests still unfulfilled past your SLA, logs the requesting branch, item, quantity, and days overdue to a tracking sheet, and posts each source branch a Slack follow up list with the oldest requests first. Managers get tagged automatically once a request passes 5 business days.
- Overdue transfers surface every morning instead of at month end
- Each branch gets its own follow up list instead of one long report
- Requests over 5 business days automatically tag the branch manager
Built for multi branch HVAC distributors · warehouse managers · branch operations teams · inventory 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
klipboard.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Savance Enterprise (Klipboard) - find transfer requests past SLA
klipboard.com
WebRun opens Savance Enterprise (Klipboard) to find transfer requests past SLA. - Open Savance Enterprise (Klipboard) and filter Branch Transfer Requests to Open
- Capture the requesting branch, source branch, item, quantity, and request date for each
- Flag any request older than your set SLA, typically 2 business days
Done when Every open transfer request past SLA is captured with its details.
-
2
Google Sheets - log each overdue transfer
google.com
WebRun opens Google Sheets to log each overdue transfer. - Add or update a row for each overdue transfer with days overdue
- Sort the log so the oldest and highest quantity requests sit at the top
Done when Every overdue transfer is logged with a current days overdue count.
-
3
Slack - post the branch follow up list
slack.com
WebRun opens Slack to post the branch follow up list. - Post each source branch a list of what it still owes, oldest first
- Tag the branch manager on any request over 5 business days old
Done when Every branch with an overdue transfer has this morning's follow up list in Slack.
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 move stock between branches itself?
No. It only finds and lists transfer requests that are overdue. A branch still has to pick, pack, and ship the transfer itself.
How is a request marked overdue?
Any open transfer request older than the SLA you set, typically 2 business days, gets flagged and logged with its exact days overdue.
What if a branch already shipped the transfer?
It reads the live status in Klipboard each morning, so any transfer already marked shipped drops off the list automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.