HUCE Booking Ready for the first customers

Customers book themselves. The calendar handles the rest.

A booking system for clinics and treatment centres. Customers book online, and the calendar keeps track of rooms, practitioners and shifts. All of it runs on your own domain, in your own design.

The day calendar in HUCE Booking: three practitioners side by side, each with their own room, bookings laid out by the hour, and a count of the day's shifts and bookings along the top.

One example, all the way through

Meet Lyngstrand.

Three clinics, 24 practitioners and a handful of company agreements. The rest of this page shows their week, screen by screen.

Lyngstrand does not exist. It is a made-up example, and every name, number and screen on this page was produced for the purpose — none of it comes from a customer's data.

Lyngstrand Treatment clinics in Aarhus, Odense and Copenhagen
3
clinics
24
practitioners
11
services
18
company agreements

What the customer sees

Four steps. No account.

The customer picks a site, a service, a day and a time, and types their name. Nothing more. If only your members book with you, they get a one-time link by e-mail instead of a password they have forgotten anyway.

The booking page can be placed inside your own website, so the customer is not sent off to an address they do not recognise. You decide which websites are allowed to show it.

The first step of the booking page: the clinic's address and three treatments with duration and price, each with a radio button.
1Site and service
The second step of the booking page: a month calendar where the days with free times are marked with a dot.
2Pick a date
The third step of the booking page: the free times on the chosen day, shown as buttons from 08.00 to 16.00.
3Pick a time

Behind the desk

The whole day on one screen.

Every room and every practitioner stands side by side. When a customer rings to cancel, you move the booking with one click — the system already knows whether the time is free, whether the room is taken, and whether that practitioner may carry out the treatment.

  • You lay shifts, not individual slots. Once the shift is there, the system works out the free times itself — including the gaps in the middle of the day.
  • When the customer is at the desk or on the phone, you create the booking from three fields and a time.
  • Moves and cancellations are recorded with a reason, so afterwards you can see who, when and why.

The rota

The rota catches the mistakes straight away.

Lay a week at a time from a template. The system watches rest periods, weekly hours and travel time between clinics, and objects immediately — not first when payroll is run.

When a practitioner calls in sick, the system passes the shift on to those who hold the qualifications, one at a time. The first to accept gets it. No group text, and nobody arrives too late.

A week of the rota: fifteen shifts with day, hours, practitioner, site, room and work type, all marked published.

Company agreements

When the company pays.

A company buys an agreement with a period and a number of clips. Their employees book against it, the clips come off automatically, and you can see at any time how much each company has used.

The public events page with an upcoming course, its time and place, and a button to buy a ticket.

Events

Classes, courses and talks.

A course has tickets and a cap on places instead of a practitioner and a room. It gets a page of its own, and at the door you scan the ticket instead of looking for the name on a list.

Getting started

You are ready in an afternoon.

You get a link by e-mail. It signs you in the first time, so no passwords have to be passed around, and it opens a list of what is still missing. The list is built from your own data and ticks itself off as you create things.

Each line is a shortcut to the screen where the job gets done. When the necessary parts are in place you take the system into use, and the list disappears.

The setup checklist in the console: nine lines, six of them ticked, each with a shortcut to the screen it belongs to.
The identity card in settings: fields for the name, the logo, five colours, the typeface and the corner radius.

Your name, not ours

In your own design.

You set up the logo, the colours, the typeface and the corners once, and it reaches everywhere: the console, the customer portal and every page your customers see. The booking page lives on your own domain — not on ours with your name in it.

Where your data lives

Your data sits on its own.

Every customer gets a database of their own. Not one shared database with a customer number in every row. If we part company one day, you can have your data handed over as a single file.

If your practitioners, agreements and shifts already live in your own Dynamics 365, they stay there. A wizard connects your tables to the platform's, checks the setup against your environment and reads sample records before anything is saved. HUCE Booking reads from there and never writes into what you own.

Our database Standard. Nothing to set up.
Your own Dynamics 365 Mirrored data stays where it is.

Modules

You only switch on what you need.

The modules are off to begin with. When one is off it is not in the menu, and you do not run into it anywhere. That is why the system does not feel big, even though it can do a lot.

Booking

Sites, rooms, services, practitioners and the rota. The calendar, the booking page and everything an ordinary day is made of.

Companies and agreements

Customers can belong to a company that holds an agreement with a period and a number of clips. The employee then books against the company's agreement instead of paying themselves.

Clinical notes

Notes on the treatment, encrypted in the database and visible only to those you have given access. A clinic needs them. A workshop does not, and then the word never appears in the menu.

Waiting list

When a time is taken, the customer joins the list. When it frees up, the first in line hears about it straight away, without anyone having to remember.

Events

Courses, talks and classes with tickets, a cap on places and check-in at the door. They get a page of their own that needs no booking account.

Campaigns

Gaps in the calendar you can still fill: see where demand is missing and write to the customers who usually come at that time.

Prices

A fixed price per month.

No set-up fee, no lock-in and no charge per booking. You can change plan from month to month, and you only pay for the modules you have switched on.

The first 30 days are free, so you can set everything up and try it out before an invoice is sent.

Start

DKK 249 per month

One clinic with a couple of practitioners.

  • ✓ Online booking
  • ✓ Booking page on your domain
  • ✓ Sites and rooms 1 site
  • ✓ Practitioners up to 3
  • ✓ Rota
  • – Working-time rules
  • – Waiting list can be added
  • – Clinical notes can be added
  • – Events can be added
  • – Company agreements
  • – Your own Dynamics 365
Get started

Enterprise

By agreement ask for a price

Your own systems, many addresses or many company agreements.

  • ✓ Everything in Clinic
  • ✓ Any number of sites
  • ✓ Clinical notes and events
  • ✓ Your own Dynamics 365 shifts and agreements stay where they are
  • ✓ A database of your own outside the shared pool
  • ✓ A named contact
Contact us

Add-ons: clinical notes DKK 99, events DKK 99 and waiting list DKK 49 per month. Texts to customers and practitioners are billed as used.

All prices exclude VAT.

The groundwork

What only becomes important after a couple of months.

Roles and access

Nobody sees anything until you have granted it. A scheduler can be given one clinic, a receptionist their own day, and a stand-in only what the shift requires.

Working time that is checked

Rest periods, weekly hours and travel time between clinics are counted while the shift is being laid. Not afterwards, when it is already in the calendar.

Sickness that gets covered

When a shift comes free, the practitioners who hold the qualifications are asked one at a time. The first to accept has the shift.

Personal data you can hand over

A customer can be given everything you hold on them, and can ask to be forgotten. Both are a button in the console, not a job for a developer.

A trail you can follow backwards

Who moved that booking, and when? Every change that matters is written down automatically.

Danish and English

The whole system exists in both languages. Including the error messages, which are the ones that hurt most to read in a foreign tongue.

Let's talk

Shall we take a look at your calendar?

Tell us how you book today and where it goes wrong. Then we will work out whether HUCE Booking is the right answer for you.

christian@huce.dk