Troubleshooting

If invitees report your booking page shows no slots, work through this checklist.

1. Check Your Availability Schedule

Settings, then Availability. Confirm: – The schedule for the event is active. – At least one day has time blocks set. – Time zone is correct.

2. Check Date Overrides

Open Date Overrides tab. Confirm: – No accidental full-block override for the current period. – Holiday imports did not block too much.

3. Check Min Notice And Max Days Ahead

Open the event editor, Availability tab.

• Minimum notice of 24h means slots within 24h are hidden. If it is currently 10 AM and minimum notice is 24h, the earliest slot is tomorrow at 10 AM.
• Max days ahead of 7 means only the next 7 days are bookable.

4. Check Buffer

Buffer 30 min before + 30 min after on a 30-min event = 90 min of calendar time per booking. With a full external calendar, every slot gets blocked.

5. Check Calendar Sync

• Open the Read inspector (Calendars settings).
• Look for “block-everything” events: vacations, all-day events, recurring events.
• Move any to a calendar Bookme does NOT read.

6. Check Daily / Weekly Caps

Caps you set on the event hide slots once reached: – Daily cap 3 hit = today is “full” for invitees. – Weekly cap 8 hit = this week is “full.”

7. Check Round-Robin Pool

For round-robin events, slots only appear when at least one pool member is free. If everyone is on vacation, the whole pool shows empty.

8. Use The Public Slots Debugger

Settings, then Tools, then Slot debugger. Pick the event and date range. Bookme shows you EXACTLY why each slot is or is not available.

9. Test In Incognito

Sometimes browser cache or cookies cause stale views. Open in incognito and confirm.

10. Contact Support

If you have checked all the above and slots are still missing, email [email protected] with the event slug and the date range. We can diagnose from the server side.

Bookme sometimes appears to “skip” a slot you expected to be bookable. Here is why this typically happens.

1. Buffer Is Eating The Slot

If your event has a 15-minute buffer before and after, an existing booking at 2 PM blocks 1:45 – 2:45 PM. The “next slot” appears at 2:45, not 2:30 as you expected.

Check your event’s buffer settings.

2. External Calendar Has A Tentative Event

Bookme by default treats tentative Google or Outlook events as busy. A meeting you marked as “Maybe” still blocks the slot.

To change this: – Settings, Calendars, Treat tentative events as available toggle.

3. Min Notice Pushes The Slot Out

At 12:36 PM with a 1-hour min notice, the next bookable slot must start at 1:36 PM or later. Slots on the half-hour grid start at 2:00 PM (the next 30-min boundary after 1:36).

This is correct behavior, but feels like the system “skipped” 1:30. It did not; 1:30 was 54 minutes from now and minimum notice required at least 60.

4. Calendar Read-Sync Latency

External calendar events take up to 5 minutes (Google, Outlook) or 15 minutes (iCloud) to be reflected in Bookme. If you just deleted a calendar event but the slot is still blocked, wait a bit and refresh.

Click Force sync to skip the wait.

5. Daily / Weekly Cap Hit

A daily cap of 3 means after 3 bookings today, no more slots show today. Check the event’s daily / weekly limits.

6. Date Override Set Custom Hours

A custom-hours override for the day overrides the regular schedule entirely. If you set “Today, 9-12 only” and it is 2 PM, no slots show until tomorrow.

7. Round-Robin Pool Is Empty For That Time

If all team members in a round-robin pool are busy at the requested time, no slot is offered. Check each team member’s availability for that day.

8. Slot-Grid Mismatch

If your duration is 45 minutes but your slot-grid interval is 60, slots only appear on the hour (not :15 or :30). Check the event’s grid interval.

9. Use The Slot Debugger

The slot debugger (Settings, Tools) lists every potential slot in a range and tells you why each was kept or dropped. The fastest way to diagnose.

If a reminder email did not arrive, here is what to check.

1. Workflow Is Turned Off

Workflows page; confirm the relevant workflow has the Active toggle on.

If you toggled it off recently, any bookings made AFTER that point will not have the workflow fire.

2. Workflow Did Not Apply To This Event Type

If the workflow is scoped to specific event types and the booking is for a different event, the workflow does not fire.

Open the workflow and check the Event types dropdown.

