Principle 1
Confirm the new scope
Say what changed, why it changed, and what the customer is now receiving.
Service scope-change checklist
When the work changes, the bill and the recognition story must stay clear.
Extra time, added tasks, substitutions, and new team members can blur the line between required charges and voluntary appreciation.
Practical guidancePlain-language trust standardsBuilt for real service moments
From guest signal to owned action
ConnectedRecognition
Make appreciation easy
Recovery
Give supported work an owner
Team context
Keep recognition visible
Public review
Offer a configured next step
The connected product loop
Recognition, service context, and supported follow-up.
The short answer
Start with clarity, not persuasion.
Document the changed work, confirm any required charge before completion, update who owns the service, and present optional recognition only after the customer understands the final scope.
Principle 2
Agree on required charges
Do not let a tip become a substitute for pricing added work clearly.
Principle 3
Update service ownership
Keep the recognition path connected to the actual person or team after staffing changes.
Principle 4
Close the loop once
Give the customer a final summary before presenting optional feedback or recognition.
The working checklist
Use this before the experience reaches a guest.
A good recognition moment should be understandable without a policy document or a sales explanation.
The changed work is described in plain language.
Any required price change is agreed before completion.
The final person or team responsible for the service is recorded.
The customer receives one coherent final summary.
Optional recognition appears only after required charges are clear.
The follow-up link points to the correct service context.
Where trust breaks
Watch for the moments that make appreciation feel confusing or coercive.
Using a tip to cover extra work
The customer is left to compensate a worker for scope the business should have priced clearly.
Recognizing the wrong team
The original assignment remains attached even though different people completed the work.
Multiple conflicting closes
The office, field team, and invoice each tell a different story about what happened.
Put it into practice
Keep the service record aligned with the people who delivered it.
A larger moving job
Confirm the added time and crew, then connect recognition to the full team that completed the move.
An event schedule change
Document the new service window and team before the guest-facing recognition path appears.
A substituted practitioner
Update the appointment context so feedback and recognition reach the professional who delivered the service.
Continue the work
Choose the next useful resource.
A better service moment starts here
Make the recognition moment feel as thoughtful as the service.
Try Aplauso as a guest, then use the guide to shape an experience your team and customers can trust.