Feature Requests

The current calendar visibility in ChiliCal cannot be scoped by workspace or by user. Teams with specific privacy requirements (HR data, manager calendars set to private in Google Calendar, etc.) need to control who can see calendar details based on workspace membership. Admins should be able to restrict calendar visibility on a per-user or per-workspace basis in ChiliCal, so that a user outside a given workspace cannot view or access calendar details belonging to users inside it, regardless of the account-wide Free/Busy setting. Full calendar exposure across workspace boundaries doesn't meet the compliance and privacy requirements of all organizations. Booking and routing only require free/busy status, not full event detail, so scoped visibility controls would let teams protect sensitive calendars without giving up existing scheduling functionality.

I frequently want to give Round Robin credit back to a user for a meeting due to extenuating circumstances (e.g. misrouted but can't reassign due to re-assignee's restrictions on minimum scheduling window). It becomes a pain to figure out which distro triggered the meeting and then credit the user back (and vice versa, deducting a credit for the new assignee!). There should be a way to manage credits from the meetings report so I don't have to go searching around. Similarly, we should be able to do this from the concierge log.

This is a small thing that customers expect us to have, but we don't. We can only show weekly times which I think should stay as the default as it positively impacts show rates by influencing meetings be booked closer to the date it was scheduled BUT some customers and prospects prefer a monthly view especially if they are leaving tools like calendly.

Chilipiper is limited in what we're able to customize in web experiences currently. Given this is a major part of the higher chilipiper tier the expectations of customers/prospects is more flexibility. More visual customizations for web experiences (sizing, png/jpg, animations, audio in chat, chat icon).

Permission levels are too broad. Granting a sales manager the ability to edit team groups also gives them access to unrelated settings they shouldn't have visibility into. Admins should be able to assign more granular permissions to specific roles, such as allowing a sales manager to edit team groups without granting broader admin access. Overly broad permission levels force a choice between too much access or no access. Granular permissions let organizations align access to actual job responsibilities without creating security risks.

There is no way to make one booking dependent on another. An admin can offer a meeting type, but cannot require that the booker also schedule a second, different meeting as part of the same flow, and cannot hold the first meeting unconfirmed until they do. Follow-ups are treated as entirely new, unrelated meetings. Requested behavior: at the meeting type level, let an admin mark a second meeting type as required. When someone books the gated meeting type, the flow presents the second booking before finalizing, and the first meeting is not confirmed until the follow-up is scheduled. If the booker abandons the second step, the first booking does not stand. Use case: the customer offers an internal 1-1 that is only worth holding if a paired external follow-up call is also on the calendar. External partners are the ones doing the booking, so there is no internal rep in the flow to enforce it manually. Existing workarounds prompt the booker toward a follow-up but never block confirmation, so the pairing is optional in practice and partners skip it, which is exactly the outcome they need to prevent. Why it matters: without a hard gate, "paired" meetings are a suggestion. Teams offering a meeting only as part of a two-step commitment have to police it after the fact or stop offering it at all.

Our end users would like the capability to automatically detect and mark no-shows in Chili Piper when using Microsoft Teams for meetings. It looks like this is being done for Zoom, but I'd thought I would submit the same request for Microsoft Teams since that's what our team uses.

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.

Have a feature that allows Admins or users to set a maximum duration for which a one-time link is valid and usable; after that, it automatically expires in X days.

When a rep leaves a company and their account is deactivated, any personal booking links they shared via email or embedded in outreach continue to resolve to a broken or dead-end page. There's no way to redirect that traffic to an active rep, queue, or router. Allow admins to configure a redirect for deactivated users' personal booking links, so anyone who clicks an old link is sent to an active booking experience rather than hitting a dead end. Reps share booking links in email signatures, outreach sequences, and marketing materials. When they leave, those links don't disappear and prospects who click them are left with a broken experience at a critical moment in the buying journey. A redirect turns a dead link into a recoverable interaction.