Find open slots in the staff schedule while they still sell

The agent works with the Yclients API in the scope of a single branch: its number takes part in every request, and every figure belongs to that branch. It reads appointments and visit history, clients, services and categories, staff with their schedules, open slots, goods and warehouses, financial transactions, loyalty and analytics. An open slot is counted not from a blank space in the grid but from the specialist's schedule and the duration of the service — otherwise a slot looks sellable and never sells.

An appointment and a visit are different things in a salon: the appointment stays in the schedule even when the client never showed up, and staff utilisation counted from appointments always looks better than the real one. The agent leans on the visit status and on the payment. Revenue is taken not from the price of services in the appointments either, but from financial transactions and Z-reports day by day: discounts, gift cards, packages and deposits shift the amount, and only the till adds up.

For writes the agent creates and reschedules appointments, adds clients and goods operations — as far as the system user's permissions reach, no wider. Before creating one it checks whether the specialist's slot is free and looks the client up by phone so a second copy does not appear in the base. Rescheduling and cancelling touch a live person with a reminder on their phone, so the agent names who is being moved and to when, and waits for confirmation.

Access is assembled from two tokens: the partner one opens only public methods, while branch data — appointments, clients, finances — is returned by the partner and user pair together with the branch number. The Yclients request rate is low, so the agent does not run the schedule in circles and picks periods deliberately. If a method is closed by the system user's permissions or there were no appointments in the period, it says so directly instead of showing an empty table.