3. Workflow Was Created AFTER The Booking

Workflows fire only on FUTURE bookings. If you created the workflow today and the booking was yesterday, the workflow did not fire for that booking.

4. Booking Was Cancelled Before The Workflow Fired

If a 24-hour reminder is scheduled but the invitee cancels 26 hours before the meeting, the reminder is cancelled (not sent).

Check the booking’s status and the workflow activity log.

5. Workflow Activity Log

Open the workflow. Scroll to Activity log. It lists every recent firing attempt, success or fail.

If you see your booking listed with a “Skipped” reason, the log tells you exactly why.

6. Email Landed In Spam

The email DID send; the invitee just did not see it. See article 13.5 on deliverability.

Ask the invitee to check spam, search for “Bookme.”

7. Wrong Recipient

Workflow might be configured to send to host, not invitee. Open the workflow and check Recipients.

8. Webhook Workflow (No Email)

If the workflow is a webhook only (not an email action), no email is sent regardless. Webhooks ping your endpoint silently.

9. Send A Test To Yourself

On the workflow editor, click Send test to me to verify the workflow renders correctly. If the test arrives, the workflow itself is working.

10. Contact Support

If you have checked all the above and a workflow that should have fired did not: – Email [email protected] with the booking ID. – Include the workflow name and the expected fire time.

If the booking page shows the wrong time zone for you or an invitee, here is what to check.

1. Check Your Time Zone In Settings

Settings, then Profile. Verify the time zone matches your actual location.

If you travel often, this can drift. Update it whenever you settle in a new place for a while.

2. Invitee Time Zone Auto-Detection

Bookme detects the invitee’s time zone from their browser. Common cases where it is wrong: – VPN. Browser timezone might be the VPN server’s location. – Travel. Invitee in Europe but laptop set to home time zone. – Misconfigured device. Rare but possible.

3. Manual Time Zone Override

Invitees can change the displayed time zone on the booking page via the dropdown at the top. Tell invitees they can pick their own zone if the default looks wrong.

4. Calendar Event Time Zone

The calendar event is written in your write calendar’s time zone. If Google Calendar is set to “Eastern Time” but your account in Bookme is “Pacific Time,” the calendar event time will be displayed in Eastern Time on the calendar even though Bookme stored it as Pacific.

Confirm your Google Calendar default time zone matches your Bookme time zone.

5. DST Transitions

Daylight Saving Time shifts happen automatically in modern browsers and apps, but for bookings made before a DST shift that occur after, the clock time may seem off by an hour.

Verify with the date and your time zone using a tool like timeanddate.com.

6. Multiple Time Zones In One Workspace (Teams)

For round-robin events, each host has their own time zone. The booking page shows slots in the invitee’s time zone, computed by intersecting all hosts’ availability.

If a team member’s time zone is set wrong, their offered slots will be wrong.

7. Test With A Friend In A Different Zone

The most reliable check: – Ask a friend in a different time zone to open your booking page. – They confirm the time matches what they expect for their location. – If they see it wrong, the issue is on their side (browser, VPN). If they see it right but you see it wrong, the issue is your settings.

If a booking was created but no Zoom link appears, the system fell back to brandID Meet (or another tool). Here is why.

1. Zoom Was Disconnected At Time Of Booking

The most common cause. If your Zoom OAuth token expired (or you accidentally revoked it) at the moment the booking was made, Bookme could not create a Zoom meeting.

Bookme falls back to brandID Meet so the booking can still complete.

Fix: Reconnect Zoom under Settings, Integrations. Future bookings get Zoom links.

2. Zoom Account Limit Reached

Some Zoom plans cap concurrent meetings. If you hit the cap, new Zoom meeting creation fails.

Fix: Upgrade your Zoom plan or wait until earlier meetings end.

3. Recreate The Zoom Meeting Manually

For an existing booking that should have a Zoom link: – Open the booking from the Bookme dashboard. – Click Details. – Click Recreate meeting.

Bookme tries again with the current Zoom connection. If successful, the calendar event is updated and the invitee receives a fresh confirmation.

4. Event Type Was Set To brandID Meet, Not Zoom

Open the event editor and confirm the location is set to “Zoom.” If it says “brandID Meet,” that is by design, not a bug.

