Reliable reminders and notices for patients and providers, with access controls and clear data handling.
Dependable patient notices with privacy-first AI and a human on every message
Reminders must arrive in time
Dedicated streams and monitoring keep time-sensitive mail moving.
Messages should not carry sensitive details
Templates make it easy to send a secure-portal link rather than content.
Who sent what must be traceable
Audit logs and role-based access show who changed settings.
Care messages should be clear, minimal and easy to act on. The steps below keep them careful by design.
Healthcare email is the operational email that clinics, hospitals and health apps send to patients and staff: appointment reminders, booking confirmations, prompts to open a result in a portal and internal scheduling alerts. These messages are practical rather than promotional. They need to arrive in time, say as little sensitive detail as possible, and leave a record of who sent what. Their value depends on reliability, tone and restraint with sensitive information.
Healthcare senders often rely on a scheduling or practice-management system with limited email controls. Reminders arrive late or land in spam, staff and patients cannot tell whether a message bounced, and templates drift as different people edit them. Teams also worry about putting details in an email, and without clear roles and logs, nobody can say who changed a setting or which version of the wording went out. Small gaps add up quickly.
MigoSMTP, built on MigoMTA, sends reminders from your scheduling system by API or SMTP, keeps them on a monitored stream, supports reviewed templates that point patients to a secure portal rather than carrying details, and records access and changes in audit logs. AI can suggest plain-language wording and flag likely no-show risks using redacted data. Staff approve all wording and sends.
Send reminders at set intervals before a visit and use delivery events to see which patients did not receive them, so staff can follow up another way.
Confirm scheduled visits straight after booking with consistent, reviewed wording, location details and a link to reschedule or cancel. Staff can see which patients received them.
Tell patients that a result or document is ready and direct them to sign in to a secure portal, without placing the content in the email.
Notify staff of schedule changes or cancellations quickly, on a separate stream and domain from patient mail, with access limited by role. Audit logs record any configuration change.
Invite eligible people with plain wording and a clear way to book or opt out.
Remind patients that a refill is due without naming the medicine in the message.
A careful message keeps health detail out of the inbox.
This is general good practice, not legal advice. Check your own obligations with your legal and compliance advisers.
Suggest clear, readable reminder and preparation wording at a suitable reading level. Clinical or administrative staff review and approve each template before it can be used.
Highlight appointment types or time slots with higher historical no-show rates, using redacted data, so staff can add extra reminders. People choose whether to act on them.
Remove names, identifiers and clinical terms before any AI analysis, and allow administrators to turn AI off.
Ask which reminders bounced this week and get a summary from the delivery log. The copilot reads status information only and never edits messages. Answers cite status entries only.
AI features are assistive, staff approve all content and keep control, and regulated data handling must be confirmed with the customer's compliance team before use.
Say that a message is waiting and link to an authenticated portal, instead of including diagnoses, results or detailed notes.
Keep standard wording in templates that clinical or admin leads approve, so every patient sees consistent and accurate information.
Use webhooks to find undelivered reminders and trigger a phone or SMS follow-up, particularly for high-priority appointments. Document each fallback step.
Use different domains or streams for patient notices and internal alerts, with role-based access to each. Review that access every quarter.
Need to discuss a sensitive use case? Talk to us before you design the flow.
Trigger reminders from your scheduling system through an API or SMTP, at set intervals before the visit. Use an authenticated domain, concise wording, a reschedule link, and delivery events so you can follow up when an email bounces. Keep the message brief.
It is safer to keep details out. Send a short notice and link to an authenticated portal. What you may include depends on the rules that apply to you. When unsure, leave detail out.
We make no compliance claim on this page. Whether a service suits your obligations depends on your jurisdiction, contracts and configuration, so confirm with your compliance team and review the Trust page. Ask for current written documentation before signing anything.
Authenticate the sending domain, use a recognisable From name, avoid promotional language and large images, and keep reminders separate from marketing. Watch bounce and complaint data by provider so you can respond to filtering early. Review these settings after each platform update.
Timely reminders with an easy reschedule or cancel link give patients a chance to act. Track which reminders were delivered, and use a second channel for patients whose email bounced. Test wording with a small group first.
Limit access by role: administrators manage domains and keys, template owners edit wording, and most staff get read-only views. Review the audit log for changes, and remove access promptly when people change roles. Limit administrator rights to as few people as practical.
Only with care. Use redaction, keep AI optional, and require staff review of anything it drafts or flags. Confirm the approach with your compliance team before enabling it. Keep an approval record.
It can draft plain-language wording from generic descriptions, summarise delivery logs with identifiers removed, and highlight scheduling patterns from redacted data. Staff approve all output. Nothing is sent without human approval and review.
Tell us about your volume and setup and we will walk you through the right configuration.
Create an account, add your domain and send your first email.