%20(1300%20x%20200%20px).png?width=450&height=69&name=Short%20Haircut%20Photo%20Banner%20Email%20Header%20(1300%20x%20300%20px)%20(1300%20x%20200%20px).png)
Guests can now be charged a Request or Non-request (base) price for their services. A service not marked as Request, will be charged at the base price, as configured for the Default/None level. A service marked as a “Request” will be charged at the employee’s level price.
Related configuration
Configuration options for Request/Non-Request functionality are found in Setup > Configuration > Sales > Point of Sale Setup.
Default employee bookings as Requests: If you would like to automatically mark appointments made directly within employee time slots as Requests, check the ‘Default employee bookings as Requests’ setting ON.
If you would like to manually mark appointments as Requests, leave this setting OFF.
Pricing for Non-Requested Employees: If you would like to charge base pricing (configured as the Default/None level) for all Non-Requested employee services, choose ‘Base Pricing’.
If you would like to charge services in the traditional manner of using an employee’s Level price, choose ‘Level Pricing’.
Marking services as Requested or Non-Requested
In all scenarios where non-request bookings or check-ins are initiated, Shortcuts will fairly allocate employees based on a new ‘round-robin’ approach. See “Fair allocation of employees for non-request services” below for more information.
Appointment Book: Making a booking within an employee’s time slot within the Appointment Book, will now check your ‘Default employee bookings as Request’ setting to determine whether this should be automatically marked as a Request or not.
You can now also initiate a booking with any employee (Non-request) by clicking on the preferred time on the left side of the Appointment Book.
Walkin Manager: Continued ability for an operator to check-in a walkin guest with the next available employee (Non-request) OR with a specific employee (Request).
Online Booking: The “Any” employee option will be considered a Non-request, where the base pricing will be used. A specifically chosen employee will be considered a Request by default.
Self Check-in: The “Next available” employee will be considered a Non-request. A specifically chosen employee will be considered a Request by default.
A new “Request” checkbox on the Service Selection screen will allow operators to change between a Non-Request or Request employee as required.
Notes:
- On a given day, if a guest has multiple services with the same employee, changing any of those service’s Request/Non-Request status with that employee will automatically update the other services for that employee also.
- When upselling (adding) an extra service via the Appointment Book, Walkin Manager or Point of Sale, it will take on the same Request/Non-Request status of the services already assigned to the employee within that visit.
Identifying requested employees
Requested appointments and Walkins will be clearly marked as “REQ” in the Appointment Book and Walkin Manager, to differentiate Request vs Non-request bookings. Please note, these are different to the traditional “Tags”, so you may want choose to change the way you currently use tags when making bookings to take advantage of this new feature.
Fair allocation of employees for non-request services
Shortcuts has implemented a new round-robin approach to fairly allocate an employee for any booking where ‘Any employee’ is chosen, including initiating a booking from the Appointment Book time bar. Shortcuts will rotate through employees who are free during the requested time slot.
Example:
I have 3 employees - Jane, Sarah and Chris. The bookings referred to below are all for non-request bookings. All employees are free in all time slots mentioned below.
Jane is assigned for booking 1. If Jane, Sarah & Chris are free in the time slot for booking 2, it will assign Sarah. Then it will assign Chris for booking 3. It will then rotate through again, choosing Jane for booking 4. Booking 5 is then for a time slot where Jane is already busy, so it would allocate Chris.