Skip to content

article

StretchSchedule FAQ and Troubleshooting

Answers to the most common StretchSchedule questions and fixes for booking-page, availability, timezone, and routing issues.

This article collects the questions we hear most and the fastest fixes for common issues. For deep-dives, follow the links to the dedicated guides.

Frequently asked questions

Do the people booking with me need an account? No. Your public booking pages require no login for invitees. Only you (the host) sign in to your StretchSuite workspace to manage event types, availability, and bookings.

See Sharing Booking Links.

Can several event types share one set of hours? Yes. Build an availability schedule and point multiple event types at it. You can keep several schedules and mark one as the default.

How do I stop last-minute bookings? Set a minimum notice in Settings or on the event type. Slots inside the notice window are hidden. See Scheduling Rules.

How do I avoid back-to-back meetings? Add before/after buffers so consecutive slots leave a gap. See Scheduling Rules.

Can my team share incoming bookings? Yes — use a round-robin event type with routing hosts, and choose a strategy (round-robin, least-loaded, or priority). For meetings that need everyone, use collective mode. See Team Scheduling.

How do reminders work? Workflows send email/SMS reminders and follow-ups on triggers with a delay. See Automated Reminders and Workflows.

Can I make the booking page look like my brand? Yes — upload a logo, set brand/accent/background colors, add a welcome message, and hide the Powered by footer. See White-Labeling Your Booking Page.

Troubleshooting

My booking page says "not found" The event type must be both visibility = public and status = active. Drafts, private, internal, disabled, or archived event types return a not-found response on purpose (the app never reveals whether a page is merely private vs. nonexistent). Flip the event type to public + active and retry.

No available times show up Work through these in order: 1. Does the availability schedule have active weekly windows? Empty schedules offer nothing. 2. Is the booking window wide enough to include upcoming days? 3. Is minimum notice so large it's excluding everything near-term? 4. Are buffers and existing bookings squeezing out the day?

Times look wrong to my invitees The page always displays times in the invitee's local timezone. If they look off, your availability schedule's timezone is probably set incorrectly — fix it and re-test in a private browser window.

A slot disappeared right before someone booked That's intentional. StretchSchedule re-checks availability at write time, so if a slot was taken while the invitee filled in the form, the booking is rejected (a 409) instead of double-booking you. The invitee just picks another open time.

An invitee can't reschedule or cancel They may be past your reschedule or cancellation cutoff. Those cutoffs limit what invitees can do on their own — you can still reschedule or cancel any booking from your Bookings list.

Round-robin bookings all land on one person Confirm every host is in the event type's routing hosts, the strategy is least-loaded or round-robin (not a lopsided priority list), and each host has real availability so the pool has slots to offer. Use routing preview to check behavior.

My logo or colors won't apply Logos must be PNG, JPEG, or WebP. Colors must be full 6-digit hex values like #10B981 — names and shorthand aren't accepted. Save, then reload the public page.

The AI event helper isn't available AI extraction is flag-gated. If it's turned off or the AI service is momentarily unavailable, it fails safe and returns no events. Ask your workspace administrator whether it's enabled.

Still stuck?

If a problem persists after these checks, note the event type's slug, the timezone involved, and what you expected vs. what happened, and reach out to support with those details — they make diagnosis much faster.

Was this helpful?

Help us improve this article

Use these controls to share whether this answer solved the issue. Feedback helps prioritize updates to StretchSuite Support.