Frequently asked questions.

Everything you need to know.

Getting started

No. Create an event with no account or sign-in. You'll get an event link right away — share it with everyone, including yourself. When you visit the link, you add your availability like everyone else, and you'll see who's replied and the group heatmap.

No. Everyone uses the same event link. Participants enter their name (and optionally their email) and mark their availability. No login, no password, no account required.

Yes. WhenItWorks is 100% free. Create unlimited events, collect availability, and see results at no cost. No credit card, no upgrades, no strings attached.

Organizers and guests use the same event link — there's no separate “manage” link. Everyone visits the same page: add your name, mark your availability, submit. After submitting, you see who's replied, the best available times, and the full availability heatmap.

Managing your event

Events stop accepting new responses at the end of the day before your latest event date. After that, you can still view results but cannot change them. Events are automatically removed after a few months.

Yes. On the same device, return to the event link anytime — your response will be pre-filled for easy updates. To edit from another device, add your email when submitting your availability; you'll receive a private edit link by email.

After creating an event, you get one event link. Share it with everyone via group chat, email, or any method you prefer. Organizers and guests use the same link.

After submitting, you see participant names and who has responded. Availability is shown as aggregated counts per time slot. The heatmap shows the overlap so you can pick the best time.

Events use the timezone you choose when creating (detected from your device by default). The time window is shown the same way to all participants — everyone sees the same range, so there's no confusion.

Privacy & security

Yes. We use industry-standard security practices. Event data is stored securely, and tokens are hashed. We never store plaintext tokens or expose sensitive information.