Less scattered work
Your team and its operational issues no longer live in separate tools.
Centralize vacations, absences, attendance, shifts, schedules and coverage alerts for every service and location.
These are the concrete results you get with this feature in the day-to-day of service.
Your team and its operational issues no longer live in separate tools.
Services can show alerts or problems when expected staff is missing.
Vacations, corrections and profiles stay organized by organization and location.
Real screens of the product in action, not mockups. What you see here is exactly what your team will use.
Employees and roles
The team, their roles and permissions by location, as the foundation of all staff operations.
Team calendar
Each employee's shifts and availability by week, with alerts when a service is left without coverage.
Attendance and clock-ins
A record of team clock-ins and clock-outs, with an attendance list and corrections to approve.
Vacations and absences
Team vacations, absences and blocks on the period's calendar.
Vacation requests
The approval flow: team requests with status and buttons to approve or reject.
Employee profile
Each employee's record with their upcoming services and the month's attendance hours.
Features that are already available and live in the product from day one.
Step by step, this is how this feature fits into real service, without switching tools or losing context.
Organize staff by location, role and operational context.
Vacations, absences and corrections stay centralized and visible to operations.
The service can alert you when expected staffing isn't covered.
Explore the rest of the features and see how they fit together within a single operation.
Launch your own booking channel with a URL and QR per location, availability by service and direct entry into the restaurant's operations.
Open pageModel zones, tables, combinations and capacity rules to better assign each service and make the most of every time slot.
Open pageBooking, table, ticket, payment and invoice live within the same operational flow so service never loses context.
Open pageCheck this feature's documentation, go back to the index or jump straight into a demo with real data.