5. Reschedule Or Cancel/Rebook Bug

In rare cases, a reschedule of a Zoom event might fail to update the Zoom side while the calendar updates. The result: the booking has a Zoom URL but it points to the OLD time.

Fix: Cancel and rebook, or click Recreate meeting.

6. Preventive Measures

• Enable Notify on Zoom disconnect in Settings, Integrations. You get an email the moment Zoom disconnects, before any bookings fall through.
• Re-test Zoom quarterly by booking a test slot.
• Monitor your Zoom plan limits in the Zoom dashboard.

7. brandID Meet As Permanent Fallback

For event types where Zoom is your preference but you cannot tolerate a fallback to brandID Meet (e.g. customer expects Zoom branding): – Set up alerts on Zoom disconnect. – Pause the event when Zoom is down.

Cancelled bookings are intentionally one-way. Once cancelled, the slot is released and the booking record becomes historical.

1. Why Cancellation Is One-Way

• The calendar event is deleted.
• The meeting URL (Zoom, Google Meet) is destroyed.
• Refunds are processed (if paid).
• Workflow jobs (reminders, follow-ups) are cancelled.

Rescheduling a cancelled booking would require: – Recreating the calendar event. – Issuing a new meeting URL. – Re-charging the invitee. – Re-firing workflows.

It is cleaner to create a new booking from scratch.

2. What To Do Instead

Ask the invitee to book a new slot via your booking page. They can use the same event type as before.

Or send them the direct event link in an email: – “Sorry about that. Here’s the same calendar to pick a new time: [link].”

3. Distinguishing “Cancelled” From “Decided To Reschedule”

When you click Decided to reschedule in the post-meeting check-in (or invitee uses the reschedule link), the booking is NOT cancelled. It enters a “rescheduling” state where: – The original slot is released. – The Zoom URL stays alive temporarily. – The invitee gets a fresh calendar picker.

This is different from a full cancellation.

4. Recover A Recently Cancelled Booking

If a booking was cancelled very recently and you want it back: – Within 1 hour: contact [email protected] immediately. – After 1 hour: the slot, calendar event, and Zoom meeting are gone. Recreate manually.

5. Bulk Re-Invite Cancellation Victims

If you accidentally cancelled multiple bookings (e.g. test of bulk-cancel went wrong): – Filter the bookings page by status = Cancelled. – Export them. – Send a manual “sorry, please rebook” email referencing the export.

6. Preventive Measures

• Always double-check before bulk-cancelling.
• For paid bookings, the refund triggers immediately on cancel. Reversing is hard.

For anything not covered in this help center, Bookme has three support channels.

1. Email Support

• Address: [email protected].
• Hours: Email is answered 9 AM to 6 PM Eastern, Monday to Friday.
• Response time: Usually within 4 hours during business hours, within 24 on off-hours.

Include in your email: – Your account email. – A clear description of the issue. – Steps to reproduce (if a bug). – Screenshot or screen recording. – The booking ID, if applicable.

2. In-App Chat (Pro and Elite)

The chat bubble at the bottom right of your dashboard connects you to live support during business hours.

• Pro: Best-effort response within 1-2 hours.
• Elite: Priority queue; usually under 30 minutes.

3. Help Center

You are reading it. Search at the top of help.bookme.brandid.app for any question.

4. Bug Report Template

For technical bugs, this template helps support diagnose fast:

“` Account email: [your email] Account plan: [Free / Pro / Elite] Browser: [Chrome 128 / Safari 17 / etc.] OS: [macOS 14 / Windows 11 / iOS 17]

What I expected: [clear description]

What actually happened: [clear description]

Steps to reproduce: 1. [step] 2. [step] 3. [step]

Screenshot or video: [attach] Booking ID (if applicable): [id] “`

5. Feature Requests

Email [email protected] with the subject “Feature request: [short title].”

We read every one. We do not commit to building everything, but every popular request gets reviewed.

6. Status Page

For service outages or known issues: – status.bookme.brandid.app.

Subscribe to updates via email or RSS.

7. Community And Updates

• Twitter / X: @brandIDbookme.
• LinkedIn: brandID bookme company page.
• Email updates: Subscribe in your Notifications settings.