Automated Daily Repair Ticket Digest
Every morning, WebRun opens RepairDesk, counts and categorises all open tickets by status, flags any that are overdue or awaiting parts, and posts a structured daily digest to your Slack channel so the team starts the day with full visibility.
How do I get a daily summary of all open repair tickets sent to my team?
Every morning before the shop opens, WebRun reads all open RepairDesk tickets, groups them by status, flags overdue jobs and any with no recent activity, and posts a structured digest to your Slack team channel. The whole team starts the day with a shared, accurate picture of the repair queue.
- Every technician starts the day knowing exactly what is on the bench without checking the system
- Overdue tickets are surfaced immediately so no job is forgotten
- Managers get a daily count to spot queue build-up before it becomes a problem
Built for phone repair shops · computer repair shops · repair shop managers · multi-technician repair 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.repairdesk.coin a real browser with your saved login - no setup, no API keys. -
1
RepairDesk - read and categorise all open tickets
repairdesk.co
WebRun opens RepairDesk to read and categorise all open tickets. - Open RepairDesk and load all tickets not in Closed or Collected status
- Group tickets by status: In Progress, Awaiting Parts, Awaiting Customer Approval, Ready for Pickup
- Flag any ticket that has passed its promised completion date as overdue
- Note tickets where no update has been logged in the last 48 hours
Done when All open tickets are counted, categorised by status, and overdue items are flagged.
-
2
Slack - post daily ticket digest to team channel
slack.com
WebRun opens Slack to post daily ticket digest to team channel. - Post a structured digest to the team channel with a count per status group
- List overdue tickets by name and days overdue so they get immediate attention
- Highlight tickets waiting on parts that arrived since yesterday
- Include a total open ticket count and a brief note on any unusually long queue
Done when The team has a Slack digest covering every open ticket before the shop opens.
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 this send anything to customers?
No. The daily digest is entirely internal and posts only to your team Slack channel. No customer is contacted at any point.
Can it include tickets from multiple technicians or locations?
Yes. WebRun reads all open tickets in your RepairDesk account. If you want to split the digest by technician or location, tell WebRun and it will group the output accordingly.
What counts as overdue?
A ticket is flagged as overdue when its promised completion date has passed. If a ticket has no due date set, WebRun flags it after a configurable number of days since it was opened.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.