Frequently asked questions.

Texting patients is allowed when it is done carefully. In practice that means minimising what goes into the message, having a BAA in place with your vendor, honouring the patient's stated preferences, and being able to show later what was sent and why. Remind is built around those four things: reminder templates default to the minimum useful detail, the BAA is signed at signup, consent is a ledger, and every send is recorded.

Included at every tier, signed inside the signup flow rather than negotiated afterwards. The agreement text, your signature, the signing IP and a hash of the document are stored together as an append-only record.

Appointment reminders sit in a different bucket from marketing messages, but you still need a defensible record of what each patient agreed to. Remind keeps consent as an append-only ledger — every grant, pause and opt-out with its timestamp — so months later you can answer exactly why a given patient did or did not get a message. We are not your compliance counsel; we give you the evidence trail.

The opt-out is recorded against that patient immediately and future reminders stop. The record stays in the consent ledger rather than being deleted, so the reason is visible later, and staff can see the patient opted out rather than assuming a delivery failure.

This is the question we built the product around. A reconcile sweep runs continuously: when an appointment is cancelled, every reminder still queued for it is cancelled with it; when one is moved, its reminders are retimed against the new slot. It is not limited to a horizon of a day or two — it reconciles the whole queue, which is why a patient never gets reminded about a visit they already cancelled.

You set the offsets per rule — a common pattern is one a few days ahead and one the day before. Quiet hours are enforced regardless: nothing sends between 21:00 and 08:00, and a reminder that would have fired overnight waits for the morning instead.

On Growth and above, replies come into a staff inbox and are recorded against the appointment, so a confirmation shows up as a confirmation rather than as a phone call the front desk has to field.

Yes, WhatsApp is a first-class channel alongside SMS and email, selectable per reminder rule. It is unusual in this category — most reminder platforms offer SMS, voice and email only.

Yes — because it does not require an integration. Remind reads a schedule export: type appointments in by hand, upload a CSV, or have your system drop a file into an SFTP folder we scan every five minutes. Practices with a live HL7 SIU/ADT feed can use that instead on Growth. If your system can produce a schedule, you qualify.

You can import this week's schedule and have reminders queued the same afternoon. There is no integration project to schedule and no vendor approval to wait for.

No. Remind sends from its own number and does not touch your phones. Some platforms in this category bundle reminders with a phone system replacement; this one does not.

No cap and no meter. Reminder volume follows your schedule. Monthly SMS allowances are common in this category — a few thousand messages per tier — and we deliberately did not do that.

No, it is flat per practice: $99, $199 or $299 a month. Adding a clinician does not change your bill. Per-provider pricing is the category norm, at roughly $50 to $200 per clinician per month.

No. Month-to-month, no setup fee, and your patient and appointment data stays exportable if you leave.