Principle 1
Required means required
Label business charges before the guest reaches the recognition moment.
Service charge vs tip
Guests and teams lose trust when a service charge, contractual gratuity, labor fee, and optional tip are presented as if they mean the same thing.
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
A service charge is a required business charge governed by the agreement or bill. A tip is voluntary recognition from the guest. Explain both separately and say who receives each one.
Principle 1
Label business charges before the guest reaches the recognition moment.
Principle 2
Do not use copy or interface defaults that make a voluntary tip feel mandatory.
Principle 3
Say whether the service charge supports the business, labor, or a defined team and who receives the tip.
Principle 4
Events, hotels, tours, and home services may all use different billing and team models.
The working checklist
A good recognition moment should be understandable without a policy document or a sales explanation.
Where trust breaks
A service charge and tip prompt appear together with no explanation of the difference.
The guest assumes a required charge goes directly to the person who served them when that is not clear.
The optional tip is requested before the guest understands the required bill.
Put it into practice
Explain contractual charges in the event agreement; present guest recognition separately at the event.
Keep room and amenity charges separate from recognition for housekeeping, valet, or bell teams.
The invoice covers the contracted work; a crew recognition link remains optional and clearly named.
Continue the work
A better service moment starts here
Try Aplauso as a guest, then use the guide to shape an experience your team and customers can trust.