Front desk
It takes repetitive questions, finds bookings and prepares changes instead of manual rewriting between calls and walk-ins.
AI receptionist for salons, clinics and services
Sofia relieves an overloaded front desk and gives hair stylists, barbers and other staff a fast way to handle bookings, availability and calendar changes over WhatsApp or Telegram on top of Alteg/Altegio. It can also handle client questions without another app.
Sofia live
Where Sofia helps the team during the day
Sofia was not built as a website chatbot. It is an operational assistant for places where messages, reschedules and calendar changes fall on an already overloaded front desk and then spill across the whole team.
It takes repetitive questions, finds bookings and prepares changes instead of manual rewriting between calls and walk-ins.
Between clients, they can quickly check the schedule, find a booking or prepare a move without opening multiple screens or forwarding messages back to reception.
They can see what changed, who approved it and return supported actions when something happens in the wrong time or context.
When teams work across multiple salons, Sofia verifies the right Alteg account, location and employee before anything important is applied.
What overloads the front desk and team today
When the front desk cannot keep up, messages land with hair stylists, barbers, therapists or branch managers. People reply between appointments, search bookings on their phones and change the calendar under pressure. That is exactly where delays, mistakes and lost bookings appear.
WhatsApp and Telegram messages are handled by whoever has a free minute.
Stylists and other staff deal with operations instead of the client in front of them.
The front desk keeps repeating the same availability and confirmation answers.
Calendar changes happen under pressure and still need to be traceable.
Multiple salons, accounts and employees increase the risk of acting in the wrong context.
Assistance for front desk and staff
Sofia primarily understands operational messages from staff while still handling client questions as well. It can find a booking, suggest open times, prepare a move, a cancellation or an availability change, and keep the right account, salon and employee in one execution context before anything is applied. The team does not deal with system mechanics, only with confirming what makes sense.
Hair stylist
I need to move client Novakova from today to Friday afternoon.
Sofia
I found the booking today at 15:00. On Friday, Klara has open slots at 14:30 and 17:00. Which time should I prepare?
Front desk
Close tomorrow morning bookings for barber Petr.
Sofia
I've prepared a calendar change for tomorrow morning for Petr at Barber Shop. Please confirm it before I apply it.
Client
Hi, do you have anything free on Thursday for balayage?
Sofia
Yes, Thursday has open slots at 11:00 and 15:30. If you want, I can prepare the booking right away.
Multiple contexts without confusion
Sofia assumes that a branch lead, front desk worker or freelancer can work with multiple Alteg accounts, several salons or different branches. Before an important action, it always works with a specific account, salon and employee.
User
Close bookings for tomorrow.
Sofia
You have access to multiple salons. Which salon should I prepare the change for?
Capabilities for front desk, staff and clients
Security and traceability
Sofia is not a bot that rewrites the calendar without thinking. Important actions are prepared as structured proposals first, checked against account context, salon context and permissions, and only then passed for confirmation.
Blocks, reschedules and other sensitive changes are prepared first and sent for approval whenever they can affect operations or the client experience.
Every completed step can be traced by time, account, salon and the person who approved or triggered the change.
Operational actions stay linked to the relevant conversation context so the team can see why a change happened and what request it came from.
For selected operations, the system stores the original state and prepares a controlled return path without manually rebuilding the calendar or booking.
Sofia respects branch, account and role boundaries so staff do not make changes outside the operation they are responsible for.
Before anything is applied, Sofia resolves the target account, location and optionally the employee so the action does not happen in the wrong branch.
From message to safe Alteg change
An employee or client sends a message through WhatsApp or Telegram.
Sofia recognises whether it is a client question or an operational request from the team.
It fills in missing details and resolves the active Alteg account, salon and optionally the employee.
Using Alteg/Altegio data, it prepares a concrete booking, reschedule or calendar-change proposal.
Important or risky changes are sent for approval to the right person.
After confirmation, the change is executed in the specific account and salon context.
The system stores audit history, conversation history and prepares rollback for supported actions.
How Sofia is structured
Sofia has separate layers for chat channels, active Alteg account and salon context, action proposals, approvals, audit and undo. That lets it help the front desk and the team without blind changes in the booking system.
Core stack
TypeScript
Mastra AI
NestJS
Docker
PostgreSQL
Redis / BullMQ
Audit log
OpenTelemetry
Deployment options by operational scope
Every option runs on WhatsApp and Telegram, supports multiple Alteg accounts and shares the same safe foundation: Alteg/Altegio integration, conversation audit and confirmation for important changes. The difference is not in the channels, but in how deeply Sofia participates in daily operations, calendar control and internal operating processes.
Included in every option
No matter the scope of the first rollout, you get the same operational layer for communication, safety and control.
WhatsApp + Telegram
Multiple Alteg accounts
Alteg/Altegio integration
Conversation and action audit
Confirmation for important changes
Undo for supported actions
For operations that want to solve inbound communication, bookings and common reschedules without overloading the front desk.
For operations where Sofia actively helps the front desk, stylists and other staff with day-to-day coordination.
For businesses that want tailored approvals, roles, integrations and custom operational processes beyond the standard rollout.
FAQ
Ready for operational rollout
Sofia removes repetitive messages from daily operations, prepares safe calendar changes and lets the front desk and staff focus more on clients than on booking mechanics.
Book a Sofia demo
Share the basic context about your operation, branches and who currently handles bookings. We will follow up with a concrete Sofia rollout proposal.