Patient recall software selection checks

Private clinic team at work

Patient recall software manages outreach to existing patients whom a clinic has selected for an administrative booking invitation. Choose it by checking how contacts enter a campaign, what stops further outreach, who handles replies and what permits later re-entry. Ask suppliers to demonstrate those controls before importing a live contact list.

The buying decision

The buying decision should rest on demonstrated campaign controls and a written operating specification, not a checklist of messaging features. A supplier should show what happens when a contact enters twice, books through reception, replies after a pause or appears in another campaign. Those are concrete tests of whether the proposed workflow matches the clinic's rules. Start by writing the required behaviour in ordinary language, then ask the supplier to reproduce each situation during a demonstration.

Define the outreach category before discussing features. Recall is an invitation to book, directed to an existing patient group selected by the clinic. An appointment reminder concerns a booking that already exists. Reactivation concerns contacts selected using a clinic-defined period of inactivity. Keep those categories distinct even when one tool manages all three. Where recall dates depend on a clinical decision, authorised clinic staff must supply the dates; the purchasing exercise concerns how the software uses that approved input.

Your purchasing deliverable is a rule document covering entry, exclusions, stopping and restarting, supported by demonstration notes and an itemised quote. For example, specify whether an existing booking excludes a contact from an invitation campaign and who resolves an uncertain match. Give reception and the person responsible for contact records a chance to review the document. Their administrative decisions should be settled before the supplier configures the workflow.

Buy the demonstrated workflow: an entry rule, a stop rule, a reply owner and a restart decision. A feature name such as “automated recall” leaves all four questions open.

Entry and overlap rules

Campaign entry needs a defined source, a selection rule and a stable record identifier. Record whether contacts come from an approved export, a staff action or another demonstrated connection, then specify what qualifies a record for inclusion. Ask which identifier connects a contact to an existing campaign enrolment. A changed phone number should be tested separately from a genuinely new contact, and records without a usable identifier need an explicit exception route.

Test duplicate handling with fictional enquiry identifier R-101. Import R-101, repeat the import, then change its contact number and import it once more. Ask the supplier to show whether the software flags, merges, excludes or separately enrols each version. Next, put R-101 in both a recall group and a reactivation group. The clinic must decide which campaign takes precedence, whether the other campaign is suppressed and where unresolved conflicts appear for staff review.

Use the demonstration matrix below to record decisions rather than award product scores. The expected treatment is a clinic requirement to agree before testing, not a claim about any supplier's software. During the demonstration, add the observed behaviour and supporting evidence to your purchase record. Name an exception owner for each scenario so that an unresolved duplicate doesn't become an unassigned reception task.

Fictional demonstration scenarios for a clinic to adapt.

Supplier demonstration matrix

TriggerClinic-required treatmentSupplier demonstrationException ownerAcceptance decision
R-101 is imported twiceApply the agreed duplicate rule before another enrolmentShow both import results and the resulting campaign membershipContact-record administratorAccept when repeated entry follows the written rule
R-101 enters recall and reactivation groupsApply the clinic's campaign precedence ruleShow the active campaign and any suppressed or flagged enrolmentRecall coordinatorAccept when precedence and exceptions are visible
Reception books R-101 during an active sequenceApply the booking stop rule to pending invitationsShow the booking connection and the queued action's final statusReception leadAccept when the demonstrated timing meets the clinic's requirement
R-101 replies after a pauseCreate a visible reply task without an unauthorised restartShow the reply location, assigned owner and campaign statusAssigned reception ownerAccept when staff can resolve the reply and inspect the pause
R-101 cancels a bookingUse the agreed cancellation and re-entry ruleShow whether approval is requested and which sequence would runAuthorised campaign supervisorAccept when cancellation follows the documented restart decision

Stop and restart controls

Stop controls determine which pending recall actions remain scheduled after a booking, reply, contact-preference change or staff pause. Define a separate response for each event. A booking might stop further invitations, while an unclassified reply might pause outreach until reception reviews it. A request to stop contact needs its own recorded handling route. Ask the supplier to show both the contact's campaign status and the status of individual queued actions.

Run the booking test from reception's actual workflow. In the fictional scenario, R-101 receives an invitation, books through reception and still has another invitation queued. Ask how that booking reaches the recall tool: through the proposed connection, a file transfer or a staff update. Then change the booking while an outreach action is pending. Record any demonstrated synchronisation interval, the point at which a queued action can no longer be stopped and the staff task required when the change arrives too late. A manual booking-status update takes staff time and can be missed at shift change.

