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
- Completion and Exceptions
Completion and Exceptions
Read each operation's outcome and reconcile the booking with its linked service and evidence records.
OverviewOperation Outcomes×
Salon + Booking + CRM + Inventory · Completion and Exceptions
New
Operation Outcomes
Operation receipts
| Parent | Action | Operation key | Expected revision | Result state | Occurred at | |
|---|---|---|---|---|---|---|
| BKN-15258 | ACT-580 | OK-682 | 600 | Pending | 17 Oct | |
| BKN-76277 | ACT-783 | OK-195 | 880 | Completed | 27 Oct | |
| BKN-23172 | ACT-605 | OK-121 | 250 | Failed | 23 Oct | |
| BKN-11277 | ACT-291 | OK-398 | 780 | Needs review | 17 Oct | |
| BKN-13894 | ACT-818 | OK-310 | 80 | Pending | 25 Oct |
6 of 6 records
ACT-580Operation receipts · OR-95402
PendingParentBKN-15258
Operation keyOK-682
Expected revision600
Occurred at17 Oct
Effect referencesER-108
What you can do
Review the action behind the outcome
A booking can have several guarded actions during its operating cycle. Holding the interval, confirming the appointment and closing service use each produce an outcome to inspect. Operation receipts identify the action and expected revision, with effect references and a failure reason where relevant. Salon Manager uses that context when deciding what needs follow-up.
The receipt states are Pending, Completed, Failed and needs review. A completed operation should be interpreted in relation to the action it records. Reconciliation is a separate command that reads the booking and its linked effects before marking verified completion and recording the reconciliation outcome. Auditor follows that result alongside the underlying records.
How the work is organized
- Outcome inspection. Front Desk and Service Professional inspect the receipt for the action they ran. The parent booking and expected revision help them distinguish the relevant result from an earlier attempt.
- Exception follow-up. Salon Manager reviews failed or review-needed operations using their reason and available references. The team identifies the required correction before choosing a supported retry or successor action.
- Completion reconciliation. Salon Manager runs the reconciliation command for the booking and its linked effects. Auditor follows the resulting receipt together with service use, independent decisions and provider evidence.
What to agree during setup
Agree which person handles each kind of failed action and which source records they need to examine. A payment-evidence question may need Payment Reviewer, while a service-use question belongs with Service Professional and Salon Manager. Keep the operation identity available so a successful action can be distinguished from a new request to do more work.
Confirm how the reconciliation command represents verified completion in the booking and receipt records. Review the supported behavior after a correction, including whether an earlier failed operation is replayed or a new authorized attempt is required. Keep the original outcome available so the team can explain why the later action was necessary.
Check the handoff on an actual case
Follow a booking with confirmed appointment evidence and approved, completed service use. Salon Manager runs reconciliation and inspects the action-specific outcome. Auditor opens the linked service record and provider evidence to explain what the reconciliation reviewed. Confirm that the receipt belongs to this action and the intended booking version.
Use a separate case with an unresolved linked effect or an operation awaiting review. Inspect the actual failure or review-needed response and identify the responsible person. Resolve the issue through the supported path and review the next outcome without changing the earlier evidence to make the history appear successful. The handoff is ready when the team can explain what completed, what remains unresolved and which records support that conclusion.
What your team sees
- Operation Outcomes — Follow action receipts with their expected revision and available effect references.
- Failed and Review Operations — Focus on failed or review-needed outcomes and their recorded reasons.
- Completed Product Use — Inspect completed service-use records during booking reconciliation.
Follow the work through
Use Completion reconciliation to rehearse the final review and Reports to agree the operating questions the team will follow.
What it keeps track of
Data model- Operation receipts
- Idempotent operation receipts for guarded workflow commands.
- Bookings
- Appointment bookings with lifecycle, quoted amount and resource counterparty.
- Service consumption
- Service close-out extensions recording actual product and service use.
- Review decisions
- Independent review decisions recorded against a source revision.
- Payment evidence
- Verified provider payment events reconciled against bookings.
- Record attachments
- Files attached to bookings as supporting evidence.
Who uses it
Permissions- Salon Manager
- , Front Desk, Service Professional, Payment Reviewer, Auditor, Admin.
- Salon Manager
- Coordinates reconciliation; the relevant preparer resolves an exception; Auditor reviews the resulting evidence.
Set up Salon + Booking + CRM + Inventory your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.