Skip to content
NLDONA

Scheduling

One schedule for every customer, channel and team.

NLDONA connects availability, appointments, reservations, staff, locations and customer channels so every booking uses the same business schedule.

Try NLDONASee how scheduling works

Customer request

Do you have anything Friday afternoon?

Available

  • 14:30
  • 15:30Selected
  • 16:00

Outcome

Appointment confirmed

Schedule
Fri · 15:30 reserved
Customer
Upcoming booking updated
Operations
Confirmation ready

Illustrative booking scene — not live availability metrics.

One schedule

However the booking starts, it ends up in the same schedule.

No separate phone calendar. No separate website booking calendar. Every supported booking stays connected.

Channels converge on NLDONA Scheduling — not parallel booking engines.

VoiceWebsite ChatWhatsAppPublic BookingOperator

One booking state

Same availability, same capacity, same customer context — wherever the request began.

Availability

Availability comes from the business — not from guesswork.

NLDONA checks configured rules before offering times. The model does not invent open slots.

Service

What the customer is booking, including duration.

Location

Where the work happens when you operate more than one place.

Staff / resource

Who or what must be free for the booking.

Schedule rules

Opening hours, capacity, and notice policies you configure.

External busy time

Connected calendar constraints where supported.

Appointments and reservations, handled in context.

Different booking shapes — the same availability authority and schedule visibility.

Appointment

Consultations, clinic visits, salon services, and similar timed work.

Reservation

Tables, service slots, and other capacity-based reservations.

Illustrative options — not live inventory.

Changes

Changes stay connected too.

Reschedule and cancel update capacity, confirmations, and future reminders under your rules.

Reschedule

  1. Existing booking
  2. Customer asks to move it
  3. New availability checked
  4. Booking rescheduled
  5. Capacity updated
  6. Confirmation updated

Cancel

  1. Booking cancelled
  2. Capacity becomes available
  3. Future reminders stop
  4. Business state updates

Illustrative flows — outcomes follow successful business changes.

How you work

Schedule around how your business actually works.

Services, locations, staff and duration stay part of availability — not a generic calendar blank.

Location
Vienna Center
Service
Consultation
Staff
Anna
Duration
45 min

Illustrative configuration — not a live tenant setup.

Team & self-service

AI bookings and staff bookings use the same schedule.

Your front desk and your customers do not maintain parallel calendars.

Your team can book too.

Staff can create, edit, reschedule, and cancel bookings in the operational scheduling workspace.

  • Front desk creates appointment → AI sees the slot as unavailable
  • AI books appointment → operator sees it immediately

AI-created bookings: Supported Voice, chat, and WhatsApp bookings write into the same availability and schedule picture.

Let customers book when they want.

Public Booking is self-service on the same NLDONA schedule — not a second online booking system.

  1. Choose service
  2. Location
  3. Staff if applicable
  4. Date & time
  5. Contact
  6. Confirmation channel
  7. Deposit if required
  8. Booking

Public Booking uses the same schedule as the rest of NLDONA.

After the booking

Bookings do not stop at confirmation.

Reminders, waitlist, deposits and calendars stay connected to the same schedule.

Reminders

When a booking is confirmed, reminder policy can follow. Reschedule and cancel update future reminders accordingly.

Not arbitrary campaign automation — booking-linked reminders under your rules.

Waitlist

When nothing fits, your team can capture demand on a waitlist. When capacity opens, eligible customers can be offered a time.

  1. No availability
  2. Waitlist entry
  3. Slot opens
  4. Customer contacted
  5. Customer confirms
  6. Booking created

Waitlist offers require customer confirmation before a booking is created. Public Booking waitlist self-serve join is not claimed as live.

Deposits

When a service is configured to require a deposit, customers can receive a payment link as part of the booking flow.

Customer deposits are separate from NLDONA SaaS billing. NLDONA is not a POS or accounting product.

External calendars

Google Calendar and Microsoft Calendar can contribute external busy time so NLDONA helps prevent double-booking.

External busy time is a constraint. NLDONA remains the business scheduling system — providers do not silently become booking authority.

Customer context

Customer
Maria K.
Upcoming
Fri · 15:30
Previous
Consultation
Language
German

Contact details may help locate context. They do not automatically prove identity.

Control

Your schedule stays under business control.

Availability and booking actions follow the rules you configure.

Configured availability

Open times come from business rules — not model guesswork.

Controlled booking actions

Book, reschedule and cancel stay inside your policies.

One schedule

Channels do not maintain duplicate booking calendars.

Visible history

Your team can see what was booked and correct when needed.

Built for appointment-driven businesses

DentalClinicsSalonsRestaurantsTradesLaw firmsReal estateRetailLogisticsElectrical & solar

FAQ

Common questions about NLDONA Scheduling.

Short answers based on current product truth.

What is NLDONA Scheduling?

It is the connected schedule for availability, appointments, reservations, staff, locations and customer channels — used by AI, your team and Public Booking.

Can NLDONA book appointments?

Yes, for supported appointment flows that follow your availability and booking rules.

Can NLDONA handle reservations?

Yes, for supported reservation flows that use the same availability authority.

Can customers reschedule or cancel?

Yes, when the change is supported by your rules. Capacity and confirmations update with the change.

Can staff create bookings manually?

Yes. Operator bookings and AI bookings use the same schedule.

Does NLDONA support multiple locations?

Yes. Location is part of availability when your business is configured that way.

Can NLDONA schedule different staff members?

Yes. Staff and resources can be part of availability and booking choices.

Does NLDONA connect to Google Calendar?

Yes. Google Calendar can contribute external busy time to help prevent double-booking.

Does NLDONA connect to Microsoft Calendar?

Yes. Microsoft Calendar availability can sit in the same booking picture.

Can customers book online?

Yes. Public Booking uses the same NLDONA schedule as Voice, chat, WhatsApp and your team.

Can NLDONA send reminders?

Yes. Booking-linked reminders can follow your reminder policy. Changes update future reminders.

Does NLDONA support waitlists?

Yes. Your team can capture waitlist demand in scheduling. Offers require customer confirmation before a booking is created. Public Booking waitlist self-serve join is not claimed as live.

Can I require a deposit?

Yes, when a service is configured to require one. Customers can receive a payment link as part of booking. This is not NLDONA SaaS billing.

Do Voice, Chat and Public Booking use the same schedule?

Yes. Supported bookings across those channels use the same availability and schedule.

Try NLDONA

See how NLDONA could handle scheduling for your business.

Paste your public website to start a temporary demo under your review.

Try NLDONAExplore the platform

Public information only. Demo experiences stay isolated from Production.