Skip to main content
GullySystem
Healthcare

Service Reminders for Online pharmacies

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.

Refill dates are worked out from the quantity supplied and the dose on the prescription. A customer on a monthly tablet gets a message before the strip runs out. Repeat orders start from that message.

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.
Online pharmacies

How the business operates.

An online pharmacy has no counter. The prescription arrives as a photo, the pharmacist checks it on a screen, and the medicine leaves in a parcel the patient never sees being packed.

Order queue from every channel

Collect website, app and marketplace baskets into one list with payment status, address and the lines that need a prescription, so staff can spot a duplicate or fraud attempt.

Prescription check by line

Hold the image beside the order and record the pharmacist’s name, time and decision on each medicine, with any substitution approved and any narcotic or opioid line marked.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Storefront and marketplace orders. Collect baskets from your website, app and marketplace listings into one order queue, with payment status, delivery address and a flag on every line that needs a prescription.
  • Prescription upload and verification. Hold each prescription image against its order, and let the pharmacist mark every line accepted, queried or rejected with a name, a time and a typed reason.
  • Restricted item rules. Mark medicines that need a valid prescription, a quantity cap, a cold-storage flag or a no-post rule, so the basket is stopped before payment is taken.
  • Substitution and generic matching. Offer an equivalent generic pack when a brand is out of stock, and record the pharmacist’s approval and the patient’s consent before the substitute reaches the pick list.

Operational bottlenecks to check

Prescription and order live in different tools

The image arrives through chat or upload while the order sits in the storefront, so proving which pharmacist approved which opioid or antibiotic line means searching two places.

Recall notices cannot be answered quickly

A batch is withdrawn. Without a scan at packing, nobody can list every parcel and every patient that received it, so the search is done by hand.

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. Order intake

    A basket arrives from the website, app or marketplace, payment status is recorded, and any line that needs a prescription is flagged on arrival. Nothing skips the queue.

  2. 2. Prescription check

    The pharmacist opens the uploaded image beside the order, accepts, queries or rejects each line, and records any approved substitution together with the patient’s consent.

  3. 3. Picking and batch capture

    Packers receive a pick list sorted by shelf, scan the lot and expiry of each pack, and the system stops any line that is near expiry or blocked.

  4. 4. Packing and dispatch

    The parcel is weighed, labelled and handed to a courier against a manifest, and cold-chain boxes carry a packed-at time with the tracking number sent to the patient. The cold clock starts here.

  5. 5. Delivery, returns and complaints

    Courier status updates the order, and a returned parcel goes to a holding bin where the pharmacist inspects the seal and decides to restock, destroy or return it. Every outcome carries a reason.

  6. 6. Refill and reorder

    From the days supplied on each line a refill date is set, the patient receives a reminder by SMS or messaging app, and one tap repeats the last order.

Industry reports to connect with

  • Orders waiting for pharmacist review, by age
  • Lines rejected or queried, with reason
  • Batches dispatched, by patient and parcel
  • Cold-chain parcels and courier delay

Questions before implementation.

When should online pharmacies 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