Practical guide
A complete recall operations playbook
Start with the purpose of the recall workflow
A recall workflow helps a practice identify appropriate follow-up work, communicate through its approved channels and understand what happened afterward. It is an operating process around the practice’s decisions. It should not be used to invent a clinical interval, assume that every patient needs the same visit or treat a message being sent as evidence that care has been completed.
Begin by asking what the practice wants to coordinate. The answer might concern patients whom the clinical team has identified for a particular follow-up, people who have an existing recall record or another appropriately defined group. The relevant clinician and practice representatives should establish the clinical and communication requirements. The software evaluation then focuses on how that decision is represented, reviewed and acted on.
Jelo’s patient CRM, scheduling and recall workflows support this coordination. Messaging depends on the practice’s provisioned setup, registration, consent and enabled configuration. Before describing a campaign as ready, confirm both the eligible group and the sending arrangement. A well-written message cannot compensate for an unclear cohort or an unowned reply queue.
Define who belongs in the cohort
A cohort is the group included in a particular review or outreach process. Write its definition before counting or contacting people. Identify the office, relevant date or period, the practice-approved follow-up reason and any other criterion your team actually uses. The definition should be specific enough that another authorized employee can understand why a record was included.
Also define exclusions. A patient may already have the relevant appointment, may require a different review or may have a communication preference that affects the intended channel. Use the supported records and your approved procedure to make those decisions. Do not assume that everyone with an old appointment date should receive the same message. The relevant clinical and operational context matters.
Preserve the definition when comparing results later. If one month’s cohort includes one office and the next month includes every office, a difference in volume may reflect the changed scope. If the practice changes eligibility rules, document the change and treat the new group accordingly. A consistent definition is more useful than a large count whose membership nobody can explain.
Keep clinical decisions with the clinical team
The timing and purpose of clinical follow-up depend on the individual situation and the appropriate professional judgment. This guide does not recommend a universal examination interval or decide which condition requires a visit. The recall workflow should represent decisions made through the practice’s clinical process, with enough context for staff to understand the administrative next step.
Administrative staff need clear instructions about what they can communicate and which questions require escalation. A patient may ask whether a particular visit is necessary or describe information that requires clinical review. The front desk should have an approved route for that question rather than supplying an answer based only on a recall label or a marketing script.
During evaluation, use a fictional example to show the handoff between the clinical decision and the administrative follow-up. Ask how the appropriate staff member finds the relevant instruction and knows what action to take. Confirm the supported workflow and record any manual step. A recall feature should help staff coordinate the decision, while preserving responsibility for the decision itself.
Review contact information and communication preferences
A contact attempt relies on the information and permissions the practice has recorded. Before sending, review the intended channel, relevant preferences and any unresolved issue that affects communication. The fact that a person once supplied a phone number does not answer every question about the messages the practice may send. Use the approved consent and messaging process for the actual purpose.
Jelo’s published messaging terms identify Sinch as the provider for SMS and MMS delivery. Sending depends on the practice’s provisioned number, registration, consent and enabled configuration. Confirm those prerequisites during setup. A recall plan that assumes a channel is available before the account is ready can create a gap between the planned activity and the work staff can actually perform.
Decide who maintains contact information when a patient reports a change. Staff should verify the correct record and use the supported update workflow. Keep uncertainty visible rather than repeatedly sending through a contact detail known to be questionable. This is an operating recommendation; it is not a claim that Jelo automatically validates every phone number or resolves every conflicting contact record.
Write a message with one understandable next step
A useful recall message makes its purpose clear and gives the recipient an appropriate next step. Use language approved for the practice’s intended communication. Avoid combining several unrelated requests into one message. The patient should be able to understand whether they are being asked to contact the office, review available scheduling options or follow another specific instruction.
Keep sensitive details out of routine examples and public demonstrations. The actual content should be reviewed under the practice’s communication policies and applicable requirements. This guide does not provide a universal message that is suitable for every clinical reason or patient situation. A short, clear administrative message can still require the right context and consent before it is used.
Test the message as a patient would encounter it. Review the wording on a phone, check any link and confirm that the destination matches the intended office and purpose. Ask a staff member who did not write it to explain what they would do next. If the answer is unclear, revise the message before expanding the outreach. A usable next step matters more than adding promotional language.
Prepare the receiving team before sending
Outreach creates incoming work. Patients may reply with questions, request a different time or need help finding the right appointment. Identify the person or team responsible for those responses before the message is sent. A campaign can produce activity without producing a useful outcome if nobody owns the next conversation.
Review the scheduling information the receiving team will need. Staff should know which office and appointment context apply and how to route a clinical question. If the practice has limited availability for the intended visits, discuss the operating plan before encouraging a large group to respond at once. This guide does not prescribe a particular capacity model; it recommends aligning outreach with the team’s actual ability to handle the result.
For a fictional rehearsal, have one person act as a patient who replies with an ordinary scheduling question. Ask the receiving employee to locate the relevant context and explain the next step. Include a question that needs another role’s review. The rehearsal tests the handoff and makes an unowned responsibility visible before real patients encounter it.
Separate an attempt, a delivery result and a response
A contact attempt records an action by the practice. A delivery result describes what the communication system reports. A response describes something the patient sent back. These are different events and should be counted separately when the practice reviews recall activity. A message being sent does not establish that the recipient read it, and a reply does not necessarily mean an appointment was scheduled.
Define the events your team will use in its operating record. For example, an outreach review may distinguish attempted contact, an unresolved sending issue, patient response and a scheduling action. The exact available statuses depend on the supported workflow and configuration. Ask the implementation team to demonstrate the records you intend to rely on rather than assuming every channel provides identical information.
Keep the next action tied to the event. An unresolved delivery issue may need contact information review. A scheduling question needs a staff response. A clinical question needs the appropriate professional. Treating all three as a generic “recall not completed” category can hide the person who can actually advance the work.
Distinguish a booking from a completed visit
A scheduled appointment and a completed appointment represent different stages. If the practice wants to understand recall follow-through, it should decide which stage it is measuring and over what observation window. Counting bookings can help evaluate the scheduling handoff, while completed visits answer a later operational question. Neither count should be silently substituted for the other.
For a fictional cohort of forty eligible patients, suppose twenty receive the defined contact attempt and eight schedule an appointment within the chosen window. Those numbers describe different stages of the same process. If six later complete the visit, that is another count with its own observation period. The example illustrates measurement structure, not a benchmark for what a practice should achieve.
Write the dates and attribution rule before reporting a conversion percentage. Decide how the practice will handle a patient who already had an appointment or who schedules through a different channel. Keep missing or uncertain attribution visible. A clean-looking percentage is not useful if the team cannot explain which bookings were included and why.
Avoid duplicate or conflicting follow-up
When several employees can contact patients, the practice needs a way to understand what has already happened. Staff should review the relevant communication and appointment context before starting another attempt. A patient who has already responded should not receive an unnecessary repeat simply because another employee is working from an older list.
Use the supported Jelo records to coordinate the work and document any additional operating step your practice requires. This guide does not promise automatic deduplication across every outside campaign or channel. If the practice uses another tool, explain how the teams will keep the two processes aligned. An integration or manual reconciliation requirement should be part of the setup plan, not an assumption.
Define what happens when an appointment is cancelled or moved after outreach. The appropriate next step depends on the reason and the practice’s approved process. Do not automatically reinsert every cancelled appointment into the same message sequence without review. A clear handoff keeps the recall workflow connected to the patient’s current situation rather than an outdated contact list.
Plan multi-location recall around office context
A patient may belong to a shared practice record while the intended visit takes place at a specific office. The recall message, scheduling destination and staff response should use the correct context. A general practice-wide invitation can create confusion if the patient cannot tell which location is relevant or if a reply reaches a team unfamiliar with the intended appointment.
Jelo’s multi-location functionality is available and uses office membership and role permissions. Confirm how your messaging numbers, account setup and supported views represent each location. Do not infer that every office automatically has an independent number or identical recall configuration. Bring the actual office structure and staff responsibilities to the implementation discussion.
When measuring results across locations, use consistent definitions and show the office scope. Different volumes, staffing patterns and appointment availability can affect the observed counts. The purpose of the comparison is to identify a useful operating question, not to declare one office successful based on a percentage without context. Keep the raw counts and the relevant period visible.
Review unresolved responses with a small exception list
An exception list helps the team organize work that did not follow the expected path. Useful entries identify the source reference, reason for review, responsible role and next action. Keep patient details inside the approved practice system and use references or aggregate summaries in broader reviews. The list should help someone continue the work without unnecessarily duplicating sensitive information.
Group exceptions by the action needed. A contact-information issue, an unanswered scheduling question and a clinical question require different owners. Review the groups with the relevant staff rather than repeatedly asking one person to solve every type of problem. An exception can remain open while it awaits the appropriate review; the important point is that its status and responsibility remain understandable.
Look for a repeated cause before changing the entire recall process. If patients often ask the same practical question, revise the approved instruction. If staff cannot find prior communication, review navigation and training. If appointments are not available when people respond, discuss scheduling capacity. More messages will not necessarily solve a problem in a later handoff.
Measure improvement using the same definitions
Choose a small set of measures tied to your objective. These might include the eligible cohort, defined contact attempts, replies needing action, appointments scheduled and appointments completed. Record the source for each count and the observation window. A measurement plan becomes more useful when another employee can reproduce the count using the same definition.
Use ratios only when the numerator and denominator belong to the same scope. For example, dividing bookings attributed to a defined cohort by the number of people in that cohort answers a different question from dividing bookings by total messages sent. Neither calculation should be labeled vaguely as a universal “recall rate.” State the calculation in words and show the counts next to it.
After a workflow change, repeat the definition and note relevant differences in staffing, volume, message content or appointment availability. A before-and-after difference is an observation, not proof that Jelo caused the result. The operations worksheet supports transparent completion-rate arithmetic, but it does not provide an industry benchmark or a clinical outcome score.
Connect recall with the broader patient relationship
Recall is one part of ongoing communication. The practice may also handle ordinary patient questions, appointment changes and other follow-up through its CRM. Coordinate these activities so staff can understand the patient’s current context before taking the next action. A message sequence should support a coherent relationship with the practice rather than operate as an isolated campaign whose history is difficult to find.
Jelo’s connected platform includes patient CRM, scheduling, messaging and recall workflows. During evaluation, follow one fictional patient across those areas and ask what an authorized staff member can see. Review permissions and office context as well as convenience. The useful result is a demonstrated handoff that fits your practice, not an assumption that every outside channel or marketing service is included.
Keep marketing activity distinct from the fact that someone asked an administrative question. Review the intended purpose and permissions for each communication through the practice’s approved process. For broader outreach and discovery work, see the local marketing guide. It connects website inquiries to staff follow-through without claiming that Jelo manages business listings or creates patient reviews.
Build a short review agenda the team can sustain
A practical recall review can cover five questions: is the cohort still correct, are sending prerequisites ready, do replies have owners, are scheduling handoffs complete and what unresolved pattern needs attention? The practice chooses the frequency. The value comes from a focused action record rather than a meeting that repeats totals without deciding what to do.
Invite the people needed for the current questions. A manager may resolve responsibility or staffing issues; a clinician may need to review a clinical question; the person managing the account may need to address a configuration dependency. Keep the review proportional to the problem and protect patient information when sharing summaries beyond the people who need individual details.
At the next review, inspect the result of the agreed action. If the team changed a message, review whether the specific confusion declined. If it changed reply ownership, check whether unresolved conversations now have a clear next step. Record what the evidence supports and what remains uncertain. This keeps improvement grounded in the practice’s own observations.
What to demonstrate before adopting the workflow
Bring a fictional cohort definition, an example message and a scheduling scenario to a demo with Joel or Loreli. Ask how the appropriate employee identifies the group, reviews relevant communication information and follows the reply into the next action. Include a patient who already has an appointment and a question that needs clinical escalation. These examples make the scope testable.
Confirm the sending setup, consent process, office context and account prerequisites before treating the workflow as ready. Review how results are represented and which counts the practice can reliably use. The platform subscription is per location; any relevant service or outside-account requirements should be discussed separately. Do not turn a general feature description into an assumption about every channel or configuration.
Leave with an operating record that identifies the cohort, message purpose, responsible staff, exception path and measurement definition. Those decisions give the practice a way to train new staff and review the process later. The aim is dependable follow-through on the practice’s own decisions, with clear evidence of what happened at each stage.