Skip to main content
GullySystem
Healthcare

Service Reminders for Audiology clinics

Track due service events and their follow-up messages.

Field Service

Does this function belong in your operation?

Use when repeat services or renewals depend on dates or recorded usage.

A service date, usage threshold or contract obligation approaches.

Patients due for a yearly retest or near the end of a warranty are listed so the desk can contact them.

Bring the records the workflow depends on.

  • Due-date rules
  • Customer and asset references
  • Contact permissions

Outputs to check

  • Due-service action list
  • Reminder and response history
  • Booking or deferral outcome

Follow the service reminders workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define the due event

    Record the service date, usage trigger or contract obligation.

  2. 2. Check current status

    Exclude completed or retired items and verify contact permissions.

  3. 3. Prepare the follow-up

    Create the approved message or staff action.

  4. 4. Record the response

    Capture booking, deferral or an unresolved request.

  5. 5. Update from evidence

    Reset the due event only after the relevant service or renewal is confirmed.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Service advisor

Works the day’s reminders between vehicles and books what can be booked.

Receptionist

Reviews permitted follow-up messages, records customer responses and creates booking handoffs where requested.

Owner

Compares due services with completed visits and reviews unresolved follow-up outcomes.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Contact permission absent

Leave the communication unsent and route the permitted follow-up method.

Customer postpones

Record the agreed next action without falsely marking the service complete.

Asset no longer in use

Review the trigger with its owner before removing future reminders.

Can this work independently?

Reminders require a reliable due date or usage trigger. Job cards, contracts or customer records can supply it; booking systems record the resulting appointment. Messaging needs an authorised channel. A sent reminder does not reset the service due date or prove the service occurred.

Systems and records it connects with

  • Job cards: Service findings, approved work, parts and completion records.
  • AMC contracts: Contract coverage, dates and planned service obligations.
  • Appointment scheduling: Confirmed slots, cancellations and attendance outcomes.
  • WhatsApp and SMS: Permitted message content and channel delivery responses.

Configure, test and introduce the workflow.

  • List recurring jobs. Tell us which bring a customer back and after what gap, and reminder types come back to confirm.
  • You draft or approve wording per type. Message templates arrive for staff to use. Existing job cards or sheets supply the dates. A trial import shows today’s list.
  • The service advisor works the list for a while. Replies are recorded and wording is adjusted.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Reminders use the current due date.
  • Completed events do not keep triggering.
  • Failed messages remain visible.
Audiology clinics

How the business operates.

Hearing clinics of every size keep tests, devices and aftercare in GullySystem, configured around their own booths and catalogue. Audiologists, dispensers and reception all open the same patient file. Each record carries history, audiograms, devices with serial numbers and warranties, trial dates, repairs and balances. Recalls for retests and warranty checks are listed for the desk.

Appointments by audiologist and booth

Book tests, fittings, fitting adjustments and follow-ups by audiologist and sound booth, with reminders to the patient by text. Cancelled slots return to the diary for the next booking.

Patient history and referrals

Keep case history, symptoms, referral source from a family doctor or ear, nose and throat clinic, and notes on one dated record, so each visit starts from what was found before.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Appointments by audiologist and booth. Book tests, fittings, fitting adjustments and follow-ups by audiologist and sound booth, with reminders to the patient by text. Cancelled slots return to the diary for the next booking.
  • Patient history and referrals. Keep case history, symptoms, referral source from a family doctor or ear, nose and throat clinic, and notes on one dated record, so each visit starts from what was found before.
  • Audiograms and test files. Attach audiogram, tympanometry and speech-in-noise files exported from your audiometer software to the date of each test, and compare the latest result with the earlier curves at a glance.
  • Device and serial register. Record each device with model, side, serial number, fitting date and warranty end, and see every hearing aid a patient has owned. Receivers, domes and chargers are listed under it.

Operational bottlenecks to check

Test results are held apart

Audiograms stay inside the audiometer software on a single PC, while case history is on a card and the device sold is in a sales book. Nobody sees the whole patient.

Device and serial details are untraced

A repair or warranty claim needs the model, the serial number of the receiver and the fitting date. Staff search through paper invoices and manufacturer emails to find them.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Booking

    Bookings come in by phone, through the website or from a referring family doctor or ear, nose and throat specialist. The visit is placed with an audiologist and a booth, and the referral letter is attached.

  2. 2. Assessment

    The audiologist records history and symptoms such as tinnitus or fullness, runs otoscopy and pure tone tests, and saves the audiogram to the record. Tympanometry results go in beside it.

  3. 3. Advice and quotation

    If a device is advised, the patient receives a quotation for a model and accessories and pays a deposit. Receiver-in-canal, behind-the-ear and in-the-ear styles are priced from your catalogue.

  4. 4. Ordering and fitting

    The device is ordered, programmed and fitted. Side, model and serial number are recorded with the warranty date, and real-ear measurement readings are saved so later adjustments start from them.

  5. 5. Trial and adjustment

    A follow-up is set. Settings changed at each visit, such as gain or a new program, are noted, and the patient decides whether to keep the device or return it within the trial.

  6. 6. Aftercare and recall

    Repairs, ear moulds, wax guards and batteries are handled from the record. Yearly retests and warranty checks are listed for the desk, with the patient’s preferred reminder channel shown.

Industry reports to connect with

  • Devices sold by manufacturer, model and period
  • Loan trials open and ending this week
  • Repairs out with manufacturers and overdue
  • Warranties ending in the next quarter

Questions before implementation.

When should audiology clinics consider service reminders?

Use when repeat services or renewals depend on dates or recorded usage. A service date, usage threshold or contract obligation approaches.

What should we bring to the requirements discussion?

Bring anonymised examples of Due-date rules; Customer and asset references; Contact permissions. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Track due service events and their follow-up messages. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Regulated health or safety decisions must be made by qualified people rather than reminder rules.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Reminders use the current due date. Use this check when reviewing the first working version.

Talk to us

Discuss service reminders for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements