Feature Requests

When a new user is added to Chili Piper, they can immediately create their own scheduling links. There is no way to restrict this capability by default and require admin approval before a user can create links. Admins should be able to set a default state where new users cannot create personal scheduling links until the permission is explicitly granted. Uncontrolled scheduling link creation by new users can lead to inconsistent booking experiences and links that bypass approved routing logic. Default restriction ensures all scheduling goes through approved channels.

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 is no view-only permission level in Chili Piper. Giving a sales leader access to metrics requires granting them settings permissions they shouldn't have, creating an unnecessary security risk. Chili Piper should support a view-only access level that allows leaders to see reporting and metrics without the ability to change any settings or configuration. Read-only access for reporting consumers is a standard enterprise permission requirement. Without it, organizations are forced to either over-permission leaders or deny them visibility into data they need to manage their teams.

Admins have no way to view or control individual user-level settings across the workspace. Users independently configure meeting buffers, reminder settings, reschedule link expiry, and advanced scheduling options, leading to inconsistency at scale. Give admins the ability to override, lock, or set workspace-wide defaults for individual user settings, including meeting buffer times, advanced scheduling options, reminder configurations, and reschedule link behavior. Enterprise customers need governance and standardization across large user bases. Without admin override capability, configuration drift is inevitable and ops teams spend significant time on per-user troubleshooting that should never need to happen.

Salesforce auto-provisioning keys off the full Salesforce user list, which is far larger than the Chili Piper user base (one customer has ~2,000 SFDC users vs. ~700 in Chili Piper). Run as-is, it bulk-adds people who shouldn't have access and consumes licenses. There's also no native "is a Chili Piper user" field on the Salesforce user object to key off, so scoping today requires a custom boolean checkbox field. Give admins control over what auto-provisioning does: an assign-only mode that updates license, team, and workspace for users already in Chili Piper without creating new ones, plus the ability to scope creation to a filtered subset (criteria, report, tag, or a boolean field on the user object). Access is often an approval-based human decision, not cleanly team-defined, so all-or-nothing provisioning either floods the instance with unauthorized users and wasted licenses or forces manual provisioning that doesn't scale. Past provisioning gaps have caused real damage for this account (a user wrongly assigned as admin, a sandbox mess that took days to fix).

User provisioning and deprovisioning in Chili Piper is manual. When employees join or leave, admins have to manage access directly in the product rather than through their identity provider. Requested behavior: Support SCIM (System for Cross-domain Identity Management) so that user provisioning, deprovisioning, and role updates can be managed automatically through an identity provider like Okta or Azure AD. Why it matters: Manual user management doesn't scale and creates security risk when offboarding is delayed. SCIM is a standard expectation for enterprise buyers and a common blocker in security reviews.

Workspace admin - a separate role that allows a user to be an "Admin" in a specific workspace only. Allowing that person to manage user's calendar/schedule availability

The Chili Piper MCP today is oriented to admin/org-level access. Individual reps can't use it to pull their own numbers, e.g. their meetings, cancel/no-show rates, and other personal metrics. Requested behavior: an end-user version of the MCP scoped to the individual, so a rep can query their own meetings and performance metrics without admin-level access. Why it matters: reps want self-service visibility into their own performance without routing through an admin or a separate report.

Sales reps have no way to see why a particular lead was routed to them. Today they rely on the ops team (or external tooling for custom notifications) to explain assignments, which creates manual back-and-forth and slows reps down. Requested behavior: give reps a self-service view, at the rep level, that explains why they received a given lead (the rule/owner-match/distribution logic that fired), without needing admin access or an ops request. Why it matters: assignment transparency builds rep trust in routing and removes ops as a bottleneck. Reps currently can't answer "why is this mine?" on their own.

Chili Piper's chat spam checker and blocking exist, but the block action requires an admin. SDRs and agents are the ones actually fielding chats, so when a spammer, bot, or off-topic visitor (e.g. students) keeps chatting in, the front-line rep can't stop it themselves, they have to escalate to an admin or "sit there and take the hits" while the conversation continues. Reps handling live chat should be able to block an unwanted visitor directly from the conversation, without admin involvement. Admins should still control whether this permission is granted and be able to review or reverse blocks, but the day-to-day block action shouldn't be gated behind an admin. Front-line chat teams can't respond quickly or keep their queue clean when every block is an escalation. Pushing blocking down to the reps who see the spam first cuts response friction and reduces the noise that buries legitimate chats.