Auditdata Automated Repair Status Updates
Every morning, WebRun opens Auditdata Manage, reviews open hearing aid repairs, drafts a status update text in Twilio for patients whose device has returned or whose repair is running late, and tracks the full repair pipeline in Google Sheets so no repair goes quiet or overdue.
How do I keep hearing aid repair patients updated on their device status?
WebRun reviews open hearing aid repairs in Auditdata Manage every morning and finds devices that have returned or are running past their expected date. It drafts a status update text in Twilio for each patient and tracks the full pipeline in Google Sheets, so staff approve every message and no repair goes quiet or overdue.
- Patients hear the moment their repaired device is ready to collect
- Every status text is reviewed by staff before it is sent
- Overdue repairs surface daily so none sit forgotten with the lab
Built for hearing aid clinics · audiology practices · front desk teams · repair 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
www.auditdata.comin a real browser with your saved login - no setup, no API keys. -
1
Auditdata Manage - review open repair tickets
WebRun opens Auditdata Manage to review open repair tickets. - Open Auditdata Manage and review open hearing aid repair tickets across locations
- Read each repair's device, patient initials, sent date, expected return, and current status
- Find repairs that have returned to the clinic and repairs now past their expected date
- Capture the patient contact, device, and status for each of these repairs
Done when Every returned or overdue repair is listed with its patient and current status.
-
2
Twilio - draft the status update text
WebRun opens Twilio to draft the status update text. - Draft a status update text for each patient whose repair returned or is delayed
- For returned devices, invite the patient to collect or book a refit visit
- Queue every message in Twilio but leave it unsent for staff to approve
- Never text a patient automatically. A staff member releases each update
Done when A status text is drafted and queued for staff approval for every returned or delayed repair.
-
3
Google Sheets - track the repair pipeline
WebRun opens Google Sheets to track the repair pipeline. - Open the Repair Pipeline Tracker sheet
- Add or update a row per repair with device, sent date, expected return, and status
- Flag repairs past their expected return date as overdue
- Sort so returned and overdue repairs sit at the top for staff to action
Done when The repair tracker is current with overdue and returned repairs flagged at the top.
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 repair patients without approval?
No. WebRun drafts each status update in Twilio and leaves it queued. A staff member reviews and releases every message, so no patient is contacted until a human approves the update.
How does it know a repair is back or overdue?
It reads each repair's status and expected return date in Auditdata Manage, flagging devices marked as returned and any repair that has passed its expected return date.
Can it stop chasing a repair once the patient collects?
Yes. It reads live repair status in Auditdata Manage each morning, so once a device is collected or the ticket is closed, that repair drops off the update list.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.