Skip to content
RocketLead Developers

Recurring schedule

A resource’s availability is defined as a continuous recurring schedule — slots on a real calendar grid, not a per-week block. You drag-create a slot, set its recurrence pattern, and the slot extends forward indefinitely (or until you set an end date).

The model is the same one Google Calendar uses for recurring events, which means it inherits one of the same edge cases.

Where to find the schedule editor

Section titled “Where to find the schedule editor”

The resource-availability planner is one click deep. From the Calendar view:

  • Pick the calendar.
  • Open the resource planner (the cogwheel / Einstellungen icon → “Ressourcenplaner” or equivalent).

The planner is not in the daily customer-booking view — that one is for booking actual appointments. Resource planning is a separate, deeper view because most operators only touch it during setup or when schedules change.

Restricted users (Lead Pool members without manager-level access) can’t see the planner. Admins and managers can.

Creating a slot

Section titled “Creating a slot”

Drag on the calendar grid to draw a time block, then:

  1. Pick the resource the slot is for.
  2. Set the start and end times (drag adjusts these; they snap to 5-minute increments).
  3. Choose recurrence:
    • Daily / weekly / monthly presets.
    • Custom — pick specific weekdays for a weekly pattern (e.g. Wed/Thu/Fri only).
  4. Optionally set an end date if the recurrence isn’t open-ended.
  5. Set the max parallel bookings for this slot (overrides the resource-level default).
  6. Tick “Für Interessenten buchbar” if prospects should be able to book this slot via forms. See the gotcha →

Save. The slot appears on the calendar; subsequent weekly repeats show automatically.

The day-of-week edge case

Section titled “The day-of-week edge case”

If you create a slot on Wednesday but configure the recurrence to repeat Monday and Wednesday, the slot’s “first occurrence” matches the start date (Wednesday). Now suppose you go back and change the recurrence to Monday only:

The slot disappears. Not just from future weeks — including from today.

This is because the underlying event’s anchor is its first occurrence, and the recurrence pattern now excludes that anchor. Google Calendar has the exact same behavior; the model is consistent with the iCalendar RRULE spec.

Workaround: if you need to change a slot’s day-of-week pattern, either:

  1. Delete the old slot and create a new one on the correct day, or
  2. Move the slot to a day included in the new pattern before changing the recurrence.

If a slot “vanishes” after a recurrence edit, this is what happened.

Vacations and one-off closures

Section titled “Vacations and one-off closures”

Use the blocker feature for one-off closures (a single day or a date range when the studio is closed). Blockers don’t replace the recurring schedule — they sit on top of it and block availability for the specified period.

To add a blocker: from the resource planner, click “Blocker hinzufügen” (or equivalent), pick the date range, and choose:

  • All resources — for a full studio closure.
  • Specific resources — for a single coach’s vacation, a single room being repainted, etc.

Blockers are the closest thing the platform has to “vacation mode” today. There’s a planned automation node that will check the blocker calendar and route around closures in email flows, but it’s not built yet.

Schedule changes mid-quarter

Section titled “Schedule changes mid-quarter”

When a customer’s schedule changes (typical seasonal swap):

  • End the old slot by setting its Until date to the last day the old schedule is valid.
  • Create a new slot starting the day after, with the new times.

Don’t edit the existing slot’s times in place if past occurrences should retain the old times for analytics or audit purposes — edits are retroactive across the recurrence.

What’s next

Section titled “What’s next”