# Configure a service for online booking

> Turn on online booking for a service and set duration, buffers, limits, notice, hosts, location, deposits, cancellation policy, reminders, and intake questions.

- Product: Workspace369
- Documentation version: 2026.3
- Section: Scheduling
- Last updated: 2026-10-26
- Canonical source: https://docs.workspace369.com/v/2026.3/scheduling/configure-a-service-for-online-booking/

---

To let clients book a service, open it in **Products**, choose **Configure booking** and turn on **Accept public bookings**. Duration, buffers, notice, hosts, location, deposits and reminders are all set on the service.

Every rule that shapes an online booking lives on the service itself: how long it takes, who can deliver it, where it happens, whether the client pays up front, and what they must tell you. Booking pages only choose which of these services to show, so configure the service first.

## Open a service's online booking settings

1. Open **Products** and select a service-type product. Physical and digital products cannot be booked online.
2. On the product, open **Configure booking**.
3. Turn on **Accept public bookings**.
4. Work through each section below, then save.

Once booking is on, the product card's switch reads **Accept bookings**. Turn it off to stop offering the service online.

## Set the appointment basics

| Setting | What it does |
| --- | --- |
| Service Duration | How long the appointment lasts and how much calendar time it blocks |
| Slot interval | How far apart the offered start times are |
| Buffer before / Buffer after | Time kept free before and after each appointment so consecutive bookings do not touch |
| Minimum notice | How far in advance a booking must be made; times inside this window are not offered |
| Booking window | How far into the future the calendar opens |
| Daily limit | The most bookings one team member takes per day (0 = none) |
| Weekly limit | The most bookings one team member takes per week, Monday to Sunday (0 = none). It counts every appointment assigned to that person that week, not just this service's; once reached, the page stops offering their times until the next week and other hosts keep theirs |
| Minimum Quantity and Maximum Quantity | The lowest and highest quantity one booking can cover. Turn on **Allow Clients to Select Quantity** to let clients choose it themselves |

## Choose hosts and routing

Under **Hosts & Routing**, choose who can deliver the service in **Booking hosts**: **All eligible** teammates or **Specific people**. Availability is calculated from each eligible host's hours, so a service with no eligible hosts offers no times. A host's approved time off and workspace holidays, both set in **Time off** settings, block bookings on those days automatically, and every calendar event assigned to a host blocks the time it covers. An event with no assigned team member still blocks that time — for whoever created it, or for the workspace owner when the creator can't be determined — but it does not count toward the host's daily limit. New events you create in the app are assigned to you by default, so they block your own availability right away; clear the **Assign to** field to make an event a shared, unassigned block instead.

A host can also let their own Google calendars protect their booking times. Each host connects their own Google Calendar from the calendar's menu (see [Connect Google Calendar](https://docs.workspace369.com/v/2026.3/scheduling/connect-google-calendar/)), chooses the writable calendar that should receive Workspace369 bookings, then chooses up to 10 calendars whose busy events should block times on every booking page they host. Events marked **Free** do not block anything — which includes all-day events, since Google marks those Free by default, so switch an all-day event to **Busy** if it should keep bookings off that day. Google events block time but never count toward a host's daily booking limit, and calendar-selection changes take effect on availability within a minute.

**Automatic assignment** decides who receives a booking when the booking page assigns hosts automatically:

| Strategy | Behavior |
| --- | --- |
| First available | The booking goes to the first eligible host who is free at the chosen time |
| Round robin | Bookings rotate across eligible hosts so the work is shared evenly |

Set **Approval** to **Always**, or to **On these days** to choose the weekdays, when a person should look at each booking before it is final. Bookings on those days wait for your approval and the calendar event stays tentative until your team confirms it from the **Bookings** tab. Other days book instantly. **Never** books instantly every day. Days follow your workspace time zone.

When a service uses **On these days**, each time on the booking page carries a small **Instant** or **Request** tag, so clients know before they pick whether the time is confirmed straight away or sent to your team as a request.

### Set the dates a service can be booked

Under **Bookable dates**, set **From** and **Until** to offer a service only for a season, a promotion or a limited run. Both dates are included and follow your workspace time zone. Leave **From** empty to start now, or **Until** empty for no end date. Outside those dates the booking page shows no times for the service, and a booking or reschedule into them is refused. Blackout dates still work inside the range for single days off.

## Set the location

Choose where the appointment takes place: In person, Phone, Google Meet, or Custom.

