A realistic afternoon
At 2:10 pm a client changes her appointment. At 2:20 pm a staff member reports a late start. Before closing, a completed service has a payment split across two methods. Three separate messages are not enough: you need to see what is pending, confirmed and resolved.
Four views that must work together
- Bookings: Which request needs approval, and who sees the changed time?
- Team: Who owns the next task and who takes over when plans change?
- Working hours: Is attendance recorded, and does a difference need review?
- Internal cash review: Do the service, recorded amount and payment methods match?
The benefit is a traceable workflow with clear owners, not four more disconnected screens.
A 15-minute demo test
Give the provider one real service, two team members and a common reschedule. View the owner and staff screens separately. Then enter a payment split across two methods and ask how a difference is recorded and resolved. Have the provider show these steps on a phone.
Already using software?
Run the same day in your current system. Count the extra calls and messages the team needs. Before switching, ask about data export, permissions, setup work, full cost and a way back. Judge SalonOS against your own day rather than a feature list.
Berlin, Cologne and Hamburg
Berlin can test several staff roles and client language needs. Cologne can test a day with the owner away. Hamburg can test a late reschedule and split payment. These are remote demo examples, not claims of local offices.
SalonOS · Medyahashtag
You cannot spend every day at reception. When you are with a supplier, your family or another business, you need a clear workflow for decisions rather than a stream of messages.
Test my salon day in a demo