Patient Communication
Say the right thing for the reason you are calling
One patient, many reasons you might be contacting them, and the wording that fits the actual reason.
- Per use case
- Its own wording, timing, and trigger
- Your voice
- Written by the clinic, not a stock script
- One engine
- Every campaign shares the same controls
What Changes
How it goes without automation
- One generic reminder script is reused for every reason a patient is contacted.
- A patient overdue for screening hears the same words as someone confirming a routine visit.
- Changing the wording means asking whoever set it up originally.
- Campaigns that need different timing get the same timing, because there is only one setting.
How it goes with Joud Health
- Each reason for contact is its own use case, with its own wording.
- A patient hears why this call is happening, in your clinic’s language.
- Timing is set per use case, because a physical recall and a post-op check are not the same clock.
- Adding a new campaign does not disturb the ones already running.
Step By Step
Your team
Your clinic writes the message
What to say, when to say it, and what should trigger it. This is yours: a recall for an overdue physical is a clinical decision about tone as much as timing.
Joud Health
A patient becomes due
From a list your clinic supplies, or from a visit that triggers a follow-up. The reason they are due is what decides everything after this.
Joud Health
The matching message is chosen
One patient can be due for more than one thing. The use case that actually applies is the one they hear, rather than a general reminder that covers none of them properly.
Screening duePatient
They hear why you called
In your clinic’s own wording, naming the actual reason. A patient who understands why they are being contacted is far likelier to book than one who heard a generic prompt.
Joud Health
Booked and recorded
If the call needs an appointment it is made there, and the outcome is recorded against the use case so you can tell which campaigns are working.
BookedWhat It Hands Off To
A point solution finishes its own job and stops. These workflows run on one platform and one EMR connection, so the end of one is the start of the next.
- Outreach And Recall
Recall campaigns are the most common thing to configure this way, one use case per reason patients are due.
- Follow-Ups
Post-visit follow-ups are another use case, with their own timing and their own words.
- Confirmations And Reminders
Confirmation and reminder wording is configured the same way, per clinic rather than per vendor.
How It Is Set Up
- Scope
- Wording, timing, and trigger, all per use case
- Examples
- Annual physicals, overdue screening, post-op checks, seasonal campaigns
- Authorship
- Written with your clinic during onboarding
- Isolation
- A new campaign does not disturb running ones
- Control
- Each use case can be stopped on its own
- Reporting
- Outcomes recorded per use case
Questions
What counts as a use case?
Any distinct reason you contact a patient. Annual physicals coming due, an overdue screening, a post-operative check, a seasonal campaign, a medication review. If the reason differs, the wording and the timing usually should too, which is what makes it a separate use case rather than a variation of one.
What if a patient is due for two things at once?
They hear the one that applies rather than both stacked into a single call. Combining them tends to produce a message that does neither well, and a patient who is unsure what is being asked of them books nothing.
Can we change the wording ourselves?
Changes are made with us rather than through a self-serve editor today. That is a real limit and worth saying plainly: it means a wording change is a conversation, not a five-minute edit, though it also means nothing goes out to patients that nobody reviewed.
More Care. Less Admin.
All of it, on one platform
JOUD Health works quietly in the background so your team is free to focus on what matters: patient care.
Request a demo