For Google Meet, the host must have connected Google Meet to their account; the meeting link is then created automatically for each booking. See [Integrations and API](https://docs.workspace369.com/v/2026.3/admin/integrations-and-api/).

**Location details** sits under the location choice and holds up to 500 characters describing it. What to enter depends on the location type:

- **In person**: the address.
- **Phone**: what the client should expect, for example "We call you" or the number to dial.
- **Google Meet** and other video providers: leave it empty to use the automatically generated link, or paste a fixed link or instructions instead.
- **Custom**: whatever free text describes the location.

This field is public. It shows on the booking page under the service name and again on the confirmation, appears as the "Where" line in the confirmation and reminder emails, and becomes the location on the calendar invite and the calendar event. Leave out anything you would not want a client to read.

## Take a deposit or full payment

| Option | What the client pays at booking time |
| --- | --- |
| **No payment required** | Nothing; the booking is confirmed or queued without a payment step |
| **Deposit required** | A fixed amount or a percentage of the service price, in the currency you choose |
| **Full payment required** | The whole service price |

Deposits and full payments are collected through Stripe. Connect Stripe first — otherwise visitors see an error at checkout. When a payment is required, the client's slot is held for 30 minutes while they pay. If the payment does not complete in time, the hold expires, the time is released, and the request is marked expired and leaves the Requests list.

Refunds are automatic in four cases: the client cancels within the service's cancellation policy, your team cancels the booking from the Bookings tab or the calendar, your team declines the booking, or the payment arrives after its hold had already expired. The full payment goes back to the original payment method and takes 5–10 business days to appear. Automatic refunds are always for the full payment. The one automatic refund you control is a team cancellation, where **Cancel booking** lets you turn the refund off. To refund only part of a payment, refund it in your Stripe dashboard; Workspace369 picks up the refund on the booking and its invoice. See [Manage booking requests](https://docs.workspace369.com/v/2026.3/scheduling/manage-booking-requests/).

## Set the client policy

Decide what a client can change after booking:

- Whether the client can cancel (**Allow client cancellation**), and the notice a cancellation needs. **Cancel notice minutes** is counted in minutes; the default, 1440 minutes, is 24 hours.
- Whether the client can reschedule (**Allow client rescheduling**), and the notice a reschedule needs. **Reschedule notice minutes** works the same way and also defaults to 1440 minutes.

Both actions are offered through the manage link in the client's confirmation email. Once the notice window has passed, the client can no longer cancel or reschedule from the manage link.

## Configure notifications

- **Email clients**: whether the client receives booking emails such as the confirmation with its manage link.
- **Email assigned teammate**: whether the assigned host receives an email for each new booking, and again when the client cancels or reschedules through their manage link. Only the host receives it, not the whole team.
- **Reminders**: when reminders reach the client before the appointment. Pick one or more chips: 7 days, 2 days, 1 day, 3 hours, 1 hour, 30 min and 15 min. Choose **Other** to add your own in minutes, hours or days, up to 7 days. The defaults are 1 day and 1 hour before; adjust them to suit the service.
- **Text message reminders**: sends the same reminders by text message to the client's phone number, when it was entered with a country code (for example +1 …). Texts are paid from the workspace's Token balance. Off by default.
- **Require bot protection**: asks the client to complete a short Cloudflare Turnstile check before the booking can be submitted. Turn it on if you receive spam or automated bookings. Off by default.

## Add intake questions

Add the questions the client must answer when booking. Each question has a label and a type: `text`, `textarea`, `email`, `phone`, `number`, `select`, `multiselect`, or `checkbox`. The `select` and `multiselect` types take a comma-separated list of options for the client to choose from. Mark a question required so the booking cannot be submitted without it. Answers are captured with the booking.

## Add blackout dates and public instructions

Blackout dates remove whole days from the service's availability, such as dates when the service is not offered, without changing anyone's working hours. Workspace holidays and each host's approved time off already block their days automatically, so blackout dates are for days specific to this service.

Public instructions are the notes clients see for this service: what to bring, where to park, how to prepare.

## Verify on the booking page

1. Open **Booking pages** and make sure a page includes the service. See [Create and share a booking page](https://docs.workspace369.com/v/2026.3/scheduling/create-and-share-a-booking-page/).
2. Open the page's public link in a private browser window.
3. Choose the service and confirm that the duration, price, offered times, and questions match what you configured.
4. Make a test booking with your own email address, then decline it from the Bookings tab or cancel it through the manage link in the confirmation email.

Continue to [Create and share a booking page](https://docs.workspace369.com/v/2026.3/scheduling/create-and-share-a-booking-page/).

> Deposits and full payments need a connected Stripe account. Google Meet links are created only when the assigned host has connected Google Meet.
