Feature Requests

Meeting buffers are set globally, applying the same values to all users. Reps with different schedules and working styles have no way to configure buffers that reflect their individual needs. Each user should be able to set their own meeting buffer times independently, rather than being subject to a single global buffer setting applied across the entire team. A global buffer that works for one rep may be too long or too short for another. Individual buffer control respects different working styles and prevents one team member's preferences from impacting everyone else's availability.

Calendar buffers are calculated in calendar days, not business days. A buffer set to prevent Monday morning meetings isn't respected when a booking happens on a Friday or Saturday. Admins should be able to configure buffers that respect business days, so that scheduling constraints like minimum lead time are calculated based on working days rather than calendar days. Calendar-day buffers produce unexpected results for teams that only operate Monday through Friday. Business-day buffers ensure scheduling rules behave as intended without manual workarounds.

Meeting Type-level booking caps are siloed. Users with multiple Meeting Types can be over-booked in aggregate even if each type has its own limit, because there's no way to enforce a cap across types simultaneously. Allow admins or users to configure a global booking cap that limits the total number of meetings scheduled across a selected set of Meeting Types, not just per individual type. AEs and other reps who use multiple Meeting Types across different deal stages need to control their total calendar load. Without a cross-type cap, per-type limits give a false sense of control and calendar overload remains a real problem.

Availability range is a single fixed window per meeting type. Teams can shorten it to push prospects toward booking sooner (e.g. 3 days out), but if those near-term days are full the prospect simply has no times, there's no way to then reveal later dates. Let admins configure a tiered availability window that starts narrow and automatically extends further out only when the initial window has no open slots, so prospects are nudged toward earlier bookings without being blocked when early dates fill up. Long booking windows correlate with higher no-show/churn (prospects booked far out are more likely to ghost), but a hard short window risks leaving no options behind a busy link. Progressive expansion gets the urgency benefit while preserving a fallback. Today the only workarounds are padding the window a day or two, a multi-meeting link, or an MCP query that swaps links, all of which are manual or heavy.

We need the ability to temporarily block off proposed calendar slots for all assigned internal team members until a client confirms a meeting time. Use Case: When sharing booking links for large stakeholder discussions, our internal team members often get booked over by other meetings before the client selects a time. This causes scheduling conflicts and forces us to reschedule. Benefit: This would prevent internal double-bookings, protect our team's schedule, and ensure we can honor the slots presented to high-value clients.

A meeting type created for a specific conference with the configured dates and timezone doesn't carry those settings into Handoff. This is causing more clicks for bookers when they try to book a time during the conference.

The ability for the online / offline toggle to be linked to someone's calendar working hours. So they do not have to remember to turn their availability on and off

Preventing bookings on company holidays currently depends on each user manually blocking their calendar. Anyone who forgets or is newly onboarded leaves their calendar open on days no one should be booked. Allow admins to define a list of org-level holidays that automatically block availability across all users, routers, and distributions, regardless of individual calendar settings, AND are taken into consideration for CRM routing.

Custom schedules are created at the individual user level and can't be shared. Admins who want to apply the same schedule configuration across a team, department, or group have to recreate it manually for each user. Allow admins to create custom schedules at the workspace level and assign them to multiple users or groups at once, rather than requiring per-user creation. Manual per-user schedule setup doesn't scale. For organizations onboarding new teams or standardizing availability across a large user base, workspace-level schedule management is a basic time-saving capability that also reduces configuration drift.

Chat routing to respect real-time rep availability, not just static schedules or round-robin rules. Specifically: Detect when a BDR/AE is actively on a call (Zoom, Teams, Google Meet, phone) Pull presence/availability from calendar status (busy, in a meeting) and communication tools (Teams, Slack, Zoom status) Automatically skip or deprioritize reps who are unavailable when routing inbound chats Resume routing to the rep once they're free, without manual intervention Goal is to avoid sending live chats to reps who can't respond, which hurts speed-to-lead and creates a bad prospect experience. Applies to Chat AI routing, but the underlying presence/availability signal could also inform Distro/CRM Routing Flows and Concierge meeting handoffs.