The confirmation is buried in an inbox
A booking made in March is confirmed in an email nobody can find in July. The customer phones to ask what time it was, and somebody stops what they are doing to look it up.
A customer portal that answers “what did I book?” without an account
Half the messages a booking business receives are the same three questions: what time was it, can I move it, and can I cancel. Answering them by hand is a job somebody does instead of the work. Answering them with a page the customer reaches from their own confirmation costs nothing and keeps the decision where it belongs — a customer can ask to move a booking, and the business still says yes or no.
Every «what time was my booking again?» is a phone call your staff answer instead of working.
What is included
- A link by email, not a password to remember
- The booking, its status, its dates and its price
- Change and cancellation requests, answered by you
- The business's own logo and colour on the page
- No account, no marketplace, no other business's offers
- Direct customer access
- Clear request status
- Business-owned relationship
What the customer portal is for
For the customer who booked and now wants to check, change or cancel something without phoning during your busiest hour. It fits appointments, classes, rentals and stays alike, and it is most useful where bookings are made weeks in advance — which is exactly where people forget the time and where a rearrangement is most likely.
What it is not
It is not an account system, a loyalty scheme or a customer app. There is no profile to build, no password to manage and no marketplace to browse. It is also not a self-service rebooking engine that overrides your rules: what the customer sends is a request, and confirming it stays with your team.
Why the same three questions keep arriving
Three ordinary frictions that cost more in interruptions than they ever do in bookings.
Nobody wants another password
Asking a customer to create an account to see one booking is a good way to lose them at the door. Whatever protects the booking has to be lighter than the thing it protects.
A change request becomes a conversation
A customer wants an hour later. Without a place to ask, that is a phone call, a missed call, a message and a call back — four interruptions for one small decision that could have arrived as a request in the queue.
A client portal for bookings, opened from the confirmation
Four steps, and the first one is why nobody has to remember anything.
1. The link comes with the confirmation
Every confirmation carries a way back to the booking, so the customer already has it in the message they were going to search for anyway.
2. Access is verified, not registered
Reaching the booking is confirmed against the contact that made it rather than a new account and password. Nobody manages credentials, and a link that arrives at the right person is enough for a page about one booking.
3. They see the booking as it stands now
What, when, where, with whom, and the rules they accepted. If it moved last week, the page shows the current version rather than the version in an old email.
4. They ask; you decide
A request to move, extend or cancel arrives in the same queue as everything else, with the rule that applies attached. The business confirms or refuses, and the customer is told which — instead of assuming that sending a message was the same as agreeing something.
Requests stay requests, decisions stay yours
Three things, and each of them is a decision the business keeps.
Requests are requests
Nothing a customer does silently changes your calendar. A cancellation or a move is proposed, checked against your notice rules, and confirmed by somebody on your side.
One booking, not a customer file
The page shows the booking it was opened for. It is not a profile, not a history of everything they ever did with you, and not a place where somebody could browse your business.
The current version, not the old email
Because the page reads the booking rather than a copy of it, a customer looking on Thursday sees what is true on Thursday.
A forgotten time and an early move request
A forgotten time, and a request that arrived before the day did.
“What time were we booked?”
The customer opens the link from their confirmation and reads the answer. Nobody at the desk stops mid-job to look it up, and the question never becomes a phone call at the busiest hour of the week.
A move requested on Thursday
The customer asks to shift Saturday by two hours. The request lands in the queue with the notice rule attached, the desk sees the alternative time is free, and it is confirmed in a minute — before the slot would otherwise have been quietly wasted.
Access tied to one booking, nothing more
A link that shows somebody’s booking has to be careful about who can open it and what it reveals.
Access is tied to the booking, not to your business
A verified link opens one booking. It does not list your customers, does not expose other bookings and does not become a way into anything else you run.
Only what the customer already knows
The page shows what the customer booked and agreed to. Internal notes, staff comments and anything your team wrote for its own use stay inside the business, where they were meant to be read.
Letting customers manage booking online on your terms
Decide what a customer may ask for — a move, an extension, a cancellation, or only some of those — and make sure your notice rules say what happens for each. Write the confirmation so the link is obvious rather than buried under a signature. Decide who watches change requests and how quickly they are answered, because a request nobody replies to is worse than no portal at all. Then open your own confirmation on a phone and try to move a booking as a customer would; whatever confused you will confuse them.
Not an account, an app or a payment page
It is a window onto one booking, and it stays that small on purpose.
Not an account or an app
No registration, no passwords, no profile, nothing to install. If a product asks your customers to sign up before they can look at their own appointment, it is optimising for the wrong party.
Not self-service that overrides you
A customer cannot rebook themselves into a slot your rules would refuse. The portal proposes; the business disposes.
Not a payment page
No cards and no balances. Where money is involved, the rule is shown and the payment happens the way your business already handles it.
Customer portal questions
How does a customer find their booking again later?
From their own confirmation. This client portal for bookings opens from the link in the confirmation, and access is checked against the contact that made the booking, with no account or password. There the customer sees the time and what they booked and accepted, and can manage booking online by asking to move or cancel it. Your team still confirms or refuses each request.
Do customers need an account?
No. Access is verified against the contact that made the booking, so there is no registration and no password to forget.
Can a customer cancel by themselves?
They can request it. The request carries your notice rule and is confirmed or refused by your team, so nothing changes in your calendar without somebody deciding.
Can they see other bookings or other customers?
No. A link opens the booking it belongs to and nothing else. It is not a directory and not a way into your business.
Are internal notes visible?
No. The page shows what the customer booked and accepted. Notes your team writes for itself stay inside the business.
Does the portal take payments?
No. Where a deposit or balance applies, the rule is shown and the money moves the way it already does in your business.
Next step
Open a workspace and set up one booking flow
Registration takes an email address. The operating model, services and resources are configured afterwards, in the console.