Admin Center
:🚀 UserRole and Profile fields now available in SFDC Provisioning Rules
Admins can now access UserRole and Profile fields in provisioning rules, enabling them to filter by role names and profile names, in addition to just IDs. Faster, cleaner rule setup that scales across complex territory trees.
Example:
Create a single rule like UserRole Name contains "Sales" to provision all Sales roles across NA, EMEA, and APAC without maintaining long ID lists.
🚀 Extension Status in User Management Table -
Help ArticleVisibility in the User Management table of who has downloaded the browser extension. This speeds up rollout and ensures reps have the Chili Piper Chrome extension as part of their workflow.
Example:
After a new team is onboarded, the admin filters for “Not Downloaded,” extensions send reminders to those users to install it, and ensure they understand how to use it.
ChiliCal
:🚀 Pass multiple assignees in URL
Support for ?assignee1={slug}&assignee2={slug}, along with ?assignee={slug}, to predefine which assignees a booking link should use.
Example URL:
Chat
:🚀 JS Events API Options -
Help ArticleReal-time browser events for key chat and booking milestones such as chat_targeted, chat_responded, availability-loaded, timeslot-selected, booked, and booking-confirmed. This lets teams capture analytics, measure funnel drop-off, and trigger custom workflows in tools like GA, Segment, or a webhook listener.
Example:
If no-free-slots fires, trigger a redirect to a fallback calendar or display an offer. When booking-confirmed fires, send a conversion event to GA and push the meeting payload to your data warehouse.
Distro
:🚀 Send to Router Node -
Help ArticleYou can now chain routers together directly, without needing to use the Update Field node and helper fields. This eliminates field hacks, reduces SFDC clutter, and gives clear, auditable subflows. Modular routing becomes much easier to build and maintain.
Examples:
- Match a Lead to an Account, then send that MatchedAccount to an Account router
- Route a Lead and assign the SDR in one router before sending the same record to an alternative Lead router to assign the AE
- Chain multiple routing decisions without leaving Distro
🚀 Working Hours Round-Robin Distribution Type -
Help ArticleA distribution algorithm that prioritizes users currently within their ChiliCal default working hours, then falls back to strict round-robin when nobody is working. This improves speed to lead and real-time coverage without sacrificing long-term fairness.
Example:
A lead arrives at 5:30 pm. Madonna is up next, but off at 5:00 pm. Kevin is on until 6:00 pm, so he gets the record now. Tomorrow morning Madonna receives the next two to stay even.