Restart decisions need separate tests because cancellation, an expired pause and a repeated import are different triggers. Don't assume that cancelling an appointment should automatically restart invitations. Specify whether each trigger requires staff approval, resumes an existing sequence or creates a new enrolment. Ask which roles can authorise the action and inspect the history afterwards. The history should let the clinic identify the triggering event, the decision and the sequence that became active.

Test the boundary, not just the normal sequence. Change a booking or contact preference while an invitation is pending, then inspect the action history and the reception task.

Replies and event records

Every recall reply needs a visible owner, a status and a recorded next action. Ask the supplier to demonstrate a booking request, a request to pause contact and a question that reception must transfer for staff review. Reception's role is administrative routing, not deciding clinical suitability. Test a reply that arrives after a campaign has stopped, then another through a different supported channel. Staff should be able to locate the reply, identify its campaign context and close or transfer the task using the proposed workflow.

For a clinic serving patients from several countries, demonstrate the exact language and channel combination the clinic intends to use. Delta Fuji handles enquiry calls, WhatsApp follow-up and confirmations in the patient's language, making language handling relevant to the wider front-office purchasing decision. For recall specifically, ask the supplier to demonstrate the proposed coverage rather than infer it from another service. Show how reception receives a reply when staff don't speak that language, where questions are recorded and who takes responsibility for the next response.

Keep outreach attempts, delivery statuses where available, patient replies, bookings and attended visits as separate events. A booking records an appointment; attendance needs its own later status. Inspect timestamps, campaign identifiers and record identifiers so a manager can reconstruct the sequence. If a patient replies after a stop, the log should show both events in order. Request an export demonstration using the fictional records, including how the export represents a pending action, a stopped action and an unresolved reply.

The purchase record

The purchase record should connect every required behaviour to demonstrated evidence, an unresolved question or a named staff workaround. Build a capability matrix with rows for duplicate handling, campaign precedence, stop controls, restart permissions, reply ownership and record export. For each row, record the clinic's requirement, what the supplier showed, any configuration needed and the person approving acceptance. An unanswered question belongs in the record with an owner and a resolution task, not in an informal assumption that the feature will work.

Request an itemised quote against the workflow you actually tested. Include setup, contact migration, users, outreach allowances, channel charges, language coverage, booking connections, support and exports. Ask which items are included, metered or separately charged, and what happens when the quoted allowance is exceeded. Describe the proposed languages and channels explicitly. For example, ask whether the quoted scope covers the demonstrated recall invitation and reply handling, rather than accepting a general reference to multilingual messaging.

Launch with a clinic-approved contact group and an assigned reception owner before extending the rollout. Review the group's exclusions and contact preferences before enrolment, then inspect unexpected entries, unresolved replies and pending actions during the launch. Compare the observed behaviour with the signed-off rule document. Expand only after the clinic has resolved acceptance questions and assigned ongoing ownership of imports, exceptions and campaign changes.

Common questions

What is patient recall software? Patient recall software manages booking invitations to existing patients selected by a clinic. Its administrative workflow covers campaign entry, exclusions, outreach, reply handling, stopping and possible later re-entry. Where selection uses clinically determined recall dates, authorised clinic staff supply those dates.

How does patient recall software differ from appointment reminder software? Patient recall software invites a selected existing patient to book an appointment. Appointment reminder software sends administrative messages about an appointment already booked. A tool may cover both workflows, but the clinic should test their rules separately, especially whether a new booking stops pending recall invitations.

What should stop an automated patient recall sequence? Four events need a stop rule: a booking, a reply, a contact-preference change and a staff pause. For example, a booking can end further invitations, while an unclassified reply can pause outreach until reception reviews it. Test each event, then specify who can authorise a restart and whether a restart resumes the previous sequence or creates a new enrolment.

What should clinics check before importing an existing recall list? An existing recall list needs a confirmed source, an approved selection rule, usable record identifiers and checked contact preferences. Confirm permitted use against applicable requirements, then test repeated imports, changed contact details, existing bookings and overlapping campaigns with fictional records. Assign an owner for records that cannot be matched or enrolled under the agreed rules.

What should a patient recall software quote include? A patient recall software quote should itemise setup, contact migration, users, outreach allowances, channel charges, language coverage, booking connections, support and exports. Ask which charges are included, metered or separate, and how excess usage is billed. Tie the quote to the specific workflow, language combinations and connections demonstrated by the supplier.