# AI Booking System, Client Portal and Admin Calendar Builder

Canonical: https://uvilno.com/use-cases/booking-and-clinic-portals
Updated: 2026-11-07

Build an appointment journey around service selection, availability, a booking request and a confirmed status. Uvilno can generate the customer website, mobile portal and desktop calendar views with managed records. Define cancellation, conflict and authorization rules explicitly. For clinics, keep sensitive medical records outside an unverified general-purpose booking release.

## Define confirmation and conflicting requests

A calendar UI cannot guarantee availability by itself. State whether an appointment is a request awaiting staff review or an immediately reserved slot. Specify time zones, buffers, capacity and cancellation windows. Confirmation must come from the service's authorized saved state, with useful feedback when two requests compete for the same time.

## Collect only the information the flow needs

A basic appointment request may need a name, contact method and chosen service. Health details, payment information and identity documents add substantial privacy requirements. Ask for an explicit data review before expanding a clinic portal. Test client and staff access independently and keep sensitive information out of public calendar cells.

## Platform plan

| Platform | Generated experience |
| --- | --- |
| web | Service details, availability selection and booking request. |
| mobile | A client view for upcoming appointments and permitted cancellations. |
| desktop | A staff calendar and request queue with authorized confirmation actions. |

## Declared collections

| Collection | Fields | Access |
| --- | --- | --- |
| services | name, duration, buffer, availability | Public service information and authorized schedule management. |
| bookings | owner, service_id, requested_at, status | Client-owned appointments and explicitly scoped staff review. |

## Acceptance checks

- Request a slot and show its actual pending or confirmed status.
- Exercise a conflict between two requests for the same availability.
- Verify time-zone display and cancellation rules.
- Confirm another client cannot read private booking details.

## Setup and launch boundaries

- Calendar presentation is not an atomic reservation system unless the backend implements that rule.
- Sensitive health information requires a separate legal, security and deployment review before collection.

## Editable starting brief

Build a booking website for a service business with service details, availability selection, a client account and a booking-request flow. Use services and private bookings collections. Begin with staff-reviewed requests and make pending versus confirmed status clear. Add a desktop staff calendar with explicit authorization and a touch-first client companion for upcoming bookings. Test conflicting requests, cancellation windows and time zones. Collect only ordinary appointment contact details. Do not collect medical records or claim regulatory compliance. Link companion projects through App connections after the core booking journey is verified.

## Common questions

### Does the calendar prevent double bookings automatically?

The backend must implement the required reservation or review rule. Ask for the intended conflict behavior and test concurrent requests before relying on availability.

### Can I store patient medical records?

This blueprint covers ordinary appointment coordination. Sensitive health records need a separate privacy, security, legal and deployment assessment.
