Slotora for busy salons

A login for the front desk

The person on reception needs more than a stylist and less than you. Slotora has a seat for exactly that, and this page is the list of what it opens — read out of the permission sets themselves, not described from memory.

Two seats, and you choose per person

A salon hands out two kinds of login. Nobody is charged for either, and there is no limit on how many people are on the team.

  • Front desk

    Runs the floor: every column of the diary, the client book, payments at the counter and a refund with the guest still standing there. Not the salon's takings, and not the settings.
  • Stylist

    Her own column, her own hours, her own numbers. You can widen her to the whole salon's diary with one tick if she books for other people, and that tick changes nothing about money.

What each login reaches

Each row below is one permission set in the code, not a summary of several. Where a row says the owner, a colleague's login cannot get there by typing the address either. The table is the starting point: the rows that say „or a login you allow” can be handed to one person at a time.

See the whole team's diary and move an appointmentOwner, manager, front desk — and a stylist for her own column
Open a guest's card: past visits, notes, tags, photosOwner and front desk
Take a payment at the counter — cash, card, QR codeOwner, front desk and stylist
Give a guest her money back at the deskOwner and front desk — and you can take it away from one login
See what the SALON took today, this month, per personThe owner — or a login you allow
Change the price of a visit or give a discountThe owner — or a login you allow
Change services and their pricesThe owner — or a login you allow
Export data to a spreadsheetThe owner — or a login you allow, and then only what she may see
Change hours, the booking page, payment settingsThe owner only
See what the salon owes each personThe owner — and each person her own row; a login you allow to see reports

Giving somebody the seat

You add the person to the team, choose which of the two seats she gets, and Slotora e-mails her a login. She never sees a password of yours.

  • Six permissions, per login

    On top of the seat, six switches for one person: see reports, see everyone's takings, give a discount or change a price, refund, export, and edit services and prices. Each starts at what her seat allows, so nothing changes until you change it. The owner and admins always have everything.
  • A login that works at one premises

    With more than one address, bind a front-desk or stylist login to one premises or several: her diary, her bookings and her exports narrow to them, and she can only book there. The client book stays whole, and a report she may see shows only her premises — never another shop's figures.
  • Set from the phone too

    Coming
    The permissions and premises screen comes to the Slotora app with its next version. The rules themselves are checked on our side, so a phone on an older version already obeys them.
  • From the browser

    The team screen, next to her name. Choosing the seat is part of adding her, not a separate settings page to find afterwards.
  • From the phone

    The same two seats in the Slotora app, so an owner who never opens a browser can put somebody on reception on a Saturday morning.
  • Taking the seat back

    One switch on the same screen. Her diary history stays — what she changed and when is still on the booking she changed.

And you can keep the phone numbers to yourself

One setting hides every guest's phone number and e-mail address from the team while leaving the notes, the tags, the caution field and the receipt exactly where they are. It is the setting a salon asks for when somebody leaves and takes a client list with her, and it applies to the front desk as well as to stylists.

Questions a salon owner asks first

Can the receptionist see how much the salon made?

Not unless you let her. By default that is the owner's, and it is a separate permission from the client book on purpose — she counts the till at the end of the day without ever seeing the month. You can switch on reports and everyone's takings for her login if you want her to.

Can a receptionist at one branch see only that branch?

Yes. Bind her login to that premises: the diary, the bookings and what she can book narrow to it. The client book stays whole, and a report she may see shows only her premises — never another shop's figures.

Can she refund a card payment?

Yes, at the desk, because that is where the guest is when she asks. An online card payment is a separate matter and follows whoever was paid.

How many logins can I give out?

As many as you have people. There is no per-seat charge and nothing in Slotora counts your team before letting you add somebody.

Does a stylist see the other stylists' guests?

Only her own column unless you widen her, and widening her is about the diary alone. She never sees what anybody else earned.

Next

The two other things a salon asks about, both on their own page:

The rest of this product

The other pages about Slotora for busy salons.

Set up tonight, take bookings tomorrow

Register, add your services and each colleague's hours, and your booking page is live. No card, no contract, no notice period.

Open a salon account

May we measure which pages actually help? “Accept all” also lets us measure our own adverts.

What exactly does this mean?

We'd like to use Google Analytics to see which pages help and which don't, and to remember which poster, flyer or message of ours — or which salon's recommendation — brought you here. Accept all also allows a Meta advertising pixel, so we can tell which of our own adverts brought a salon that signed up — and if you create an account, our server sends Meta your email address scrambled (hashed), never as readable text, with your IP address, your browser's details and Meta's own cookie ids — never your name — purely so it can recognise that the sign-up came from an advert. None of this runs on a salon's own booking page. Everything the service itself needs works either way. Cookie Policy