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.
14,000+ developers and product teams rely on Sent for messaging
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.
Turn every care moment into a clear next step.
Automate essential patient communication without building separate workflows for every channel, provider, and messaging requirement.
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.
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.
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.
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.
Frequently asked questions
Your system calls one Sent API endpoint when an event happens — an appointment booked, a prescription ready, a visit completed. Sent handles the template, the contact, the channel, and the delivery record from there.
Yes. One request can reach SMS, WhatsApp, or RCS, and you can set the order Sent tries them in or let it choose the strongest available route per patient.
Consent is checked before every send, and a reply that opts out is honoured across every channel from that moment on. Required care communication is kept separate from marketing.
No. Templates can carry the minimum a patient needs to act, with anything sensitive kept behind a secure portal link into your own authenticated surface.
Yes. Replies such as confirm, reschedule, or cancel come back to you as inbound events, so your system stays the source of truth for the appointment.
Every message returns a status event — queued, sent, delivered, failed, and read where the channel supports it — with a message ID you can store against the patient record.
Sent can retry, switch provider, or fall back to another channel, and the failure reason comes back with the event so your team knows which recovery path to take.
Yes. Templates live in one place, carry channel-specific approvals where a channel requires them, and are reused across every system that triggers a send.
Yes. Test credentials are separate from production, so a full journey can be run end to end without a message reaching a patient.
No. Sent is the delivery layer. Your systems decide what happened and what the patient should do next; Sent carries the message and returns what happened to it.