Service – Add · Edit · Delete

Quick overview: what should you look at first?

• If you want to start quickly: fill in at least the Name, Type, Capacity, Duration, and Active status fields.
• If you need precise operation: set preparation time, buffers, and deadlines separately.
• If you manage a group service: enable the waitlist and set the offer expiration.
• If you have a monthly cycle service: the monthly batch block fields define the allocation logic.

Concept clarification: Preparation time vs. Buffer before

At first glance, the two fields may look similar, but they serve different purposes:

• Preparation time (prep_minutes): the operational preparation of the service (e.g. equipment setup, administration, room preparation). This is a professional “preparation block.”
• Buffer before (buffer_before): a calendar protection gap. It prevents the system from allowing bookings too close to each other.

In short: preparation time = what you do before the session, buffer = how much empty space you keep in the calendar for safe operation. The same applies to the buffer after field: it protects the time needed for wrap-up or transition.

Creating and editing a service — field by field

1) Basic data

• Name: this is what the customer sees on the booking page. Keep it clear and short.
• Technical name (slug): identifier used in URLs and internal references. It is generated automatically from the name but can be edited.
• Public description: short text shown on the customer-facing page.
• Internal description: admin-only note (operational details, internal rules, training notes).
• Type: Single / Group / Monthly batch. This determines which extra fields appear and which booking logic runs.

2) Group-specific fields

• Enable waitlist: when fully booked, interested users can join a waitlist.
• Waitlist algorithm: strategy for assigning newly available seats.
• Offer expiration (minutes): how long a released seat can be reserved.
• Auto-approve waitlist offers: after acceptance, the booking can be finalized without a manual admin step.
• Seats per email: limit on how many seats one email address can take for the same event.

3) Monthly batch-specific fields

• Response window (days): how long participants can respond to the monthly proposals.
• Maximum desired count: upper limit of sessions a participant can request per month.
• Allocation algorithm: greedy or more even (spreader) distribution.
• Base weight: influences how strongly the algorithm favors even distribution.
• Distribution cooldown scale: how strongly it avoids too dense allocation in a short period.

4) Timing and capacity fields (key for all types)

• Capacity: number of customers who can book the same time slot.
• Duration (minutes): length of the bookable time slot.
• Preparation time (minutes): time reserved for professional preparation before the start.
• Buffer before / after (minutes): calendar protection around the slot.
• Minimum booking notice (minutes): limit for last-minute bookings.
• Max advance booking (days): how far ahead customers can book.
• Reminder offset (minutes): how long before the session the reminder is sent.
• Cancellation / Reschedule deadline (minutes): business rule for changes.
• Post-booking redirect URL: optional landing page after successful booking.
• Allow overbooking: allows bookings above normal capacity.

5) Public view and communication

• Public theme: display style (light/dark/custom).
• Public accent color: color for visual highlights (HEX format).
• Public message: informational text on the booking page.
• Confirmation message: message shown after booking.
• Confirmation email text (HU/EN/DE): language-specific additions to the system email, with shortcodes.

6) Status and additional fields

• Indefinite duration: no predefined end date.
• Arrival time required: separate arrival data is required.
• Public price + currency: price shown to the customer (e.g. 12000 HUF).
• Active: only active services are operational and bookable.

Mandatory check before deletion

Before deleting, check whether there are active or future bookings for the service. If so, it is usually better from a business perspective to deactivate it (turn off is_active), because this keeps past data and reports consistent.

Recommended configuration patterns

• 1:1 consultation: capacity=1, slot=60, prep=10, buffer_before=5, buffer_after=10.
• Group session: type=group, capacity=12, waitlist_enabled=yes, max_per_email_event=1–2.
• Monthly club: type=monthly_batch, response_window_days=3–7, desired_count_max according to business limit.