Automatic Floor Machine Repair Status Updates
Every morning, WebRun opens JanSanix, checks every open floor machine and equipment repair ticket for a status change, drafts a status update text in Twilio for each customer whose ticket moved, and posts the service department a Slack digest of every ticket still open and how long it has been waiting.
How do I keep customers updated on floor machine and equipment repairs without calling each one?
WebRun checks your open floor machine and equipment repair tickets every morning. It reads status changes in JanSanix, drafts a short update text in Twilio for each customer whose ticket moved, and leaves every message queued for the service coordinator to review and send. It also posts a Slack digest of every open ticket with days waiting, so aging repairs never get lost.
- Customers hear about a status change the same morning it happens
- Aging tickets get flagged before a customer has to call and ask
- Service coordinators review a ready to send text instead of writing one from scratch
Built for jan-san distributors with an equipment service department · service coordinators · floor care equipment technicians · customer service reps
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
cloud9erp.comin a real browser with your saved login - no setup, no API keys. -
1
JanSanix (Cloud 9 ERP Solutions) - check open repair tickets for status changes
cloud9erp.com
WebRun opens JanSanix (Cloud 9 ERP Solutions) to check open repair tickets for status changes. - Open JanSanix and pull every open floor machine and equipment repair ticket
- Note any ticket whose status changed since yesterday, such as parts ordered or ready for pickup
- Calculate how long each open ticket has been waiting
Done when Every open repair ticket is checked for a status change and days waiting.
-
2
Twilio - draft the customer status update text
twilio.com
WebRun opens Twilio to draft the customer status update text. - Draft a short status update text for each customer whose ticket status changed
- Leave every message queued, unsent, for the service coordinator to review and send
Done when A drafted status update exists for every ticket that changed status.
-
3
Slack - digest the service department's open tickets
slack.com
WebRun opens Slack to digest the service department's open tickets. - Post the service department a digest of every open ticket with days waiting
- Flag any ticket open longer than your target turnaround
Done when The service team has today's full open ticket digest 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
Will it text customers without anyone reviewing the message first?
No. Every status update is drafted in Twilio and left queued for the service coordinator to review and send. WebRun never texts a customer on its own.
How does it know a ticket's status changed?
It compares each open ticket in JanSanix against the status it saw the day before, so only tickets that actually moved, like parts ordered or ready for pickup, get a drafted update.
What about tickets that have been open a long time?
Any ticket open longer than your target turnaround is flagged separately in the Slack digest, so aging repairs do not get lost among the rest.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.