Appointment booking
A customer picks a service, a person and a time; the system checks opening hours, the employee's days off, buffers before and after, and whether the slot is still free. We have built this logic with prices and durations per employee, special working days that override the weekly schedule, and an 'any available' choice that spreads work round-robin. For a Danish construction company we set up site visits at the customer's address: 60 minutes with 30-minute travel buffers on both sides, and the address checked against our own address API before the booking is saved.
Rooms, equipment and vehicles
When a booking needs a thing as well as a person, such as a treatment room, a shared massage table, a van or a meeting room, the system has to count capacity. We model each resource with a quantity per location and refuse overlapping bookings once that number is used up, both when booking and when an appointment is moved. It is the same check bkg.dk uses for a salon with three chairs and five stylists. Equipment rented by the hour or by the day can get its own calendar and its own price rules.
Staff schedules and rota
Bookable times are only as good as the staff schedule behind them. We connect booking to the rota, so sick days, holidays and swapped shifts close the right slots without anyone editing two systems. Our time-registration product jatid.dk already exchanges data with bkg.dk this way: it reads planned schedules and booked times without any customer details, and sends back worked minutes, which appear next to booked minutes in the payroll report. If you need a rota system on its own, that is jatid.dk; here we build the link to your booking.
Reminders by SMS and e-mail
Reminders reduce no-shows only if they arrive at the right moment and name the right day. We learned that from a bug of our own: a booking made for the same afternoon received its confirmation and its 24-hour reminder minutes apart, and the Danish template said 'tomorrow'. Now a booking must be at least three hours old before a reminder is sent, and every template states the actual date. Text messages go through our SMS gateway jasms.dk with your business name as sender; confirmations on WhatsApp run through n8n and the WhatsApp Cloud API where customers prefer that.
Deposits and no-show fees
A deposit is the most direct protection for a full calendar. We set it per service, as a fixed amount or a percentage, and take it through Stripe when the customer books. Businesses that prefer not to charge upfront can save the card at booking instead and charge a no-show or late-cancellation fee afterwards, under the cancellation deadline they choose. Payments land on your own Stripe account, not on ours, and the customer sees the terms before confirming.
Waitlists that fill cancellations
When an appointment is cancelled, the people waiting for that day should hear about it at once. Our waitlist sends a notification with a signed link; the first person to click gets the slot, and a lock in the database stops a second person taking it in the same second. Cancellations are also sent as webhooks carrying the freed employee, service and time, but no customer data, so other tools can react. One use we built for: an automatic social post about free times tomorrow.
Client self-service
Customers want to move or cancel without having to call. We build a 'my bookings' page reached from the confirmation e-mail, with rebooking inside the rules you set, for example no changes within the cancellation window, plus booking history, saved cards and consent or health forms filled in before the visit. The confirmation screen in bkg.dk offers 'add to calendar' for Google and as an .ics file. Staff get their own view in the language they prefer, Danish, English or Ukrainian.
Calendar integration
Booking and private calendars have to agree, or double bookings follow. Exporting is simple and robust: each booking as an .ics file or a subscribed feed, which is how jatid.dk shares shifts with employees' phones. Reading busy times back from Google Calendar or Outlook needs more care, because two systems now edit the same hours; we build it when the business really plans in both places and agree in advance which side wins a conflict. Full two-way sync is not part of bkg.dk yet, for exactly that reason.