CalendoxCalendox Docs
Account

Notifications

How Calendox in-app and email notifications work — sync, billing, team, and booking notification categories, and which preferences you control.

Calendox sends notifications through two channels: an in-app bell dropdown and email. Everything generates an in-app notification; emails are sent for the categories where missing the news would matter — billing, team, security, integrations, booking activity, and (if enabled) sync failures.

Where do I find my notifications?

The bell icon in the header shows a dot whenever you have unread notifications. Opening the dropdown marks notifications read automatically as you scroll past them. Click View all (or go to Dashboard → Notifications) for the full, paginated history.

Dismissing a notification hides it from your list. Read notifications older than 30 days are cleaned up automatically; unread notifications are never auto-deleted.

What triggers each notification category?

Each notification carries a category badge in the list:

CategoryWhat triggers itChannels
SyncA sync finishes setting up, fails, or some events couldn't be copied after repeated retriesIn-app + email (failure emails only if enabled, see below)
EventBooking activity on your pages — new bookings, approval requests, reschedules, booker cancellations, expired requests — and responses to team invites you sentIn-app + email (booking request expiry is in-app only)
ReminderAn upcoming event is starting soonIn-app
BillingSubscription activated, renewed, cancelled, trial ending/expired, payment failed or recovered, plan changedIn-app + email
TeamA member is added/removed, a role changes, or a license is assigned, updated, or revokedIn-app + email
IntegrationsA meeting app (Zoom, Google Meet, Microsoft Teams) is connected or disconnectedIn-app + email
SecurityAn account security event, such as a sign-in from a new deviceIn-app + email
GeneralUncategorized account notificationsIn-app

How do booking notifications work?

Bookings notify both sides of every change, and each side gets what fits their situation:

  • You (the page owner) get an email and an in-app notification (tagged Event) for new bookings, approval requests, reschedules, and booker cancellations. Expired approval requests appear in-app. Every booking notification links straight to Dashboard → Bookings.
  • The booker isn't a Calendox user, so they're kept informed entirely by email — confirmation with their private manage link, approval or decline, reschedule, cancellation, expiry, and up to 3 pre-meeting reminders.

All booking emails show times in the recipient's own timezone with a UTC reference. See Manage bookings for the full booking lifecycle.

Which preferences can I control?

Go to Dashboard → Settings → App → Notifications:

  • Sync failure emails — whether a failed calendar sync also emails you (on by default).
  • Marketing & product updates — occasional feature news; entirely optional.

Everything else — billing, team, security, integrations, and booking emails — is transactional and always sent, because each one reflects something that already happened to your account. In-app notifications are always created regardless of email preferences.

Who gets notified on a team?

For Business and Enterprise accounts, billing and team notifications aren't limited to the person who triggered them:

  • A billing event (e.g. a failed payment) notifies every admin on the team, not just the person who manages payment.
  • Removing a member notifies that member directly and notifies all team admins.
  • License assignment, update, or revocation notifies only the specific member whose license changed.

If something looks wrong

  • An expected email never arrived — check spam, then check Settings → App → Notifications in case the sync-failure toggle is off. In-app notifications still appear even when emails are disabled, so the bell is the source of truth.
  • A notification disappeared — read notifications are cleaned up after 30 days; the underlying event (sync status, booking, invoice) is still visible on its own page.

Next steps