Most healthcare messaging is administrative, and administrative is exactly where a missed message costs a wasted appointment slot. The discipline is to say just enough to be useful and nothing that belongs in a clinical record.
The pattern that works is a confirmation plus a timed reminder, on the same number the patient booked with, with a one-tap way to change the appointment. Everything else is noise that trains people to ignore the channel.
The platform stores no message bodies — the log keeps metadata only, which removes one place detail could accumulate. What the message says is still yours to decide: content passes through your provider and lands on a handset that may be shared. The practical rule is to send a reference the patient resolves in your own portal rather than the clinical detail itself.
Who may be contacted, what may be said, and how long records are kept are clinical and professional obligations, and they stay where the duty sits — with the healthcare provider. The platform’s part is getting the message there reliably and keeping a record of the send.
The platform asks you to declare what kind of message you are sending instead of inferring it from the text. That one field decides whether the opt-out gate applies — and the honesty of the declaration is yours.
Read the guide →Message content is not archived. What is kept is metadata — and among that metadata two fields are load-bearing, because without them a bill could not be reconciled.
Read the guide →A storefront is mostly a messaging operation that happens to have a checkout. The confirmation, the dispatch note, the delivery window, the code for a failed payment — these are the messages customers actually read, and they run on the same few send paths every day.
Open →In payments, the message is often the product: a code that must arrive before a session expires, an alert that proves a transaction happened, a reminder that keeps a subscription alive. Latency and duplicates matter here more than anywhere else.
Open →A delivery operation lives on contact attempts: the customer who is not home, the gate code nobody has, the parcel going back to the depot. Each of those is a message that either saves a second attempt or causes one.
Open →For a SaaS product, messaging is infrastructure with a product surface: the login code, the incident notice, the trial-expiry nudge. These messages sit on the critical path of someone else’s workday, which sets a higher bar than marketing ever has.
Open →Education messaging is overwhelmingly about timing: a class that moved, a deadline that is close, an enrolment that has not been confirmed. The failure mode is not a missing message, it is a message that arrives after it matters.
Open →A marketplace sends to two audiences who care about the same event for opposite reasons: the buyer wants it to arrive, the seller wants proof that it did. That makes receipts and auditability the interesting part of the problem.
Open →Travel messaging is time-zone-shaped: a confirmation that must arrive immediately, a reminder that should arrive the evening before, and a disruption notice that is worthless if it arrives after the guest has left for the airport.
Open →Field service messaging is measured in minutes: a technician is twenty minutes away, a job has moved, a customer will not be in. Every one of these messages exists to avoid a wasted trip.
Open →