Shared Assets
:🚀 Updated Reassignment Flow -
Help ArticleAdmins can now reassign meetings more efficiently through a simple Scheduler pop-up. This gives admins full flexibility and control over how meetings are Reassigned, whether they need to follow strict distribution logic or reroute using Handoff logic. It reduces manual steps and helps maintain clean routing even post-booking.
Example use case:
An admin sees that an AE is on vacation. They open a meeting from the calendar, hit “Reassign,” and either choose the next rep in line (per distribution rules) or rerun the Handoff logic to find the right fallback based on routing paths and ownership rules.
🚀 Update Salesforce reassign buttons to always use the Scheduler -
Help ArticleSalesforce event object buttons used for reassigning now open the ChiliCal Scheduler directly. Workspace Managers and Admins get a side panel view with appropriate permissions. It unifies the reassignment experience and ensures that all permission checks and distribution logic are respected, while giving visibility into the meeting’s context.
Example use case:
An SDR manager needs to reassign a meeting originally booked by a now-departed teammate. From the Salesforce event record, they click “Reassign” and are immediately directed to the scheduler to select a new assignee without leaving their workflow.
🚀 New Available Updates on the Confirmation screen in Branding & Language
The confirmation screen now clearly displays:
- Who you are meeting with
- Time
- Guests
- A reschedule button
- Booking details
It enhances transparency for the booker and the prospect, reducing confusion and support requests while improving the professional appearance of the booking flow.
Example use case:
A customer books a demo and immediately sees all relevant details in one place. If they need to reschedule, they can do it instantly from this screen without searching for the confirmation email.

🚀 Show API names in Rules (SFDC and HubSpot)
Admins can now toggle on “Show API Names” when editing Rules (outside of Routers) to see the underlying field API names, including custom relationships like Chili Piper’s LeadtoSQL_rc. This makes it significantly easier to distinguish between similarly labeled fields, especially in complex CRM setups. It’s a fast, low-friction way to avoid misconfigurations and troubleshoot faster.
Example use case:
An admin is building a rule to route based on a custom field called "Region." There are two fields with similar names, but by toggling API names on, they identify the correct one and avoid breaking their routing logic.


Distro
:🚀 Additional fields in Create Opportunity and Task nodes
Admins can now configure more fields when using the "Create Opportunity" or "Create Task" nodes in Distro. Previously, these nodes were limited to a fixed set of 4–6 fields. Teams can now ensure required fields (like Opportunity Stage, Custom Task Type, etc.) are properly populated from the routing flow itself, avoiding manual Salesforce edits or failed task creation.
Example use case:
A sales org needs every task created from a routing event to include a “Due Date” and “Campaign ID.” Now, these can be added directly to the node, eliminating the need for follow-up by the rep or admin.

Form Concierge
:🚀 Enrichment For Form Shortening -
Help ArticleForm Enrichment for Form Shortening lets Chili Piper automatically fill in form fields using data from providers like LeadIQ, Apollo, and ZoomInfo. When a visitor submits a form, Chili Piper uses their email domain and other details to pull enriched data (such as company size, industry, or location) and map it to your CRM fields. This means you can remove those questions from your form, making it shorter and faster to complete, without losing important qualification data.
Example Use Case
A form asks only for Name, Email, and one key question, while enrichment supplies company size, industry, and job title from ZoomInfo—delivering fully qualified leads without adding form friction.
ChiliCal
:🚀 Improve Buffer Handling over busy slots
When buffer times block a slot (and your workspace doesn’t allow scheduling over busy times), users now see clear feedback either on hover (if buffer display is enabled) or with a detailed error message. Reduces frustration and booking confusion. Users now understand why a slot is unavailable, whether it’s due to the meeting or just the buffer overlapping.
Example use case:
A prospect sees an open time, but can’t book. Previously, the system gave a generic error. Now, it explains “Meeting Buffer overlaps with a busy slot,” helping the user choose a better time without needing help.
