Asynchronous work has been one of the dominant ideas in remote work culture since 2020. The argument is intuitive: if you remove the requirement for everyone to be online simultaneously, you eliminate timezone friction, reduce meeting overload, and give people more autonomy over their working hours. Several prominent tech companies — Basecamp, GitLab, Automattic — have built their entire operating models around async-first communication and made compelling cases for it.
The argument is largely correct for knowledge work, documentation, code review and written decision-making. It is almost completely wrong for scheduling and booking.
What async does well
The case for asynchronous work is well documented. GitLab's Remote Work Report, based on its own fully distributed workforce of 2,000+ employees across 65+ countries, identifies asynchronous communication as essential for equitable participation across time zones, reducing the meeting burden on individual contributors, and enabling deep work.
Stanford economist Nicholas Bloom, one of the world's leading researchers on remote work, has published extensive evidence that hybrid and remote work can match or exceed in-office productivity for roles involving sustained focused work — writing, analysis, coding, design. The key conditions: clear deliverables, reduced interruption, and autonomy over scheduling.
For these tasks, async works because the output is separable from the process. A pull request reviewed at 10pm London time is as useful as one reviewed at 2pm. A design file uploaded at 8am Singapore time is there when New York wakes up.
Where async breaks down: booking and confirmation
Booking is categorically different from knowledge work. It requires bilateral agreement in something close to real time, because the value of a booking is contingent on mutual confirmation.
Consider what happens when booking goes async.
Scenario one: you message a client on Monday morning asking if they're free Thursday at 3pm. They see the message Tuesday and reply that it works. You see their reply Wednesday and confirm Thursday. They've already double-booked Thursday, because they assumed silence meant the slot was available. The appointment fails.
Scenario two: a personal trainer posts their available slots in a WhatsApp group on Sunday evening. Members reply over the course of Monday with their preferred times. Three people select the 9am slot. The trainer has to manually adjudicate, notify the two who missed out, and reopen negotiation. This takes until Tuesday, and one of the three has already made other arrangements.
These aren't edge cases. They're the normal failure mode of async scheduling.
The research on response time and conversion
Harvard Business Review's research on lead response time, originally published in the context of sales leads but widely replicated across service bookings, found that the likelihood of a successful conversion drops by a factor of ten if contact is delayed by more than one hour. At 24 hours, conversion rates drop by a factor of sixty.
Applied to booking, a service professional who receives a booking request and responds the next day is operating at a fraction of the conversion rate of one who responds within the hour. The client has moved on: found an alternative, changed their mind, or simply lost the momentum of the original intention.
Accenture's research on small business customer experience consistently identifies responsiveness as one of the top three drivers of client retention for service businesses. Async workflows introduce latency into every response by design, which is acceptable for queries with no real urgency and actively damaging for booking requests.
Why WhatsApp creates a synchronous expectation
WhatsApp is not an email client. Its design — real-time delivery indicators, read receipts, "online" status — creates an implicit expectation of a relatively fast response. Ofcom's 2023 Communications Market Report found that half of WhatsApp messages are answered within an hour, compared with 90 minutes for SMS and over six hours for email.
When someone sends a scheduling request on WhatsApp and waits 24 hours for a reply, the wait feels longer than the same delay would in email, because WhatsApp has already conditioned them to expect faster. The friction isn't just the delay itself — it's the gap between expectation and reality.
The right framework: async for work, sync-capable for booking
The most effective model for remote and distributed teams isn't "async everywhere." It's async for knowledge work and near-real-time for coordination and booking specifically.
- Documentation, review and planning stay async.
- Decisions on complex topics use structured async with a sync fallback when they stall.
- Scheduling and booking need to be sync-capable and fast to confirm.
The tool requirement for booking is different from the tool requirement for deep work. A booking tool needs to work inside the messaging platform where clients already are, propose times without forcing a context switch, and collect confirmation in one or two messages rather than a back-and-forth.
Calendly and similar link-based tools solve part of this by creating a self-serve booking page, but they break the synchronous feel of a WhatsApp conversation, and completion rates drop noticeably when a booking link is shared inside a messaging thread rather than sent by email.
Does async work actually hurt small business bookings?
Yes, measurably. The cost of a single missed or delayed booking compounds every time a response sits unanswered overnight, because a client's intent to book has a shelf life that a "we'll get back to you" workflow routinely exceeds.
Wenya is a scheduling keyboard for WhatsApp, iMessage and Telegram that makes booking as fast as sending a message, with timezone handling built in. Try it at wenyawanna.ai
Sources: GitLab Remote Work Report, Stanford University / Nicholas Bloom remote work research, Harvard Business Review lead response time research, Accenture Customer Experience Research, Ofcom Communications Market Report 2023.