Conversion & Scheduling

We use the edge API to see available sessions - after which we grab the meeting link. We would like the option to grab the single-use meeting link instead of the persisted one. Thank you!

The customer wants the ability to restrict scheduling links to allow bookings only within the current quarter. This feature is not directly supported and would require manual adjustments.

Adding meeting reminders through a webhook can enable users to send reminders with their tools of choice, from different SMS providers to WhatsApp, AI voice agents and more!

Group booking links require a pre-configured set of participants. Teams that need to include different combinations of attendees depending on deal context, such as adding a CS and SA to an AE's onboarding link at close, would need a separate link for every possible combination. Chili Piper should support passing additional attendees as URL query parameters at runtime, for example ? assignee=user1@company.com , user2@company.com , so a single base link can be composed dynamically from Salesforce or any external system. This removes the need to pre-build every permutation of group meeting and makes post-close scheduling workflows automatable without manual link management.

Group booking links can only be created by admins at the workspace level. Reps who want to set up a booking link that includes themselves and one or more colleagues, including people outside their workspace, have no self-service way to do it. Allow individual reps to create their own group booking links that aggregate availability across multiple participants, including people outside the workspace, without requiring admin involvement. Cross-functional deal motions, such as an AE and an SE joining a discovery call, or a CSM and a product specialist running an onboarding session, are extremely common. Requiring admin setup for every multi-person booking link creates unnecessary overhead and slows down collaboration that reps should be able to self-serve.

There's no cap on how many times a guest can reschedule. A single meeting can be rescheduled indefinitely, with no mechanism to flag chronic reschedulers or route them to a different experience when it becomes clear they're unlikely to hold a call. Allow admins to configure a maximum number of reschedules per meeting at the Meeting Type level. When the limit is reached, the guest should see a message directing them to contact the company directly rather than continuing to reschedule. Unlimited rescheduling wastes rep time, distorts pipeline data, and signals disqualified leads that are better handled directly. A reschedule cap gives teams a lever to protect rep capacity and route low-intent prospects appropriately.

Chili Piper's scheduling capabilities are built around virtual meetings. Teams that need to book in-person meetings, such as field sales calls, on-site visits, or conference booth appointments, have no native way to manage the distinct requirements of in-person scheduling, including location details, directions, travel buffers, or physical capacity constraints. Extend Chili Piper's scheduling capabilities to support in-person meeting types, including the ability to specify a physical meeting location, add location-based details to the calendar invite, and configure scheduling parameters appropriate for face-to-face meetings. Enterprise and field sales teams rely heavily on in-person meetings. Without native support, they either shoehorn virtual meeting configurations to approximate the experience or manage in-person scheduling entirely outside Chili Piper, which fragments data and undermines platform adoption for a significant portion of their meeting activity.

Meeting descriptions only support plain text. There is no way to add hyperlinks, bold text, italics, bullet points, or numbered lists. Teams sharing relevant resources like articles, reports, or prep materials are forced to paste raw URLs, and any structure in the description has to be approximated with plain characters. Meeting descriptions should support standard rich text formatting, including hyperlinks, bold, italics, and lists. Meeting descriptions are often the first thing a guest reads before a call. Plain text limits the ability to share context clearly or direct guests to relevant resources without making the description look messy. It is one of the few areas where the native calendar experience currently beats Chili Piper.

Phone is not available as a native meeting location option in Meeting Types. Teams that conduct meetings by phone have no way to configure which phone number should be used, such as the host's, assignee's, booker's, or guest's number, or prompt guests to provide their number at booking. This means phone-based meetings require manual workarounds for both setup and guest communication. Admins should be able to select phone as a meeting location type, configure whose number is used or displayed, and optionally prompt guests to submit a phone number as part of the booking flow. The confirmation and calendar invite should reflect the correct copy and phone details for the meeting. Phone is a standard meeting format, particularly for CS, onboarding, and sales teams. Without native support, teams are forced to either use a generic location field or route phone meetings through a different tool entirely, creating inconsistency in how meetings are set up and communicated to guests.

Ability to set router rules based on dates and display team availability for a selected date (for events with different reps)