Skip to content

Keep patients on track, from appointment to follow-up.

Reduce no-shows, support medication adherence, and keep patients informed with consent-aware messaging across SMS, WhatsApp, and RCS, all through one API.

A clinician at a workstation beside an automated appointment reminder confirmed by a patient over SMS

Healthcare communication breaks at the moments that matter.

When messages arrive late, go unseen, or live across disconnected systems, patients lose momentum and providers lose valuable time.

  • Appointments get missed

    Patients forget upcoming visits or cannot reschedule in time, leaving empty slots and interrupting continuity of care.

  • Refills slip through

    Pickup, refill, and dose reminders arrive too late, or not at all, making medication adherence more difficult.

  • Follow-ups lose momentum

    Post-visit instructions, preventive care reminders, and important updates disappear across fragmented communication channels.

Meet Sent: one messaging layer for every patient journey.

ReminderAppointmentSchedulingFollow-ups

Turn every care moment into a clear next step.

Automate essential patient communication without building separate workflows for every channel, provider, and messaging requirement.

  • An appointment reminder with confirm and reschedule replies

    Appointment reminders patients can act on

    Send scheduled reminders with confirmation, reschedule links, location details, and preparation instructions through the channel most likely to reach each patient.

  • A refill alert offering a repeat request and a secure portal across SMS, WhatsApp and RCS

    Prescription and refill alerts that keep care moving

    Notify patients when medication is ready, remind them when refills are due, and direct them to a secure portal when more information is needed.

  • Care coordination and follow-up

    Automate post-visit check-ins, preventive care reminders, recall campaigns, and ongoing patient outreach.

  • Intelligent routing and fallback

    Sent retries, switches provider, or moves to another channel so a reminder still reaches the patient it was written for.

  • Real-time delivery visibility

    Track every message from request to delivered, failed, and read through consistent status events and webhooks.

Under every reminder is infrastructure built for complexity.

Patient contacts normalised, the correct template applied, compliance checked, then routed

Connect once to the systems your teams already use

Trigger messages from scheduling, pharmacy, or care platforms through one API. Sent normalises patient contacts, applies the correct template, and delivers through SMS, WhatsApp, or RCS without separate integrations.

The workflow keeps moving when delivery fails

Sent can retry, switch providers, or fall back to another available channel while preserving consent rules and giving your team a complete delivery history.

A reminder retrying across SMS, WhatsApp and RCS until it is delivered and read

Built for healthcare communication where trust comes first.

  • Support consent-aware messaging, secure portal links, controlled templates, and clear message records without exposing unnecessary patient information.

  • Every send checks the patient record for permission first, and a reply that opts out is honoured across every channel from that moment on.

  • Redundant routes, regional delivery, and an engineering team on hand keep patient communication running through the moments that matter most.

An appointment reminder passing from a healthcare system through Sent to a secure portal link, delivered

Frequently asked questions

Appointment reminders with location and preparation details, prescription-ready and refill alerts, post-visit check-ins, and preventive-care or recall reminders. Your scheduling, pharmacy, or care platform triggers each message through one Sent API call, and Sent delivers it over SMS, WhatsApp, or RCS.

Add buttons such as "Confirm" and "Reschedule" to the reminder template. They appear as tappable buttons on WhatsApp and suggestion chips on RCS; on SMS, include a reply keyword or a link in the text. Every tap or reply reaches your scheduling system as a reply event, so the appointment is updated where it lives.

Sent is SOC 2 Type II certified, with data stored in AWS regions in the US and EU. If you need a BAA or HIPAA documentation, contact Sent before sending patient data.

Yes. Set a send time on the request and Sent holds the reminder until then. If the appointment is cancelled, your system can cancel the reminder through the API before it goes out. Sent also holds any message that would arrive during the patient's local quiet hours, and releases it when the window opens.

SMS works on every mobile phone with no app to install, including basic phones. When Sent chooses the channel, it checks which channels each patient can receive and uses SMS whenever WhatsApp or RCS isn't available. Patients who prefer plain texts and those who use WhatsApp both get the reminder from the same template.

Yes. Create one template per language and have your system choose the template that matches the patient's preferred language. On SMS, languages with non-Latin scripts, such as Arabic or Chinese, use a different character encoding with a 70-character limit per message, so keep those reminders short.

No. Sent only delivers messages. Your EHR, scheduling, or pharmacy system decides what happened and what the patient should do next, and remains the record for appointments and care. Sent sends the message, reports whether it was delivered, and passes patient replies back to your system.