Preserve the original customer request
Keep requested service, preferred time, staff preference, contact route and supplied context without marking the appointment confirmed.
Workflow blueprint
A CRM booking system that never confuses a request with a booking
An appointment handoff blueprint for salons that keeps customer context while a controlled record owns the accepted person, service and time.
Explain reliable request and confirmation states while excluding public booking, calendar sync, automated availability, reminders, deposits, no-show scores and commission calculations.
TL;DR — Explain reliable request and confirmation states while excluding public booking, calendar sync, automated availability, reminders, deposits, no-show scores and commission calculations.
Review resources and operating conditions
Confirm duration, qualified person, location, preparation, conflict state, price basis and cancellation terms before offering a slot.
Record explicit customer confirmation
Create the appointment only after the customer accepts the offered service, person, place and time through the agreed communication route.
Control later revisions as proposals
Retain the confirmed version while a requested move receives another conflict check and customer decision before becoming current.
Page-specific decision aid
An appointment-request, confirmation and customer-context handoff slip
The slip follows a Saturday colour-treatment request with a stylist preference. The salon offers another qualified person, preparation note, duration, price basis and 10:30 slot; the customer accepts. A later move request stays proposed until resource conflicts are checked again and the customer confirms the replacement.
- ✓A preferred time is not reserved capacity.
- ✓The accepted slot owns the booking state.
- ✓Relationship reminders and promotions need different communication purposes.
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Request and confirmed appointment remain distinct states
- ✓Resource review identifies service duration and qualified person
- ✓Revisions preserve the earlier agreement until reconfirmed
- ✓Public booking, sync, reminders, deposits and commissions excluded
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow