Remote team scheduling

Schedule your remote team meeting without the Slack thread

Finding a time that works across a distributed team shouldn't take 40 messages and three days. Share one link, let everyone mark when they're free, and see the best slot emerge automatically.

Free to useNo account for anyoneWorks across time zones

Remote teams are generally good at recurring meetings. You have your weekly standup, your bi-weekly retro, your monthly all-hands — all locked in the calendar, recurring forever. Those aren't the problem.

The problem is the one-off meeting. The cross-team kickoff that involves six people who've never met. The external collaborator whose calendar you can't see. The quarterly planning session that needs everyone present but keeps getting postponed because nobody can agree on a time. The meeting that turns into a Slack availability thread that dies after three replies.

WhenItWorks is built for exactly that moment. Not to replace your scheduling stack — it doesn't do calendar sync or Zoom links — but to answer the one question that keeps causing friction: when can everyone actually meet?

What a Slack availability thread actually looks like

#team-general · scheduling a kickoff

AJ
Alex J Mon 9:14 AM
Hey all — need to find a time for the Q3 kickoff. Who's free this week or next?
SR
Sam R Mon 9:31 AM
Tuesday works for me most of the day, blocked Thursday afternoon
PK
Priya K Mon 11:08 AM
I'm in EST so mornings are rough — earliest I can do is 11am. Next week is better for me honestly
MO
Marcus O Mon 2:47 PM
Wednesday or Friday next week 👍 Tuesday is out for me
LT
Lena T Tue 9:02 AM
Sorry just seeing this — I'm traveling Wed/Thu next week, can do Friday afternoon or the week after?
AJ
Alex J Tue 10:15 AM
okay let me try to figure this out... @channel anyone NOT free Friday the 18th at 1pm EST?
↓ 23 more replies · 3 days later · still not scheduled

Every distributed team has a version of this thread. Availability trickles in across time zones, in different formats, over multiple days. The organizer ends up doing manual logic across 8 schedules to find a slot — and still misses someone who replied late.

The compounding problem:Each person in that thread has to read everyone else's messages to understand the current state of the negotiation. Add timezone conversions, different "morning" and "afternoon" definitions, and a few people who never reply, and what should take five minutes takes three days.

How WhenItWorks replaces the thread

1
Create a scheduling event in under a minute
Name it, pick the date range and time window you want to consider — for example, next two weeks, 9am–6pm. No account needed to create it. You get a shareable link immediately.
2
Drop the link wherever your team communicates
Slack, Teams, email, wherever. One link for everyone — team members, external collaborators, contractors. Nobody needs to create an account or download anything to respond.
3
Everyone marks their availability on the grid
Each person opens the link, enters their name, and taps or drags to mark when they're free. Takes about 30 seconds. Works on any device, in any browser.
4
The best slot surfaces automatically
The live heatmap shows which times have the most overlap. The best slot is flagged automatically — no manual counting, no mental math. You can also see exactly who's responded and who hasn't, so follow-ups are targeted rather than blanket reminders.
5
Pick the time, book it in your calendar tool of choice
WhenItWorks doesn't generate calendar invites or Zoom links — that part you do yourself with Calendly, Google Calendar, or whatever your team uses. WhenItWorks just gives you the answer to "when" so you can move on.

When it's the right tool — and when it isn't

WhenItWorks is deliberately focused. It solves the availability-discovery problem, not the full scheduling workflow. That makes it genuinely excellent for some situations and the wrong choice for others.

Good fit

  • One-off or infrequent group meetings
  • Cross-team syncs with people who don't share calendars
  • External collaborators, clients, or contractors
  • Groups of 4–15 where manual coordination breaks down
  • Teams in 2–3 time zones within a workday overlap
  • Anyone who would otherwise start a Slack availability thread

Not the right fit

  • Recurring meetings already on the calendar
  • 1:1 booking pages (use Calendly or Cal.com instead)
  • Globally distributed teams needing automatic timezone conversion per user
  • Workflows requiring auto-generated Zoom links or reminders
  • Full scheduling stack replacement

On timezones: WhenItWorks uses a single event timezone that you set when creating the event. Everyone sees the same time labels. This works well for teams in similar zones — a US-based team, a European team, a single-region group. For teams spread across three or more continents where each person needs to see times in their own local timezone automatically, LettuceMeet or Doodle handle per-user timezone conversion more gracefully.

