Booking events
Handling new, changed and cancelled bookings, visit status and client data from YCLIENTS. Matching each event to the right business, location and workflow.
YCLIENTS, Telegram and MAX
I connect YCLIENTS bookings and events to Telegram and MAX. Messages follow defined rules, and a client response can confirm or cancel the corresponding booking.
Handling new, changed and cancelled bookings, visit status and client data from YCLIENTS. Matching each event to the right business, location and workflow.
Reminders, confirmations, post-visit messages and feedback requests. Scheduling rules, permitted delivery windows, templates and channel selection.
Linking a customer to a messaging account, actionable messages and a shared backend for both channels. Each platform’s API and message constraints are handled separately.
Confirm or cancel actions with checks for expiry and the intended client. The selected action is sent back to the YCLIENTS booking and its outcome recorded.
Scheduling work from events, retrying temporary failures, avoiding duplicates and exposing reasons why a message was not sent. Logs cover user actions and external responses.
Separate settings for locations and partners, workflows, channels and credentials in one administration area. Access rights and execution history for each business.
The platform includes partner and network settings, scheduled messaging windows, booking and feedback workflows, signed actions from Telegram and MAX, and booking changes in YCLIENTS. Development is ongoing.
A completed project delivered Telegram and MAX applications connected to an external API, with a web administration interface. A public client review confirms the work.
A fitness studio network website was built from scratch and connected to YCLIENTS, payments, ERP and an online class platform. It demonstrates how booking data can fit into a wider service.

Partners and networks, service workflows, Telegram and MAX, signed callbacks and application of responses to YCLIENTS bookings.
View project details
Two messaging platforms, an external API connection and a web interface for system administration.
View project details
A WordPress project integrated through APIs with YCLIENTS, payment systems, ERP and an online-streaming platform.
View project detailsWe define the process, source data and expected result. For an existing project, I review the affected code. We then agree scope, cost and milestones.
I implement the agreed workflows and check the result and its dependencies. Changes to live systems account for data integrity and neighbouring functionality.
I prepare the deployment and rollback procedure and verify the result after release. I hand over the changes and we agree further support where needed.
Yes. Each business has its own access credentials, events, channels and workflows, managed separately through one interface.
Yes, when the project rules and available YCLIENTS API support it. The response is tied to the specific booking and checked before an update is sent.
Temporary failures can be retried and logged. Ambiguous operations are flagged for review; putting a task in a queue is not treated as proof that a message was delivered.
Yes. We can implement a booking confirmation or post-visit message first, verify it against real events, and then add further channels and workflows.
Tell me which booking and messaging workflow you want to automate.
No passwords or access credentials are needed for an initial assessment. Send a project link, briefly describe the current and expected behavior, and include a timeframe or budget if already defined.