Most clinic messaging is administrative, and a missed administrative message costs a wasted appointment slot. Send a confirmation at booking and a timed reminder before, on the number the patient gave you — and keep clinical detail out of it.
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 runs on the messages customers actually read: the confirmation, the dispatch note, the delivery window, the code after a failed payment. Send all of them over the SMS, email and WhatsApp accounts your store already pays for.
Open →In payments the message is often the product: a code that has to land before the session expires, an alert that proves a transaction happened, a reminder that keeps a subscription alive. Connect your own accounts, and the send path stops being the part you have to watch.
Open →A delivery operation lives on contact attempts: the customer who is not home, the gate code nobody has, the parcel heading back to the depot. Each of those is a message that either saves a second trip or causes one.
Open →Your login codes, incident notices and renewal nudges sit on the critical path of someone else’s workday. Send them from your own service with a tenant API key, and read the outcome back through the same API.
Open →Education messaging is about timing: a class that moved, a deadline that is close, an enrollment nobody confirmed. The failure mode is not a missing message — it is one that arrives after it mattered.
Open →A marketplace messages two audiences about the same event for opposite reasons: the buyer wants it to arrive, the seller wants proof that it did. That makes the receipt the part worth getting right.
Open →Travel messaging is shaped by the clock: a confirmation that has to arrive immediately, a reminder the evening before, a disruption notice that is worthless once the guest has left for the airport. Send each one from an account that is still accepting traffic.
Open →Field service messaging is measured in minutes: a technician twenty minutes away, a job that moved, a customer who will not be in. Send the ETA when the event happens and it saves a trip; send it late and it is worse than silence.
Open →