Where this fits in a remote team's scheduling workflow

Most remote teams already have tools for the parts of scheduling that happen after you know the time. Calendly for booking pages. Google Calendar or Outlook for invites. Zoom or Meet for the meeting itself. Slack or Teams for the reminder.

WhenItWorks fills the gap that comes before all of that — the moment where you need to find the time in the first place. It's not trying to replace those tools. It's the step that happens before you use them.

Think of it as answering the question so everything else can proceed: once you know it's Thursday at 2pm ET, the Calendly invite, the Google Calendar event, the Zoom link — all of that takes two minutes. The hard part was figuring out Thursday at 2pm.

Specific scenarios where teams find it useful

Project kickoff with a new cross-functional group

You're starting a new project with people from engineering, design, and product who haven't worked together before and don't share calendar visibility. Drop the link in the project Slack channel, get responses within a day, pick the first meeting time and move on.

Scheduling with external collaborators or clients

External people usually aren't in your calendar system and you can't see their availability. Sending a WhenItWorks link is faster and less awkward than a multi-email "when are you free?" exchange — and more flexible than a Calendly link that only shows your own availability.

Quarterly or annual planning sessions

Half-day or full-day sessions that need every key stakeholder present — and that keep slipping because someone is always traveling or unavailable on the proposed date. Running a WhenItWorks event a month in advance gives people time to flag conflicts before commitments are made.

Onboarding a new team member

New hires typically need a series of intro meetings with different people in their first week. Rather than the hiring manager manually coordinating each one, a WhenItWorks event can quickly surface which intro sessions can be grouped and when each person is free.

Replacing the recurring meeting for a cycle that's changing

Your team is about to change timezones, working patterns, or headcount. The old recurring meeting slot may no longer work. Run a quick availability event before scheduling the new recurring slot so it actually fits everyone's new reality.

An honest note on what WhenItWorks isn't

Worth saying clearly

WhenItWorks is not a full remote team scheduling platform. It doesn't sync with Google Calendar or Outlook. It doesn't generate Zoom links. It doesn't send automated reminders before the meeting. It doesn't create recurring booking pages or manage a team's shared availability.

If you need those things, tools like Calendly, Cal.com, or LettuceMeet (which has Google Calendar integration) are more appropriate. WhenItWorks is best when the problem is simply: "I don't know when we can all meet, and I need to find out quickly without starting a Slack thread."

That's a real, recurring problem for distributed teams — and for that specific moment, WhenItWorks is fast, free, and requires nothing from the people you're trying to coordinate with.

Stop the Slack thread before it starts

Create a free availability event in under a minute. Drop the link in your team channel and have an answer by tomorrow.

Create your event →

Free forever · No account needed for anyone · Works in any browser

Frequently asked questions

How do I find a meeting time that works for a remote team across time zones?

Create a free event on WhenItWorks, set the date range and time window you want to consider, and share the link with your team. Everyone marks when they're free — no account needed — and the heatmap shows which slots have the most overlap. Best times are highlighted automatically.

Does WhenItWorks handle time zones for remote teams?

WhenItWorks uses a single event timezone that the organizer sets at creation. Everyone sees the same time labels, so the organizer should communicate which timezone the event is in. This works well for teams within similar time zones. For globally distributed teams needing automatic per-user timezone conversion, LettuceMeet or Doodle may handle that more gracefully.

Is WhenItWorks a replacement for Calendly or other scheduling software?

No — and it's important to be clear about that. WhenItWorks solves one specific problem: finding a time when a group of people are all free. It doesn't do calendar sync, automated reminders, Zoom link generation, or recurring booking pages. It's the right tool for the "when can everyone meet?" step, not for managing your full scheduling workflow.

Do team members need accounts to respond?

No. Anyone you share the link with — including external collaborators and clients — can mark their availability by entering just their name. No account, no sign-up, no download required.

When is WhenItWorks the right tool for a remote team?

It's most useful for one-off or infrequent group scheduling where you don't already know the right time and need to find it: kickoff meetings with new groups, cross-team syncs, external collaborator scheduling, onboarding sessions, or any situation where a Slack availability thread would otherwise break out.