Recurrence and exceptions in Nebulas Calendar: how appointments and schedules stay consistent

01

What changes for those planning repeated appointments

Nebulas Calendar coordinates operators, resources and appointments across multiple calendars, keeping working hours, slots, recurrences, business relationships and notifications linked as the schedule changes. This means a repeated series stays readable in day, week, month and agenda views, and conflicts between occurrences are flagged before confirmation.

02

How a recurrence works

Steps

1. Set the cadence: daily, weekly, monthly or yearly.
2. Apply a custom rule when the standard cadence isn't enough.
3. View the preview of occurrences generated by the series.
4. Choose the edit scope: single occurrence or entire series.
5. Add an exception for events that need to differ from the rule.

03

What you need before creating a series

Prerequisites

• A calendar configured for the operator or resource involved.
• Working hours and configurable slots already defined in the calendar.
• Notification channels enabled (email, WhatsApp, SMS) if reminders are needed.
• Customer, product or participant records linkable to the event.

04

Hypothetical example: a weekly treatment with a break

Hypothetical example: a salon schedules a treatment every Tuesday for six weeks on a calendar representing the operator. In the fourth week a closure is needed: an exception is created on the single occurrence, while the others remain managed by the series rule. The week view shows the load and the overlap check flags any conflicts before confirmation.

05

How to check a series after creation

• Text and date-range search to find specific occurrences.
• Filters by calendars, records and status to isolate a series.
• Availability reports to check the time occupied by the series.
• History and audit trail to reconstruct changes to occurrences or exceptions.

06

What Nebulas Calendar actually does

Nebulas Calendar distinguishes a single occurrence from a series through explicit edit scopes, so a change to one event doesn't unintentionally alter other dates. Preview and custom rules make the effect of a recurrence visible before saving it, while exceptions allow handling cases that depart from the standard rule.

07

Recommended operational flow for a new series

Steps

1. Create the event on the correct operator's or resource's calendar.
2. Link customer, participants, product and relevant notes to the event.
3. Set the cadence and check the preview of generated occurrences.
4. Configure the channel, recipient and template for reminders.
5. Add exceptions as variations to the series emerge.

08

Next step

If you manage repeated appointments with customers or resources, try setting up a series in Nebulas Calendar with preview and a defined edit scope, so you can immediately see how any conflicts are flagged.