A notification is written by one person and read by another, so it has to be translated into the reader's language rather than the author's. How BeeSection works out that language, why it takes two fields instead of one, and what "same as default" means.
Push is the third channel of a notification, next to the bell and the live screen update. What reaches the phone, how to subscribe a device, how to pick events, what quiet hours are and why a notification may not have arrived.
Three small things people ask about separately - your own document template for a visit, a notification to a specialist's phone when the CRM tab is closed, and webhooks so salon events land in someone else's system. What each one can do, and where its limits are.
A client asks, "When was I last in, and with whom?" - the front desk answers by hand every time. The client cabinet answers it instead: a personal link showing upcoming visits and the whole history.
A number calls in, and before the administrator even picks up, the screen already shows the client's name, when she last came in, and how many times. Here's what telephony in the CRM can do, and what it can't.
A contract with a new specialist, a policy, a payslip, an act for a client. The document is put together in the CRM, and the recipient signs it via a link - with a checkbox, a drawn signature, a PIN or an SMS code - while the signature is recorded together with the IP address and time.
The order of language selection on the site and the booking pages - the person's choice, then the region, then the browser language. Why the region ranks above the browser and how we learn it.
Checking that "the time is free" and saving the booking are two separate actions, and a second booking can slip in between them. How a database-level lock closes that gap for the CRM, online booking and the calendar at once.
A specialist sees their own bookings and not the colleague's revenue. An administrator sees the whole schedule but not the money. The ready roles, the "own only" rule and how to invite an employee.
What you can keep about a client beyond a phone number - skin type and allergies, colour formulas, before and after photos, signed consents and money on deposit. And how it works at the visit.
Why a person chooses the booking page address rather than the system, which words are reserved, why the check answers only "yes" or "no", and why the address cannot be changed.
A note on how the Telegram reminder channel is built - why there is one bot for the platform, what is inside the subscription link, and why its signature is so short.
