Arrival intervals — fixed time-slot labels for booking
Arrival intervals let you define fixed time windows and give each one a custom label — for example "10:00 – 11:30" or "Afternoon". When a customer books, Hubhus suggests exactly one slot per interval, and the label is what gets communicated, not the exact event start time.
TL;DR
Create an arrival interval set under Calendar settings → Arrival Intervals. Set the number of intervals, adjust the time boundaries, and add a label for each. Then enable it on the booking form: Slots → Use arrival intervals: Yes → select your set.
Get started in 4 steps
Create an arrival interval set
Go to Calendar settings → Arrival Intervals and click + New arrival interval set. Give it a name.
Set the number of intervals and boundaries
Choose how many intervals per day (e.g. 4). Use the timeline slider to set the boundary between each interval. Intervals can be unequal — for example 07:00–09:00, 09:00–13:00, 13:00–17:00.
Add a label for each interval
Enter the label that customers will see for each interval — for example Tidsrummet 10:00 – 11:30 or Morning. This label is what appears in booking confirmation and communications, not the exact event start time.
Enable on the booking form
Open your booking form and go to Slots. Set Use arrival intervals to Yes and select your arrival interval set under Arrival set.
Read more⌄
How arrival intervals work
- A calendar event always has a specific start time and end time.
- The start time of the event (e.g. 10:15) is matched against the intervals you defined.
- The label for the matching interval is what gets communicated to the customer — not the exact start time.
- In booking, only one time slot per interval will be suggested.
Example: you define an interval covering 10:00–11:30 with the label Morning slot. A customer who books an event starting at 10:15 will see "Morning slot" in their confirmation, not "10:15".
Multiple arrival interval sets
You can create multiple sets with different interval configurations — for example one set for a morning-heavy service and another for an afternoon service. Each booking form selects which set to use independently.
One set can be marked as Default. The default set is pre-selected when enabling arrival intervals on a new booking form.
Interval configuration reference
| Field | Description |
|---|---|
| Name | Internal name for the set — visible in the booking form selector |
| Number of intervals | How many time windows per day (e.g. 2, 3, 4) |
| Interval boundaries | Drag the timeline slider to set where each interval starts and ends. Intervals do not need to be equal. |
| Interval label | The text shown to customers for each interval. Can be any string — e.g. Tidsrummet 10:00 – 11:30 or Morning. |
| Is default | Marks this set as the default for new booking forms |
Migrating from legacy interval slots
If you previously used the Start time intervals count (legacy) setting on a booking form, Hubhus shows a warning that these settings will be unsupported in the future. To migrate:
- Create an arrival interval set under Calendar settings → Arrival Intervals that matches your existing time windows.
- On the booking form, set Use arrival intervals to Yes and select your new set under Arrival interval set.
Once an arrival interval set is selected, the legacy settings are disabled and cannot be re-activated. The legacy interval labels used the placeholders %event_start_time_interval_from% and %event_start_time_interval_to% — with the new arrival intervals these are replaced by your fixed custom labels.
Booking form settings
| Setting | Value |
|---|---|
| Use arrival intervals | Yes / No |
| Arrival set | Select which interval set to use for this booking form |
Each booking form configures arrival intervals independently. Different forms can use different sets.
Common searches
arrival interval • time slot • booking time window • interval label • ankomsttid • tidsrum • arrival set • booking form slots
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article