Practical guide
Managing patient communication and follow-up
Define the relationship work your team manages
An optical CRM should help staff understand the next communication or follow-up task in the context of the patient record. That work can include an appointment question, an optical order update, a recall invitation or a response that needs a staff member's attention. Begin by listing the situations your practice actually handles rather than starting with a desired number of messages.
For each situation, identify the reason for contact, the intended recipient, the responsible role and the event that completes the task. A message may be sent successfully while the underlying question remains unresolved. Keeping those facts separate helps the team decide what to do next.
Jelo includes patient CRM, messaging and recall in the per-location platform. The current workflow should be evaluated with your account setup, communication preferences and staff responsibilities. It is not a promise of a particular retention rate or an automatically full calendar.
Use the patient record to establish context
Before contacting someone, staff should identify the correct patient and review the information relevant to the task. Similar names, outdated contact details and an existing appointment can all affect the next action. Decide how employees resolve uncertainty instead of asking them to choose the first plausible record.
The amount of context needed depends on the communication. An administrative appointment question may require different information from a clinical follow-up. Staff should only handle the work appropriate to their role and route clinical questions to a qualified person through the practice's approved process.
In a demonstration, use a fictional returning patient with an existing appointment and a separate optical order. Ask the employee to explain which record matters to the message being prepared. This tests whether the CRM supports an understandable conversation rather than presenting every piece of information as equally relevant.
Keep contact details and preferences usable
A communication process depends on accurate contact information and the patient's preferences. Decide who verifies a changed telephone number or email address and how staff know which route is appropriate. A message sent to an outdated number can create confusion even when the software completes its technical task.
Separate routine appointment communication from marketing decisions and review the applicable consent requirements with the practice's responsible person. This guide does not establish a universal permission to contact every person in a database. The practice should define how preferences, opt-outs and exceptions are recognized in its actual workflow.
Test one changed contact detail and one patient who should not receive the planned message. Ask how the employee identifies the issue and what action follows. Record any configuration requirement or unanswered behavior before using a larger audience. A controlled example is easier to inspect than discovering a misunderstanding after a broad send.
Distinguish message purpose before drafting
An appointment reminder, an order update and a marketing invitation have different purposes. Write the purpose in one sentence before creating the message. That helps staff choose the relevant information, avoid unnecessary detail and understand what response they expect from the patient.
Keep the wording consistent with facts the practice can confirm. An order update should reflect the actual status rather than an assumed delivery date. An appointment instruction should identify the correct office and the next step. If the message requires an individual clinical judgment, involve the appropriate professional instead of using a generic template as the answer.
Review reusable wording periodically. Hours, office names, appointment routes and staff responsibilities can change. Assign an owner to the template or procedure so an old instruction does not continue circulating merely because it was once approved.
Give outgoing communication a receiving owner
The work does not end when a message leaves the practice. A patient may reply with a scheduling change, an order question or an issue requiring clinical review. Decide who checks responses, how often the queue is reviewed during operating hours and who covers an absence.
Define what the receiving employee can resolve and when the item should be routed elsewhere. The handoff should preserve the question, the relevant source and the next owner. Avoid making patients repeat the same issue because staff cannot see what has already been discussed.
Test a reply that changes the original task. For example, a fictional patient responding to a recall invitation may say that an appointment is already booked. Staff should understand how that affects further outreach. The acceptance test should cover the response and stop condition, not only the initial send.
Understand the messaging connection
Jelo uses Sinch for messaging. The provider relationship is part of the communication workflow, but it does not establish that every possible channel, campaign or sending arrangement is configured for your practice. Confirm the specific setup you intend to use and the applicable third-party charges.
Ask what information staff need to recognize a failed or unresolved send and where they review a response. If an account or channel requires setup, identify the owner and the evidence needed to mark it ready. Keep those prerequisites separate from the availability of the CRM itself.
The integration guide provides a framework for reviewing accounts, sending configuration and exceptions. Use a controlled fictional example when evaluating the workflow. Do not use a real patient audience merely to confirm that a sales demonstration can send a message.
Build recall from a clinically approved reason
Recall begins with the practice's decision about who needs follow-up and when. The appropriate clinical professional should establish the relevant criteria. The CRM can support the operational work around that decision, but a marketing page should not prescribe a universal interval for every patient.
Define the eligible group and the exclusions before preparing outreach. Consider existing appointments, recent responses, contact preferences and unresolved questions that need individual review. Assign a person to confirm the population and a separate responsibility for handling replies if your staffing requires it.
The recall operations guide explains this process in detail. Use it to create a repeatable sequence with a reason, audience, message, owner and stop condition. The goal is a clear follow-up process that staff can inspect, rather than a large number of messages with an unclear purpose.
Prevent duplicate and outdated follow-up
A patient may move between stages while an outreach plan is still in progress. They may book an appointment, call the office, reply through another route or ask not to receive a particular communication. Staff need to recognize those changes before repeating a message that no longer fits.
Decide how the team checks for existing work and how a completed or changed task stops further outreach. If two employees can contact the same person, establish an ownership rule. A shared system can support visibility, but the practice still needs an agreed process for avoiding duplicate effort.
In the demo, introduce a second contact route after the first message is prepared. Ask how the employee reviews the new information and adjusts the next step. Record whether the behavior is demonstrated, requires configuration or remains unanswered. Do not assume duplicate prevention from a general description of automation.
Connect a reply to the appropriate appointment
When a patient wants to book, staff need to move from the conversation to the correct appointment type, provider and office. The communication should preserve enough context to avoid asking the patient to start again, while the scheduling decision follows the practice's current rules.
Review the distinction between a request and a confirmed appointment. If staff must review the request before confirming, make that clear in the patient-facing instruction. A conversational agreement about a time should not be treated as a completed booking until the appropriate scheduling action is verified.
Use the scheduling page to evaluate availability, appointment rules and changes. Include a patient who needs a different office or a time that is not available. The workflow should give staff a clear next action without promising a slot that the schedule cannot support.
Keep optical follow-up tied to the order
Optical communication often concerns a specific order rather than a future clinical appointment. Staff should identify the relevant order, review the confirmed status and understand what remains outstanding. A lab response, retail order state and payment status may each affect the conversation in different ways.
Avoid using an expected completion date as a confirmed fact unless the practice has a reliable basis for it. If an outside response is missing, assign someone to investigate rather than sending an update that implies the work is complete. Patient communication should reflect what the team actually knows.
Evaluate an optical question that arrives after the original employee's shift. The covering staff member should be able to find the context and identify the next owner. The optical POS guide and VisionWeb page explain the records and external steps involved in that handoff.
Route clinical questions to the right person
A patient may use an ordinary communication channel to ask something that requires clinical judgment. Staff need an approved procedure for recognizing that the question is outside their role and routing it appropriately. The CRM should not be treated as a substitute for clinical assessment or the practice's urgent-contact instructions.
Define the administrative information employees can provide and the point at which they should involve a qualified professional. Keep the relevant question and the next owner visible within the approved practice workflow. Avoid copying clinical details into general marketing spreadsheets or unrelated tools to coordinate the response.
Test the handoff using a fictional question without asking the sales presenter to give clinical advice. The acceptance criterion is that staff know where the work goes and how responsibility is transferred. The practice's clinical lead should approve the actual procedure and patient-facing instructions.
Use the available AI assistant with review
Jelo’s in-app assistant is live and prepares supported actions for human confirmation. For patient messages, staff review the recipient and exact wording on the action card before selecting Confirm. Typing approval in the conversation does not execute an action.
That review point is useful when a draft needs a correction or the staff member realizes the wrong patient context was selected. The employee should revise or stop the action rather than assume the assistant has resolved the ambiguity. Available actions follow the user's role, location access and practice settings.
The Jelo AI page explains the live assistant and clinical support. The AI receptionist is in development. The separate, live AI biller handles insurance work at 10% of reimbursements received; availability does not mean every service is included in the platform subscription.
Distinguish activity from an operational result
A sent message measures an attempt or activity. Delivery, response, booking and attendance are different stages. Choose which stage answers the question you are reviewing and keep its definition consistent. A message count alone does not establish patient retention or revenue.
For a fictional example, a practice contacts 50 eligible patients, receives 20 responses and books 12 appointments. The response rate is 40% of the contacted group, while the booking rate is 24% of that same group. Those numbers do not tell you how many appointments were attended or why the other patients did not book.
Keep the underlying counts and period with the percentages. If the response window changes between reports, explain the difference. Review actual exceptions before attributing a change to software. The CRM can support the work, but the practice needs its own definitions and evidence to evaluate the result.
Review the queue without turning it into a blame report
A regular communication review should identify unanswered questions, repeated failures and tasks without a clear owner. Start with the work that needs attention and ask what is preventing the next action. The cause may be incorrect contact information, missing configuration, staffing coverage or an external dependency.
Assign a small number of concrete improvements. A useful action might clarify who covers replies during lunch or correct an outdated appointment instruction. Record who will make the change and how the team will verify it. Avoid adding another dashboard if the unresolved problem is simply that nobody owns the queue.
At the next review, check whether the agreed change happened and whether the same issue recurred. This creates a practical learning loop. It also gives a product discussion better evidence than a broad complaint that communication feels disorganized.
Manage communication across offices
For a multiple-location practice, the message should identify the correct office and route the response to the appropriate team. Shared patient information does not mean all office-specific instructions are interchangeable. Hours, appointment availability and external account setup may differ.
Jelo supports multiple locations, but messaging configuration should be reviewed for the actual account arrangement. Do not assume that every office automatically has an independent sending identity or identical channel setup. Confirm the requirement and test it with the staff who will handle the replies.
Use a fictional patient who contacts one office but needs an appointment at another. Ask how the team preserves context and identifies the next owner. The multiple-location guide covers office scope and rollout planning so communication can be evaluated alongside scheduling, inventory and access.
Keep a maintainable communication library
A small set of approved messages can make staff work more consistent, but each template needs a purpose and an owner. Record where it is used, which facts can change and what employees should review before sending. Avoid a library of nearly identical versions with no clear current choice.
Use plain language and a single next step where possible. If the patient needs to contact the office, provide the correct route. If the message includes an appointment detail, verify it against the current record. Do not add clinical or promotional claims simply to make a short operational message more persuasive.
Review templates when office information, appointment procedures or service availability changes. A date on a document is not evidence that someone checked the content. Keep the review practical by focusing on the facts that could misdirect a patient or create avoidable follow-up work.
Prepare the team for launch
Before using a communication workflow broadly, confirm the sending setup, staff access, contact rules and response ownership. Rehearse an ordinary message, a reply requiring reassignment and an invalid or inappropriate recipient. Each example should end with a clear next action.
Train the people who cover the work, not only the person who configured it. Have a second employee pick up an unresolved item and explain its status. This tests whether the process depends on shared information or on one person's memory of the conversation.
Use the software evaluation worksheet to record what was demonstrated and what remains open. If the practice accepts an interim process, identify where the work will live and who will review it. Launch readiness should be based on those tasks rather than an assumed benefit from turning on automation.
Review the commercial scope with the operating plan
Jelo's platform subscription is $300 per month per location or $3,000 per year per location paid upfront, with unlimited doctors and staff at each paid location. Patient CRM, messaging and recall are included in the platform scope, while account setup and applicable third-party charges should be confirmed.
Keep planned products separate from today's implementation. The AI receptionist remains on the roadmap and should not be used to fill a current staffing or phone-service requirement without a confirmed available solution. Review updates and pricing for the published status and commercial context.
Bring your communication scenarios to a demo with Joel or Loreli. Ask to follow the patient context, message preparation, response and stop condition. The result should be a usable plan for your staff, with confirmed capabilities and explicit answers still needed for your account.