Start with a goal.
Tell Recall the outcome you want. The planned guidance translates that direction into an audience brief and identifies the minimum fields to review from the source system.
Outcome → audience → export guidanceHow it works / From intent to review
From a practice goal to a reviewable recall plan.
Recall is designed to connect the outcome, audience, export guidance, and editable message plan before a practice decides what happens next. This public page is an illustrative synthetic preview; it does not accept uploads or send messages.
Every example below is synthetic and illustrative. No patient information is uploaded, stored, sent, or received by this page.
Chapter 01 / Direction
Two ways to create a useful beginningStart with the reason or the list.
The planned workflow can begin with a practice outcome or an existing contact list. Either way, the next step is a reviewable plan—not an automatic send.
Start with a list.
Begin with a practice-owned contact list in the planned authenticated workflow, map its fields, and define what those people should do. This public preview accepts no file and keeps the example synthetic.
List → goal → campaign planChapter 02 / Workflow
A deliberate path from idea to reviewDirect → Export → Audience → Messaging → Recall.
Each stage keeps the practice's intent visible. The sequence is a product illustration, not evidence of a live upload, scheduled campaign, send, or delivery state.
Direct
Define the outcome you want and the right next step.
Export
Use source-system guidance to export only the minimum contact fields needed for a planned review.
Audience
Shape an audience around the practice goal and the criteria the practice controls.
Messaging
Edit action-oriented SMS and email drafts geared to the goal.
Recall
Practice staff review the plan and own any future reply handoff.
Chapter 03 / Intelligence
Useful guidance, strong human controlExport less. Say more. Review everything.
The source system remains the right place for clinical filtering. Recall's planned preview keeps the contact mapping narrow and the messages editable.
Keep clinical filtering where it belongs.
Choose the EMR or EHR path, follow tailored export guidance, and complete clinical or eligibility filtering inside the source system. The planned workflow maps only the minimum required contact fields.
[firstName][lastName][phone][email]
Select your systemTailored path
Filter in the sourcePractice control
Map the contact fileFour fields
A first draft that earns the next action.
Messaging begins with the practice goal, the audience, and the action patients should take—not a generic reminder. The public examples are synthetic and remain illustrative; they do not call a provider or send a message.
SMS illustration
Hi [firstName]—it may be time to revisit the symptoms you discussed with [practiceName]. Would you like a member of our team to reach out? Reply STOP to opt out.
Hi [firstName]—it may be time to revisit the symptoms you discussed with [practiceName]. Would you like a member of our team to reach out? Reply STOP to opt out.
Email illustration
A thoughtful follow-up from [practiceName], shaped around the conversation your team wants to have next.
A thoughtful follow-up from [practiceName], shaped around the conversation your team wants to have next.
Draft → edit → practice approval
Chapter 04 / Practice review
The handoff stays humanA clear plan is useful only when the practice owns the next step.
Recall is presented as a support system for practice decisions. Human approval and reply handoff remain explicit parts of the intended workflow.
Review the audience
The practice keeps clinical and eligibility filtering in the source system before a future outreach path is considered.
Approve the message
Every SMS and email illustration is editable. Human approval stays in the loop before any future production action.
Hand replies to staff
A planned reply handoff returns the conversation to the practice team; this public preview does not send or receive messages.
Synthetic preview / No live workflow
Open Recall See the direction before you make a decision.
Open the existing Recall preview to explore the product boundary. It uses synthetic examples only and does not upload, persist, schedule, send, or receive anything.