Troubleshooting common problems

A booking happened but no calendar event appeared

Bookings are written to our database first and pushed to Google afterwards, so a Google hiccup can never lose a booking — it can only delay the invite. A reconciliation job runs regularly and creates any calendar event that failed the first time, without ever creating a duplicate for one that succeeded.

What to check:

• The booking itself is confirmed and the time is held either way, so nobody else can take the slot.
• You have a target calendar set in Settings. A connection used only for conflict checking is never written to.
• If the grant was revoked, the event cannot be created at all — reconnect, and email us about anything already booked so we can re-run it.

I never heard about a booking

Every booking triggers a notification email to you as well as a confirmation to the invitee, precisely so that hosts without a connected calendar are not left in the dark. If one did not arrive:

• Check spam and any "promotions"-style filtering.
• Check the address on the account — notifications go to the address you sign in with.
• Corporate mail filters sometimes quarantine mail from new senders; ask IT to allow our sending domain if this is systematic.

My invitee says they never got a confirmation

Confirmations are sent immediately on booking, and a reminder goes out roughly 24 hours before the meeting starts. The usual causes are a typo in the email address on the booking form, or the invitee's spam folder. If the meeting is on your calendar, the booking is real regardless — you can forward them the calendar invite directly.

Someone got "that time is no longer available"

This is the double-booking guard doing its job. Two people can load the same page and pick the same slot; the first to submit wins and the second is asked to choose again. It is also what you will see if a conflicting event appeared on your calendar while the invitee was filling in the form. No booking is lost — the second person simply picks another time.

Two meetings landed on the same slot

Two bookings made through Neos Meet cannot overlap for the same host; that is enforced by database constraints, not by application code that could race. An overlap therefore means one of them came from somewhere else — an event created directly in Google in the seconds between our availability check and the booking, or a calendar that is not marked for conflict checking.

Fix: in Settings, make sure every calendar that holds real commitments has conflict checking switched on.

A teammate can't be booked on a team link

A host contributes times only after accepting the invite, signing in, setting hours, and connecting a calendar. The Teams page shows exactly which step each member is on. On collective links, one unfinished host empties the whole page — see Team links and round-robin.

Cancelling or rescheduling

The invitee's confirmation email contains a management link that lets them reschedule or cancel; both parties are emailed when they do. If you need to cancel from your side and the meeting is on your calendar, cancelling the calendar event does not cancel the Neos Meet booking — use the management link, or email us if you no longer have it.

Sign-in problems

"Access denied" on the login page

A small number of addresses are blocked from provisioning accounts. If you believe yours has been blocked in error, email us from that address.

Google won't let me connect a calendar

Some Google Workspace domains restrict which third-party apps users may authorise. If the connection screen refuses or an admin approval message appears, your Workspace administrator controls that setting — the request they need to approve covers free/busy reading and the ability to manage events on calendars the user owns, which is what creating booking invites requires.

Something else

Email us with the booking link, the event type, and the exact time involved. If an error message showed a reference code, include it — it maps straight to the request in our logs.

Still stuck?

Email support@neos.network with your booking link and, if there is one, the exact time an invitee tried to book. A real person reads it — there is no bot in front of us.