These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Salon + Booking + CRM + Inventory
- Features
- Appointments and Customer Context
Appointments and Customer Context
Keep the customer name, appointment interval and accountable team member together through the booking lifecycle.
OverviewHeld Bookings×
Salon + Booking + CRM + Inventory · Appointments and Customer Context
New
Held Bookings
Confirmed waits for the front desk
| Record number | Customer name | Starts at | Ends at | Counterparty | Quoted amount USD | |
|---|---|---|---|---|---|---|
| BKN-90836 | Customer 974 | 23 Oct | 28 Oct | RSR-6320 | 340 | |
| BKN-17642 | Customer 929 | 16 Oct | 21 Oct | RSR-8574 | 880 | |
| BKN-50352 | Customer 898 | 08 Oct | 10 Oct | RSR-3232 | 610 | |
| BKN-57227 | Customer 317 | 07 Oct | 16 Oct | RSR-3800 | 630 | |
| BKN-46434 | Customer 106 | 07 Oct | 12 Oct | RSR-2851 | 240 |
6 of 6 records
Customer 974Bookings · BKN-90836
Starts at23 Oct
Ends at28 Oct
CounterpartyRSR-6320
Quoted amount USD340
Revision90
What you can do
Give the appointment a clear operating context
Front Desk prepares a booking with the customer name and a subject that explains the intended service. The planned start and end give the team a period to review, while the quoted amount records the commercial context. An owner and resource counterparty make the booking recognizable to the people coordinating the appointment.
The booking remains the parent for later service use, payment evidence and supporting files. When Salon Manager reviews a question about confirmation or completion, those links provide the context for the decision. The team can follow the same booking instead of reconstructing the appointment from separate notes held by different people.
How the work is organized
- Appointment preparation. Front Desk confirms the customer name, intended period and resource context. Use a meaningful subject so Service Professional can recognize the planned work when opening the booking.
- Lifecycle review. Requested, Held and Confirmed describe different stages of preparation. The team checks the current state and revision before running the next supported action, especially when the appointment has recently changed.
- Customer context. Supporting files and provider evidence stay linked to the booking. The name helps staff recognize the appointment, while the booking number identifies the specific record being discussed.
What to agree during setup
Agree who owns a booking at each operating stage and how that ownership relates to the person performing the service. Use the organization’s local time convention when preparing appointments. Confirm how an end is determined for the selected service before relying on the interval during resource review.
Set a consistent approach to booking subjects and quoted amounts. The team should know which record to open when a customer asks about a changed appointment or an earlier quote. If customer details arrive from another system, agree the connection and the identifiers used to match the intended booking. Keep the booking number available whenever a common customer name could be ambiguous.
Check the handoff on an actual case
For a rehearsal, prepare separate bookings bearing the same customer name: a haircut from 10:00 to 10:45 and a color service from 14:00 to 15:30. Front Desk records a distinct booking number, subject, owner and resource context for each. Service Professional opens the afternoon appointment and identifies the planned work from its own details.
Attach the confirmation material to the afternoon booking and ask another team member to locate it by booking number. They should be able to distinguish its quote and resource plan from the morning appointment without relying on the customer name alone. Follow that specific booking into its hold and confirmation steps. The handoff is ready when the team can identify the correct appointment, its full interval and the evidence belonging to it.
What your team sees
- Appointment Schedule — Review active bookings with their planned start, end and accountable owner.
- My Bookings — Locate bookings owned by the signed-in team member.
- Booking Board — Follow requested, held, confirmed and in-progress work by current state.
Follow the work through
Continue with Booking request to confirmation and use Resource Holds to review the appointment’s resource requirements.
What it keeps track of
Data model- Bookings
- Appointment bookings with lifecycle, quoted amount and resource counterparty.
- Organizations
- Salon organizations / locations operating within the platform.
- Team members
- Salon staff and platform identities, scoped to an organization.
- Resources
- Bookable salon resources: styling chairs, treatment rooms, equipment.
- Record attachments
- Files attached to bookings as supporting evidence.
Who uses it
Permissions- Front Desk
- , Service Professional, Salon Manager, Auditor, Admin.
- Front Desk
- Prepares the appointment; Salon Manager resolves scope questions; Service Professional follows the planned work.
Set up Salon + Booking + CRM + Inventory your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.