How to Set Booking Rules for Different Services
Build a service rule sheet, configure durations and providers in Niwa, and test the appointments that should fit or be refused.
Set booking rules for different services by defining each service's duration and eligible providers, then applying the hours, breaks and other constraints those providers work under. Use a written rule sheet before configuring the software, so the customer-facing description agrees with what the schedule can accept.
In Niwa, service duration and staff assignment are configured per service. Working hours and breaks belong to the team member, while the booking buffer is a shared scheduler setting. These distinctions affect how you design the schedule.
Make a service rule sheet
For each service, record its purpose, duration, eligible providers, location and any preparation the customer needs. Add the route for requests that require discussion before a date can be agreed.
Use a separate service when the commitment changes materially. An introductory consultation, a full session and a short follow-up should not share one vague appointment type if their duration or eligibility differs.
Here is an illustrative rule sheet for a small advisory business:
- Introductory consultation: 30 minutes, provided by either advisor.
- Detailed planning session: 60 minutes, provided by the senior advisor.
- Existing-client follow-up: 20 minutes, provided by the customer's assigned advisor.
Those definitions give the scheduler usable facts. The service page should also explain the difference, so a customer does not choose the shorter follow-up expecting a full planning session.
Configure duration independently of slot spacing
Enter the actual service duration. The spacing between displayed starting times is a separate concept; a calendar showing half-hour starts does not mean every appointment lasts 30 minutes.
A 60-minute visit needs a continuous hour within its provider's working period. It should not begin 30 minutes before closing merely because that starting time appears on a general timetable.
Check the service definition after editing its public description. If you change what is included and the work now takes longer, review both the appointment duration and the available times.
The Niwa booking workflow uses the configured duration when checking the proposed reservation. Keep that duration tied to the service the customer actually selects.
Assign only eligible team members
Save the people who provide appointments and assign the relevant services to them. An employee's open time should be offered only for services they can deliver.
Use the member's working hours for their real appointment periods, rather than copying the business's opening hours indiscriminately. Add recurring breaks and excluded dates for holidays or planned absences.
If a service is only offered by one specialist, that specialist's availability determines its options. If either of two advisors may handle a service, test both assignments and check who appears in the saved appointment.
A day restriction applied through a member's hours affects their other assigned services too. If your business needs a service-specific schedule that differs from the same provider's other services, discuss that requirement during configuration instead of assuming a staff-hours edit applies to only one service.
Account for turnaround time
Some appointments require time afterward for notes, cleaning or preparation. Include that time when designing the workday.
Niwa's inspected scheduler has a shared booking buffer. Choose it with the whole service catalogue in mind and test shorter as well as longer appointments. Do not describe that shared setting as an independently configurable buffer for every service.
Products offer different rule structures. Acuity, for example, documents padding between appointments. Google's appointment schedules have their own buffer and availability controls. Use those instructions only when configuring those products.
If one service needs substantially different preparation from the others, identify that requirement in the rule sheet. It may need a different scheduling arrangement; shortening the customer visit to hide the preparation time makes the service definition misleading.
Separate scheduling rules from business policy
A rule the software enforces should be tested in the booking flow. A policy that staff handle personally should be explained with the correct contact route.
For example, a project consultation may have a fixed duration but still require the owner to assess whether the enquiry is appropriate. A recurring class has capacity and attendance rules beyond a one-person appointment. Describe those needs explicitly when choosing the implementation.
Publish prices, change deadlines and preparation instructions where customers make their choice. Do not let an assistant invent exceptions or turn an unconfirmed enquiry into a promise.
The Niwa setup guide helps connect the assistant to approved service information. Check an ambiguous customer question to see whether it leads to the correct service and next step.
Test the rule sheet as a set of examples
For each service, test one appointment that should fit and one that should be refused. Use a long visit near closing, a restricted provider, a recurring break and an excluded date.
Inspect the saved service, provider, duration and timezone after a valid test. Check that the required contact fields and confirmation make sense for that service.
When staff hours or service scope changes, update the rule sheet and recheck the affected cases. The sheet becomes a practical handover reference for whoever maintains the schedule.
Bring three representative services to a Niwa demo. Include the appointment lengths, eligible staff and preparation time so the booking rules can be reviewed against the work you deliver.
