Skip to content

Productivity

Automated Notifications & Reminders

Notifications go out automatically, and every send is logged with its channel, status, skip reason and service response.

For most teams the hard part of automated messaging is not setting it up — it is noticing when a message failed. A notification that dies quietly is a patient who never received the information they were waiting for. MoonCRM records every notification with its type, variant, channel and status, and keeps the skip reason, the service response and the error message when something goes wrong. Whether the send was automatic or triggered by a user is recorded too.

What you can do

  • Sends driven by notification type and variant
  • Channel and status recorded per send
  • Skip reason stored in its own field
  • Request body, HTTP status code and response body logged
  • Error messages retained for troubleshooting
  • Automatic vs. manual trigger with the triggering user
  • Active/inactive reminders set from the patient record
  • Daily automatic summary report delivered to managers

Highlights

Delivery record

The request sent, the HTTP status code returned and the response body are stored for every notification, so a failed message can be traced to where it broke.

Skip reason

When a notification is skipped, the reason is written to the record — a missing phone number or a repeated send is read, not guessed at.

Automatic or manual

Whether the system or a person triggered the notification, and which user it was, is kept on the record.

Consultant reminders

Reminders are set from the patient card with a date and a note; the active ones become the consultant’s follow-up list.

Getting started

Setup takes three steps

An implementation specialist works with you at every step. No technical team required.

  1. 1

    Prepare your templates

    Define the WhatsApp, email and SMS templates your notifications will use.

  2. 2

    Configure the daily report

    Set up the daily summary and its recipients in settings so the numbers go out on their own.

  3. 3

    Read the logs

    Review skip reasons once a month — a recurring reason is usually a fixable gap in your data.

Frequently asked questions

Our team knows medical tourism operations inside out. Let’s review your process together in a 15-minute call.

All questions

How do I know whether a notification went out?

The notification record keeps the status, the channel, any skip reason, the request sent to the service and the HTTP response — open the record and read it.

Can I trigger a notification manually?

Yes. Manual sends are logged the same way, and the record shows both that it was manual and which user triggered it.

How do reminders work?

A consultant activates a reminder on the patient card with a date and a note, and it surfaces on their follow-up list on that date.

See Automated Notifications & Reminders in action

In the demo we walk through this module against your own process. Thirty minutes, no sales pressure.