Guides on running a salon, tips for specialists and notes on how BeeSection works inside.
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.
A message two days after the visit, a birthday greeting, and "we have not seen you in a while" after six months. How to enable them, what to set, and why nothing goes out during quiet hours.
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.
There's one machine, two specialists, and both are free at 11:00. The specialists' calendar won't show that - it tracks a person being busy, not a thing. We go through the resource catalog, automatic bookings tied to a service, conflicts, downtime, and the load map.
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 segment is a saved rule for "who exactly", a mailing is "what and how". Between them stand quiet hours - whatever lands at night goes out in the morning. We break down the channel cascade, the dry run, the queue and unsubscribing.
A specialist completes an appointment — and earns XP. XP gives a level and a title, the level unlocks achievements, and two specialists can agree to a battle with a stake. We break down what's counted automatically and where the limit is.
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.
Job application replies in DMs, paper questionnaires, "how did you hear about us" asked out loud. The form builder gathers all of it in one section - a link or widget for your site, responses with statuses, and statistics for every question.
Sometimes we send an invitation to open a higher plan for a few days. Why it is an invitation rather than a switch-on, when the countdown starts, what closes afterwards and why nothing is deleted.
