Reminders that arrive at the right moment: how Nebulas Calendar manages notifications and channels

01

A reminder is not a generic message

Nebulas Calendar notifications use the event's data and its linked subjects, not fixed text disconnected from context. Channel, recipient, template and send timing are configurable for email, WhatsApp and SMS when those channels are enabled. This means a reminder can show the real customer, product or note from the appointment, not an empty formula.

02

How a reminder flow is built

Steps

1. Link relevant customers, participants, products and notes to the event.
2. Choose the channel among email, WhatsApp and SMS, if enabled.
3. Define the correct recipient among the subjects linked to the event.
4. Choose the message template suited to the appointment type.
5. Set the send timing relative to the event's time.

03

What's needed before activating notifications

Prerequisites

• Communication channels (email, WhatsApp, SMS) actually enabled.
• Events with linked subjects: customers, participants, products, notes, status.
• Message templates ready for the different appointment types.

04

A hypothetical case: recurring appointments with differentiated reminders

Hypothetical example: a company manages weekly recurring appointments across multiple calendars, one per operator. It sets an email reminder the day before and an SMS two hours before, both built on the event's and linked customer's data. Day, week and month views remain readable while channel, recipient, template and send timing stay configured for each reminder, tied to the event's real data.

05

How to verify everything works

• Text search and filters by calendars, records and status to isolate a specific event.
• Availability reports to check conflicts before confirming the appointment.
• History and audit to find the event and reconstruct changes made to its configuration.

06

What Nebulas Calendar concretely configures

Nebulas Calendar links each calendar to an operator or a resource and each event to the subjects involved: customers, participants, products, notes, status. On this basis notifications become configurable by channel, recipient, template and send timing, across email, WhatsApp and SMS when channels are active. Working hours, slots, daily indicators and overlap checks remain available as separate functions to check availability and flag conflicts before confirming the appointment.

07

Practical sequence to activate a reminder

Steps

1. Check which channels (email, WhatsApp, SMS) are enabled for the organization.
2. Link the correct subjects to the event: customer, participant, product, note.
3. Set template, recipient and send timing for that event type.
4. Check the slot with overlap indicators before confirming.
5. Use history and audit to find the event and reconstruct changes made to the reminder's configuration.

08

The next step

If your schedule generates missed appointments or out-of-context communications, the problem is often not the calendar but the missing link between the event and real data. Map out which subjects to link to each event and which channels to enable before setting up reminder templates.