Rebooking and retention
Waitlist, slot offer and a reminder for the next booking, matched to the service and to client preferences. In this trade, a lost seat is not recovered the next day.
Square Appointments
A free slot is not enough: the person available also has to be able to do the service. The appointment is written into Square when your plan allows it, into Zenvox otherwise.
7 days, 20 answered calls, no card
Where your appointment lands
The appointment is written into Square when your plan allows seller-side writing; otherwise the request is written into Zenvox, with the service, the expected duration and the preferred professional, and your team enters it. Cancelling stays with the software: it is not written from Zenvox, and it is your own cancellation policy that gets read out to the caller.
On access, availability search and booking are documented. Still to verify: merchant-side and buyer-side permissions, the plan that allows seller-side writing, and how locations and accounts map together — a chair renter often holds their own account. A configuration carrying cancellation fees can also be excluded from certain bookings.
The classic trap of the trade is settled ahead of any software: a free slot in the calendar is not a usable slot. A colour service booked as a haircut blocks too little time and derails the rest of the day.
Read, create, update, cancel
The status below comes from vendor documentation and from what has not been qualified: plan, permissions, events and localised rules.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | Availability search is documented with services, team, customers and locations. That read is what allows offering a slot genuinely compatible with the service. |
| Create | To qualify | Booking is documented. It requires merchant-side permissions and a plan that allows writing; a configuration carrying cancellation fees can be excluded. Both points get verified before any commitment. |
| Update | To qualify | Moving an appointment needs the same skill check as booking. In a salon where professionals rent their chair, account separation has to be established before any write. |
| Cancel | Zenvox native mode | Cancelling touches your policy and sometimes fees. It is taken, time-stamped and passed on with the freed slot; the decision on fees and on a replacement stays with the front desk. |
What is included, what needs an add-on
Answering during a service, capturing the service, duration and preferred professional, stating your cancellation policy and passing the request on belong to your services base. Filling a freed slot and bringing clients back is a named add-on.
The authorisation, and what holds the truth
A salon where several professionals work under one banner raises an identity question before an access question.
- Authorisation is granted from your merchant account; Zenvox asks for no password
- Accounts of professionals renting a chair are separated before install: their bookings do not mix
- The skill a service requires is checked before a slot is offered, not after
- An uncertain request becomes a consultation; it does not block a randomly chosen duration
- The stylist validates a transformation, an uncertain duration and the product; the front desk approves a change of professional
Late afternoon, two chairs busy and nobody free to answer. The call is taken by Zenvox; nothing is written into the software.
CallerHi, I would like an appointment for a cut, and maybe change my colour at the same time.
ReceptionistLet me take your name and a callback number. For colour, how long it takes depends on what is on your hair right now: I suggest a short consultation with the colourist before booking.
ReceptionistI am also noting your preferred professional and reading out the salon cancellation policy. The salon confirms the appointment; I do not book it myself.
The salon receives an honest request: a cut, plus a colour consultation instead of a too-short slot booked blind. Tomorrow does not fall apart because a colour was taken for a haircut.
When the connection is not there
The software keeps the calendar, and the receptionist works in Zenvox native mode.
- The request is created inside Zenvox with service, expected duration and preferred professional
- Your online booking link is texted out when one exists
- Your cancellation policy is read out to the caller in your own words
- You find the call, its transcript and its reason in the app
- The day booking becomes qualified, it is added without redoing your setup
Questions about this connection
Is the appointment written into Square?
When your plan allows seller-side writing, yes; otherwise the request is written into Zenvox with the service, the expected duration and the preferred professional, and your team enters it. Merchant-side and buyer-side permissions remain to be verified.
Is a free slot enough to book?
No, the person available also has to be able to do the service. The skill required is checked before a slot is offered, not after, and a colour service booked as a haircut derails the rest of the day.
Our professionals rent their chair — do their bookings get mixed?
No, their accounts are separated before install. How locations and accounts map together is part of what gets verified before any write.
What about an uncertain request?
It becomes a consultation, and it does not block a randomly chosen duration. The stylist validates a transformation, an uncertain duration and the product; the front desk approves a change of professional.
Who decides on cancellation fees?
You do. A cancellation is taken, time-stamped and passed on with the freed slot, the decision on fees and on a replacement stays with the front desk, and your policy is read out to the caller in your own words. A configuration carrying cancellation fees can also be excluded from certain bookings.
Where to next
See the practice concerned, or the full list of software studied.
Square Appointments