Appointment reminder calls that follow your timing and consent rules.
Configure Truvoca to call eligible appointments within the approved window, deliver the minimum information needed for the reminder, capture the result, and follow the tested no-answer, voicemail, opt-out, or staff follow-up path.
This workflow is launch-gated. It should not be published as available until the appointment source, consent or lawful basis, suppression, time zones, calling windows, disclosure, retries, voicemail, outcomes, and system behavior have been verified in a production-like test.
30 minutes over Google Meet. Times are shown in Eastern European Time (GMT+03:00). Scheduling runs on Google Calendar, so choosing a time takes you into Google’s service.
- Verified appointment source and eligibility
- Customer-approved timing and communication rules
- Minimum reminder content
- Documented answer, no-answer, opt-out, and follow-up outcomes
Start from an appointment that is still eligible
Define which records enter the reminder workflow.
The source of truth may be a scheduling system, a connected record, or a controlled appointment list. Document the statuses that qualify, the source and timestamp of consent or other approved basis, suppression lists, cancellation and change checks, duplicate logic, recipient time zone, and the owner of the reminder policy.
The workflow must recheck changes close enough to the call to prevent reminders for cancelled, moved, duplicated, protected, or otherwise ineligible appointments. The refresh method and race-condition behavior are implementation facts, not assumptions.
- Source system, object, and eligible statuses
- Consent or lawful-basis evidence and owner
- Do-not-call, opt-out, and other suppression rules
- Cancellation, reschedule, and duplicate checks
- Recipient time zone and trigger timing
- Last refresh and response to a late appointment change
From eligible appointment to recorded result
Use one auditable sequence for every reminder attempt.
The workflow separates eligibility, delivery, response, and follow-up so the team can tell what actually happened.
- Select an eligible appointment from the approved source.
- Check the current status, recipient time zone, calling window, and suppression rules.
- Place the call and deliver the reviewed AI and recording disclosure when applicable.
- State only the approved reminder details and collect the permitted response.
- Apply the tested no-answer, voicemail, retry, opt-out, confirmation, or staff-follow-up rule.
- Record the attempt, disposition, next action, and timestamp in the approved destination.
- Alert the responsible owner when the call or system action does not complete.
Say enough to be useful — no more
Control which appointment details are spoken.
The reminder script should use the minimum necessary appointment details for the approved purpose. Define whether the recipient must complete an identity or privacy check before hearing a service, provider, location, or other detail. Exclude sensitive information that is not needed for the reminder.
Every personalization field needs a trusted source, fallback, pronunciation rule, and update owner. Language support is verified per script and workflow; the page should not imply universal language coverage.
- Approved recipient name or neutral greeting
- Date, time, and time zone stated clearly
- Service, provider, and location only when permitted
- Identity or privacy check where required
- Pronunciation and missing-field fallback
- Script version, language, and responsible approver
Communication rules are part of the product behavior
Apply approved timing, consent, disclosure, and opt-out rules before every call.
The customer and its advisers define the lawful communication policy for the use case and jurisdictions involved. Truvoca must be configured to use the recipient's time zone, permitted days and hours, frequency limits, suppression lists, AI disclosure, recording notice, and any required consent checks.
An opt-out should stop the conversation as defined, create the tested suppression record, prevent prohibited retries or future campaigns, and make the result available to the responsible team. This page explains the operational controls; it does not provide legal advice or guarantee TCPA, HIPAA, or other compliance.
- Recipient time zone and counsel-approved calling window
- Consent or other approved basis tied to the recipient and purpose
- Frequency and campaign limits
- Do-not-call and customer-specific suppression
- AI and recording disclosure where applicable
- Immediate opt-out response and durable suppression record
A failed connection still needs a defined outcome
Set a privacy-safe rule for no answer, voicemail, and retries.
Voicemail detection and message content must be tested together. If a message is permitted, it should disclose only approved information and follow the customer's consent, privacy, callback, and opt-out rules. If voicemail is disabled or uncertain, the workflow should record the correct disposition without leaving unintended content.
Retry count, spacing, permitted windows, busy signals, disconnected numbers, wrong numbers, carrier filtering, and stop conditions are customer-specific. The final attempt should create a clear outcome or staff task instead of an endless retry loop.
- Answered, busy, no answer, disconnected, and wrong-number dispositions
- Voicemail detection and privacy-safe message
- Approved retry count, spacing, and calling windows
- Stop on opt-out, ineligibility, or appointment change
- Carrier or telephony failure path
- Final disposition, responsible owner, and staff task
Keep reminder, confirmation, and rescheduling outcomes distinct
Route each response to the workflow that can complete it.
A reminder can invite a response, but the recorded outcome must match the action actually completed. A clear confirmation follows the approved appointment-confirmation rules. A cancellation or request for another time follows only the actions verified for that system and policy.
Capturing a preferred time, creating a callback task, or sending a scheduling link is not a completed reschedule. If the system transaction is unavailable, say that staff follow-up is required and preserve the original appointment state.
- Reminder deliveredcommunication outcome only
- Confirmation captureduse the verified confirmation taxonomy
- Cancellation requesteddistinguish request from completed cancellation
- Reschedule requesteddistinguish preference from committed change
- Question outside scoperoute to the approved team
- Unclear responsesafe fallback without changing the appointment
Make every attempt and next step reviewable
Connect the reminder to a verified source record and outcome.
A useful demonstration starts with the eligible appointment record and shows the status and timing checks, call attempt, disposition, any opt-out or voicemail behavior, and the resulting task or system update. Timestamps should make it possible to understand whether a last-minute change was recognized.
Write-back must be verified for the exact connector, object, fields, permissions, validation, duplicate behavior, and failure response. If a connected update is not confirmed, the workflow should retain a no-write outcome and alert the designated owner.
- Eligible source record and last refresh
- Call attempt and reviewed disposition
- Opt-out or suppression update when used
- Voicemail and retry evidence when enabled
- Verified write-back, task, or notification
- Timestamp, audit detail, failure result, and reconciliation owner
Reliable reminders begin with clean data and stable rules
Use this workflow when eligibility, timing, and outcomes can be governed.
Reminder calls fit operations with dependable appointment data, documented communication rules, a maintained script, controlled retry and voicemail behavior, and a team that reviews outcomes. They are a poor fit when consent or recipient identity is unclear, appointment changes cannot be refreshed, sensitive details cannot be bounded, or no one owns failed attempts.
Keep the page gated until the applicable legal, operational, telephony, integration, and security checks are complete.
Good fit
- stable appointment source and clear eligible statuses
- documented timing, consent, and suppression policy
- monitored dispositions and follow-up owner
Exclude
- uncertain source or stale change data
- sensitive details without an approved privacy flow
- campaigns with no opt-out or failure owner
Validate the reminder workflow before the first production call.
Share the appointment source, eligible statuses, consent or lawful-basis owner, time zones, calling windows, reminder content, response taxonomy, voicemail and retry policy, opt-out behavior, write-back destination, and legal reviewer. We will map the workflow and identify what is demonstrable, configurable, or still blocked by testing and approval.
Do not send patient or customer records, call lists, credentials, or recordings through the public demo form.
FAQ
FAQ
How is consent for reminder calls handled?
The customer and its advisers define the approved basis, purpose, evidence, calling rules, and jurisdictions. Truvoca must apply those rules and record the tested result, but this page does not provide a universal compliance guarantee.
When are reminder calls placed?
Each deployment uses approved trigger timing, permitted days and hours, the recipient's time zone, frequency limits, and appointment-status checks. There is no single timing rule for every customer.
What appointment details are spoken?
Only the minimum details approved for the reminder. Service, provider, location, or other sensitive context may require an identity or privacy check and should be omitted when it is not necessary.
Can the agent leave voicemail?
Only after voicemail detection, message content, privacy, consent, callback, opt-out, and failure behavior have been tested for the workflow. It is not treated as universally enabled.
How many times does Truvoca retry?
The customer-approved policy sets the limit, spacing, calling windows, and stop conditions. Retries must stop after opt-out, ineligibility, an appointment change, or the final permitted attempt.
Can a recipient opt out?
The deployment should define and test the in-call response, durable suppression record, effect on retries and future communications, external request path, and staff visibility. The exact rule depends on the use case and jurisdiction.
Can the call confirm or reschedule the appointment?
Confirmation follows the verified confirmation workflow. A completed reschedule requires current availability, scheduling rules, a two-way system transaction, confirmation, and safe failure handling; capturing a preferred time is not enough.
What happens if the appointment changes before the call?
The workflow should recheck the current record according to a tested refresh strategy, suppress cancelled or moved appointments, prevent duplicates, and surface any race condition that cannot be resolved automatically.