Receivers overview
Who receives the service — person and car receivers, and how they connect to bookings.
A receiver is who or what a booked service is performed on — for example a client, family member, or car.
Receiver types today
ServEase currently ships with two receiver detail types (more will be added soon):
| Type | Typical use | Details |
|---|---|---|
| Person | Client, family member, student, patient | Person receiver |
| Car | A single vehicle for bays, valet, or MOT-style services | Car receiver |
Need another receiver model (for example equipment)? Contact ServEase Support — additional types can be enabled per workspace.
The power of receiver types is that each collects structured data your business needs at booking time — person contact details, car make/model/registration, and similar — instead of free-text notes.
How receivers connect to services
When an admin creates or edits a service, the Offer step sets how many receivers a booking may include — for example a single receiver, multiple receivers, or tiered multi-booking discounts based on receiver count.
Customers and staff pick receivers from the customer profile (or create new ones) during booking.
Can bookings have no receivers?
- Services can be configured with no receiver requirement (
max_receiversnot set) for flows that do not need a person or car on the booking. - The admin booking UI normally expects at least one receiver when the service requires them.
- Off-system bookings may use internal placeholders — self-serve customer flows are designed around meaningful receiver selection when your service asks for it.
Why receivers matter for booking
- Pricing and discounts can depend on receiver count (multi-booking tiers).
- Questionnaires and skills can target specific receiver types.
- Reports group volume and revenue by receiver.
Manage receivers
- Admin: Manage receivers — Receivers in the sidebar.
- Customer profile: Customer receivers.