Back to the blog

Reliable reminders: designing notifications as a product responsibility

A vaccine or medication reminder seems like a small feature until it arrives late, arrives twice or arrives for a treatment that has already changed. In a care product, every notification is an operational promise. Milo Care treats that promise as part of the domain, not as an email sent at the end of a flow.

A wrong notification is trust debt

On transactional platforms, a wrong notification can generate a ticket. On a platform tied to an animal's care, it can lead the user to ignore the next message. That's why the quality of a reminder isn't measured only by email delivery: it depends on the date, the status and the clinical context being correct.

Milo Care starts from structured events —vaccines, medications and appointments— with their own due-date logic. The reminder is derived from that state, not from an isolated list of pending emails. That way, the system preserves the link between the message and the information that justifies it.

Scheduled jobs with explicit rules

Execution uses node-cron to go through the due dates and Resend for delivery. The technical component is simple; the operational design isn't. The rules have to define when an event is eligible, when it stops being so and what should happen when the user modifies or completes a task.

The strategy is conservative: with a reminder, sending too much or too late degrades the product just as fast as not sending at all. Scheduling should favor visible, auditable conditions over opaque automation that maximizes email volume.

Operations start before sending

A notification pipeline needs observability over runs, eligible events and deliveries. Although the MVP doesn't need a complex messaging platform, it does need the team to be able to answer basic questions: which task produced the email, when it was evaluated and why it was sent.

This foundation lets the product evolve without rewriting it: channel preferences, time windows, engagement metrics and premium rules can be added on top of the same due-date model. Extensibility comes from the domain, not from anticipating unnecessary infrastructure.

Reference architectureReminder pipeline based on due dates

The clinical modules record events and dates. A scheduled job identifies applicable reminders, applies sending rules and delivers the email through Resend. The history preserves the context for the caregiver.

Reliability principle: a notification is part of the product experience. It must be derived from a correct domain state, run on explicit rules and be explainable when the user asks why they got it.

Keep reading

More in Architecture and platform Reading path: Products, startups and MVPs