Front Desk / Guide

Fix calendar availability and booking problems

Check the booking route, calendar connection and service settings, then recover without creating duplicate appointments.

Last reviewed October 20, 2026

Editorial perspective: Nia · Front Desk · AI teammate

First check where the booking happened

A Google appointment-schedule page and Nia’s native calendar booking use different settings. Changing Google’s booking page does not change Front Desk’s services or booking rules. Identify the route before reconnecting or changing anything.

Keep the page or conversation reference, service, requested time and time zone. Use your own test attendee when reproducing a problem; do not repeatedly submit a customer’s booking to see what happens.

No available times appear

For a Google booking page, check that schedule’s time zone, available hours, notice period, advance window, daily limit and the calendars selected for conflict checking.
For native Nia booking, open Front Desk → Settings → Google Calendar and verify the account, calendar, timezone and connection status.
In Services, check Active, Booking enabled and Appointment duration (minutes). In Business profile, check whether Booking mode is Instant, Request or Callback.
Ask Ariy to verify the configured business hours, notice, booking horizon and conflict rules. Not every scheduling control is exposed in Settings.
Check that the relevant calendar events are marked Busy. Do not delete a real appointment to make a test slot appear.

The calendar says Needs reconnect

An owner or admin can select Reconnect Google Calendar in Front Desk Settings, choose the intended business Google account and review its permissions. After returning, verify the displayed account, calendar and timezone.

If authorization was cancelled, reconnect when ready. If the session expired, start a new connection request. A message that Google OAuth is not configured requires Ariy’s help rather than another password. While availability is unavailable, Nia should retain booking intent without inventing a confirmed time.

Nia recorded a request but no event appeared

Request mode records an unconfirmed time request for follow-up; it does not immediately create a calendar event or invitation. Callback mode keeps live scheduling off. Instant mode can confirm an available time after the provider operation succeeds.

Check the recorded state and contact details before treating a request as a missing appointment. Ask the responsible person to follow up or have Ariy verify the intended booking mode.

The event has no Google Meet link

For Google’s appointment page, check that Google Meet is the schedule’s conferencing choice. For native booking, the selected service has its own Google Meet video call setting. Business profile → Google Meet for general calls applies only when no service is selected.

A calendar event and a usable video link are separate outcomes. Google may leave the conference pending or fail to supply it. Ask Ariy to check the existing event and booking reference; do not create another appointment just to obtain a link.

Before launching a video-booking flow, verify one controlled booking, the correct event and attendee invitation, and a usable Google-provided Meet URL. A checkbox or booking request alone is insufficient.

A booking timed out or may have been created twice

Check the existing Front Desk record, owner calendar and attendee confirmation before retrying. Tell Ariy the reference and when the attempt happened, including the time zone. An unclear result needs reconciliation with the existing appointment.

Do not cancel or recreate an appointment on the customer’s behalf merely because the chat looked incomplete. Appointment changes and cancellation depend on the verified route and authorization.

Verify the recovery

After the configuration is corrected, use an approved test attendee and one controlled booking. Check the exact service, time zone, duration, event, invitation and any required Meet link, then confirm the slot is no longer offered.

Clean up the test through the agreed route. If it still fails, use the existing Ariy support conversation and include the minimum useful evidence. Do not share passwords, calendar tokens, private event details or a customer’s full transcript.

Ask Nia about this guideGet an answer grounded in the published Help Center.

Need a hand?

Prepare a useful help request, or continue your existing Ariy setup or project conversation. For Nia configuration, open your Front Desk settings.