Changelog
Follow up on the latest improvements andΒ updates.
RSS
Shared Assets
π
Chili Assist - AI to Help with Rules, Teams, and Distributions
Chili Assist is an AI assistant embedded in the Chili Piper admin UI. Instead of manually configuring conditions, members, or calibrations, describe what you want in plain language, and the assistant builds it for you. You review the change on the page and save it with the standard Publish button.
One assistant, three asset types β all used across every Chili Piper product:
- Rules β routing rules, including ownership rules and cross-object references;
- Teams β groups of users referenced by distributions and ownership rules;
- Distributions β distribution configuration, weights, and Credit/Skip calibration.
Check out the support article for more information.
Web Experiences
π Post-Form Enrichment for Concierge
Post-Form Enrichment runs after the trigger (third-party form/router link/in-app) and before the first rule. Unlike Form Shortening, Post-Form Enrichment works on every Concierge trigger, including router links and Edge/MCP.
Post-Form Enrichment is a new node in the Concierge flow builder β Enrich β that runs after the prospect submits the form. It pulls data from LeadIQ, Apollo, Lusha, ZoomInfo, or Clay based on whatever was submitted (which could be an email alone), and those enriched fields are used by routing rules.
Post-Form Enrichment is the right choice when you want Chili Piper to do more work with less prospect input. Use cases:
- Your form asks for email only, and your routing rules depend on firmographic data such as Country, Company Size, or Industry.
- You are routing through Concierge programmatically (via the Edge API or MCP) from a partner integration, AI voice agent, chatbot, or custom app, and want enrichment applied automatically without that upstream system integrating with an enrichment provider directly.
- You want the booked meeting record to carry enriched fields (Company Name, Title, Revenue, etc.) into your CRM notifications, calendar invites, and downstream automations.
Check out the support article for more information.
π Multi-Language in Chat
Chat can now detect and converse with visitors in 31 languages. Greetings, node text, and conversations automatically adapt to the visitor's language. A single journey serves all languages β there is no need to create separate journeys for each language.
Until now, Chat AI only worked in English. Customers with international web traffic had to either add a custom guidance instructing the bot to respond in the visitor's language, or duplicate entire journeys per language.
Check out the support article for more information.
π Enrichment in Chat
Enrichment is now available in Chat. Same setup, same enrichment waterfalls, same providers as Concierge.
A new Enrich node in the Flow Builder that runs mid-journey once the visitor has shared their email. It pulls data from LeadIQ, Apollo, Lusha, ZoomInfo, or Clay and writes it straight into the visitor's data fields.
In Chat Journeys, enrichment also reduces the number of questions the visitor is asked. Any later Send Data Field node is checked against the enriched record: if the field is already populated, the question is skipped automatically. Applies to both Chat and Chat AI.
Check out the support article for more information.
Shared Assets:
π Chili Piper MCP
MCP is an open protocol that lets AI assistants interact with external tools. Our MCP server exposes existing Edge API functionality β users, meetings, routing rules, distributions, workspaces, teams, and scheduling β directly from the terminal.
Once connected, you can ask your AI assistant things like "list all meetings this week", "find user by email", or "adjust distribution weights" β and it reads from and writes to your live Chili Piper data.
What's included
- Organization and tenant configuration
- User management (search, invite, update licenses)
- Workspaces and teams
- Distributions (create, update, adjust weights, delete)
- Routing rules (create, modify, delete)
- Meetings (list, export, cancel, no-show)
- Scheduling links and availability
- Handoff
- Concierge router listing and logs
- CRM operations (lookup, cancel, no-show by CRM event ID)
Check out the support article for more information.
π Form Router:
Post-Form Enrichment for Form Router/Concierge
Post-Form Enrichment runs after the trigger (third-party form/router link/in-app) and before the first rule. Unlike Form Shortening, Post-Form Enrichment works on every Concierge trigger, including router links and Edge/MCP.
What's New
Post-Form Enrichment is a new node in the Concierge flow builder β Enrich β that runs after the prospect submits the form. It pulls data from LeadIQ, Apollo, Lusha, ZoomInfo, or Clay based on whatever was submitted (which could be an email alone), and those enriched fields are used by routing rules.
How it works:
- Drop the Enrich node into any Concierge router
- Pick the data fields you want to enrich and assign an Enrichment Waterfall
- Publish
Works on every Concierge trigger: Router Link, Third-party Form, In-app Button β plus Edge API and MCP.
Check out the support article for more information.
Scheduling via the Chili Piper API is now fully programmatic.
Programmatic scheduling means booking a Chili Piper meeting without sending the lead through any Chili Piper UI. Your own code β a backend process, a custom frontend, an AI assistant β calls the Chili Piper API, picks a time, and books the meeting directly.
You have three starting points:
- A Concierge router β routes a lead using data you submit (plus CRM data when the guest matches an existing record);
- A ChiliCal scheduling link β books against a link or user you've already identified;
- A Handoff router β routes from an existing CRM lead or contact.
All three use the same two-step pattern.
When to use:
- Concierge: you want Chili Piper to evaluate routing rules and assign the meeting to the right team or user based on the lead's data.
- Schedulinglinks: you already know which scheduling link to book against β for example, a lead-owner link resolved from your CRM, or a specific group link tied to a team.
- Handoff: a rep is handing off a lead to another team member β for example, an SDR booking a discovery call with an AE. Handoff uses the rules in a Handoff router to evaluate availability and returns time slots per routing path.
Some example use cases:
- Voice agents and custom integrations can book meetings server-side without redirecting through the Chili Piper scheduler
- AI agents on MCP can list available scheduling links and book
Full details can be found here.
The Meeting Prep agent can now access Cases in Salesforce and Tickets in HubSpot, in addition to existing data sources.
How it works:
- Access is based on the associated Account (Salesforce) or Company (HubSpot) β the agent finds the appropriate account via the primary guest's email, then pulls related Cases or Tickets
- The agent can read all content from the Case or Ticket
- This toggle is OFF by default β customers need to activate it to use it
π Marketo Integration for Chat
The Marketo integration for Chat is now live for all customers.
What's included:
- Marketo in Rules β Lead and Company fields from Marketo are available as conditions in any rule within the journey
- Create/Update Lead β includes an optional Add to List action within the same node
- Update Field β update lead fields in Marketo directly from the journey (company fields coming soon)
- Log Chat Activity β creates a custom activity called "New Chili Piper Chat" in Marketo, with a configurable delay to ensure the conversation is finished before logging
- Log Meeting Activity β creates a custom activity called "New Chili Piper Meeting" when a meeting is booked via Chat
Data field mapping:
When you connect Marketo, a new Mapping to Marketo option appears below Mapping to Salesforce in the data field menu. Default fields (first name, last name, email, etc.) will be auto-mapped.
Setup:
- In Marketo, create a new Installed Service and allocate a user to get a Client ID and Client Secret
- Navigate to Integration β Web Services β REST API to get your Endpoint URL
- Enter the Client ID, Client Secret, and Endpoint URL in the Chili Piper Integrations menu within Admin Center
Coming soon: Add to Program β the Marketo equivalent of "Add to Campaign" in Salesforce.
Support article: https://help.chilipiper.com/hc/en-us/articles/49822563653779-How-do-I-configure-the-Marketo-integration-in-Chat
π Account Identification (De-anonymization) in Chat
Chat now supports account identification, allowing Chili Piper to detect and enrich firmographic company information for anonymous website visitors through a script installed on pages where the chat widget is deployed.
Requires an existing contract with
6sense
or Bombora
is required. Chili Piper connects to your existing provider β no separate data contract with us is needed.Setup:
- Connect a provider β go to Admin Center β Integrations β Built-In tab and enable 6sense and/or Bombora
- Ensure the provider's script is already on your website β no extra code required beyond the tag already installed for the provider
- Configure your data fields β go to Admin Center β Data Fields β De-anonymized Company to review and manage captured fields (name, industry, revenue, etc.)
- Set waterfall priority if using both providers β define which provider takes precedence per field by dragging them in the Waterfall Sequence
- Use it in Chat Journeys β open a Journey β Trigger β Show to a specific audience, then build rules using De-anonymized Company fields
Support article: https://help.chilipiper.com/hc/en-us/articles/49793334740499-Account-Identification-for-Web-Visitors
π Chat AI β Knowledge Base Improvements
We've shipped a batch of improvements to how you add and manage resources in the Chat AI Knowledge Base.
- New 'Add Resource' options:
- Whole websiteβ Enter a URL and choose a scan depth: Shallow (1 level), Medium (2 levels), or Deep (3 levels). Previously locked to 2 levels. Results load progressively in a tree, so you can import whole sections (e.g. everything under /resources/customer-stories) or individual pages
- Sitemapβ Unlike Whole website (which stays scoped to the domain), Sitemap reads your sitemap and picks up subdomains too (e.g. help.chilipiper.com, fire.chilipiper.com), capturing content across your entire web presence in a single scan
- Specific webpagesβ No change, comma-separated URLs as before
- New status column:
- The old 'Links Amount' column has been replaced with a status column showing IMPORTED, IMPORTING, or FAILED per entry and per sub-link.
- Tree-like view for imported resources:
- Imported resources now display in an expandable tree grouped by URL path, instead of a flat list.
- Backend reliability: the import pipeline has been rebuilt over the last three months with retry logic, improved error handling, and concurrent processing. Stuck imports should be significantly rarer.
π Chat AI Tab in the Inbox
A new Chat AI tab has been added to the Inbox for all Chat AI customers. Previously, the Inbox only showed conversations that resulted in a live chat. Admins can now see all conversations where Chat AI was involved, whether or not they ended up in live chat.
What you'll see:
- The familiar inbox interface with a dedicated Chat AI tab
- The strategy detected for each conversation (e.g. "talk to a human")
- The full back-and-forth between Chat AI and the visitor
- Actions taken and activity log
- This gives admins a quick way to evaluate how Chat AI is interacting with guests, without digging through the full chat logs tab (which is still available for detailed review).
The Chat AI tab is now also available in ChiliCal My App for end users.
π Smart Parameters in Chat
Chat now supports smart parameters in the URL, allowing you to pass data fields into your CRM beyond standard UTM parameters.
How it works:
- Specify the smart parameter in the data field configuration (e.g. personcountry)
- Append the parameter to your Chat URL (e.g. ?personcountry=Wales)
- The value passes silently through the Update/Create Record node into your CRM
Use case example: Campaign attribution β pass identifiers like GCLID (Google Click ID) or LinkedIn parameters such as ACCOUNT_ID and CAMPAIGN_ID, data that wouldn't be collected through the chat journey itself but is needed in the CRM for lead source tracking.
Important to note: This does not pre-fill form fields within the chat journey. Unlike Concierge or ChiliCal links, the data passes through silently to the CRM.
π Create Task with Conversation Transcript β Now Available Anywhere in a Journey
The Create Task with Conversation Transcript node is no longer limited to live chat paths. It can now be placed anywhere in a journey, including after Chat AI-only conversations, so customers using Chat AI can capture the full conversation as a Salesforce task.
Requirements
: the node needs an identified Salesforce record to create the task against. Make sure the journey has a Send Data Field node (to capture the visitor's email) and an Update or Create Record node earlier in the path.One thing to note
: for Chat AI-only conversations, the transcript is created once the session ends. The session timeout is currently hardcoded to 30 minutes of inactivity β an update is coming shortly to honor the delay timer configured on the node itself.π Slack Markdown in Distro & Chat Notifications
Slack notifications in Distro and Chat now support Slack's mrkdwn formatting, enabling rich text in notification messages.
What's possible:
- Tag individuals or teams β hard-coded or by referencing a Slack ID stored on a custom Salesforce field (e.g. TriggeredObject.Owner.Slack ID)
- Create clickable hyperlinks with custom display text
- Include mailto: links that present a contact option in Slack
- Use @everyone, @here, or @channel mentions
- Apply standard formatting: bold, italic, strikethrough, block quotes
A note on Chat:
The same formatting works in Chat. Dynamic tags depend on what's been collected before the Slack notification node β if you're referencing guest data (e.g. email for a mailto link), make sure it's been captured earlier in the flow.
Slack formatting guide: https://docs.slack.dev/messaging/formatting-message-text/
π MCP (Model Context Protocol) Server β Beta
CURRENTLY IN BETA β it must be enabled by Product before you can connect. Contact your CSM if you'd like to opt-in.
Chili Piper now has an MCP server that connects your Chili Piper account to AI coding tools like Claude Code, Cursor, and OpenAI Codex. MCP is an open protocol that lets AI assistants interact with external tools. Once connected, you can query and write to your live Chili Piper data directly from the terminal.
What's included:
- Organization and tenant config
- User management (search, invite, update licenses)
- Workspaces and teams
- Distributions (create, update, adjust weights, delete)
- Routing rules (create, modify, delete)
- Meetings (list, export, cancel, no-show)
- Scheduling links and availability
- Handoff, Concierge router listing and logs
- CRM operations (lookup, cancel, no-show by CRM event ID)
Shared Assets:
π Distribution Cycle Reset Changes
We've made some updates to the distribution cycle reset settings, including a new home for the configuration and two new features.
Whatβs changed:
The cycle reset now lives in its own dedicated tab (previously under Credits & Adjustments). We've also refreshed the layout and copy within Credits & Adjustments but it's still the same functionality.
New Additions:
- Reset Now button β Manually reset all distributions in a given workspace with a single click
- Yearly reset period β A new option alongside daily/weekly/monthly. When selected, you choose the month, and the reset happens automatically on the first day of that month.
π Meetings Scheduled Column β Calculation Change
We've updated how the Meetings Scheduled column is calculated in distributions β both when editing a distribution directly and in the distribution reporting tab.
Previously:
The column showed meetings scheduled to sit (or already sat) within the period, minus no-shows, minus cancellations, plus/minus reassignments in or out. This meant a meeting could appear in both the Meetings Scheduled count and the Cancelled or No-Show column.
Now:
The column shows meetings scheduled to sit (or already sat) within the period, plus/minus reassignments only. No-shows and cancellations are no longer included in this sum β they still appear in their own dedicated columns.
Whatβs next:
We're planning to surface more details on this page β reassignments in/out, vacation calibration, and mid-cycle calibration adjustments. The column will also be renamed from "Meetings Scheduled" to just Meetings, with inline indicators for scheduled/held, cancelled, and no-show β all visible at a glance within a single column. See the screenshot below for a sneak peek.
π Spam Checker: Feedback mechanism and Allowlist added
Feedback Mechanism
Admins now have access to give feedback about the result of a spam check. The feedback will teach the model and help improve accuracy. Feedback is tenant-specific; therefore, marking ola@piper.com as spam in tenant abc doesnβt mean it will be marked as spam in tenant xyz.
Various ways to provide feedback:
- Testing Page
- Spam Dashboard
- Concierge Logs
Allowlist
Admins can now add email addresses or domains to an allowlist, and those will always be marked as non-spam. When an email or domain is on the allowlist, all other checks will be marked as βskippedβ in the logs because they will not be evaluated.
Concierge:
π Spam Score can now be sent to Salesforce
Spam Score is now supported in Salesforce when using the Spam Checker path.
What changed
:- The Update / Create Record node is now allowed on the Spam path, enabling Spam Score to be written to CRM records
- Added a tooltip to the Spam Checker node to clarify setup requirements
Why it matters
:- Makes Spam Score usable in Salesforce workflows and reporting
- Clarifies how Spam Score data reaches the CRM
Chat:
π Chat AI conversation transcripts are now visible in the Inbox
Previously, when a visitor engaged with Chat AI before being routed to live chat, reps could only see the captured data (email, name, company) but not the actual conversation. This meant taking over a thread without knowing what the visitor had asked about.
What changed:
The full Chat AI transcript now appears in the Inbox conversation view. Reps can see the complete message-by-message exchange between the visitor and the AI before they were routed.
Why it matters:
- Better handoffs β Reps can pick up the conversation with full context instead of asking the visitor to repeat themselves
- Faster responses β No guessing what the visitor needs; it's all visible in the thread
- This also backfills previous conversations, so you'll see Chat AI transcripts for historical threads too.
π Export Chat Conversations
It's now possible to export conversations from the Chat logs!
How it works:
- Set your date range in the Chat logs
- Click "Export Conversations" β a pop-up appears showing the export progress
- Once ready, the status updates automatically (no need to refresh)
- Click the download icon to grab your file, or delete if you no longer need it
Whatβs Included:
The export includes the full conversation details:
- Guest ID
- Timestamp
- Sender (bot, guest, or user)
- Message text
Important Notes:
- The export includes all conversations regardless of the "show anonymous visitors" filter
- Processing time varies depending on export size
- This is different from "Export to CSV" β that option only exports the table view, not the conversation details
Why
:This allows customers to proactively analyse their chat conversations β looking for patterns, identifying common questions, and refining strategies. We'll be adding native conversation reporting to automatically surface themes and trends, but wanted to give access to raw conversation data in the meantime.
Shared Assets:
π Meeting Limits for Assignees on Meeting Types
Admins can now set a meeting limit for Assignees per Meeting Type, controlling how many meetings of a specific meeting type an Assignee can have within a defined time period.
Where to find it:
Admin Center β Workspaces β Meeting Types β Advanced Settings β Meeting limit for Assignees
What's included:
Set a per-assignee meeting cap for a meeting type:
- Apply limits by Day, Week, Month, or Custom timeframe.
- Reset timing and timezone are configurable.
- Uses the same meeting-limit behavior as links, distributions, and personal links for consistency.
Why?
- Helps prevent assignee overload.
- Gives admins better control over capacity.
- Brings Admin Meeting Types in line with existing meeting-limit behavior across the platform.
See the help article for more.
π Functional Update to the Global Calendar Connection
Booker is now able to view an Assigneeβs Calendar Free/Busy Slots via Handoff* when the Assigneeβs Calendar is not connected. Supported for both Google Calendar and O365 Calendar Integrations
Where to find the Global Calendar Connection:
Admin Center β Integrations β Calendar
*
Example in Context:
An SDR is booking a Meeting for an AE via Handoff, but the AEβs Calendar is disconnected from Chili Piper or has not logged in to connect Calendar.
Before
: The SDR would not be able to view the AEβs available times properly, often viewing a blank calendar view, which could result in a double booking.After Update:
- The SDR is able to view the up-to-date times where the AE is available.
- When the meeting is booked, Chili Piper will use the SDRβs Calendar to create the meeting and invite the AE and the Guest.
- Handoff Scheduler view will also denote this if the settings are set to create the meeting in the βAssigneeβs Calendarβ.
Applicable to:
- Viewing the Assigneeβs Calendar in Handoff Scheduler for Instant Booking, Suggested Times, & Inserting Links via Chrome Extension.
- When you add an internal additional guest to the Invite who has not connected their calendar, both in Handoff and ChiliCal view.
What it does not do:
- It is not applicable to Concierge and doesnβt serve as a βFallback Userβ
- It is not applicable to ChiliCal when using βMy Teamβs Linkβ.
- We will not create the meeting using the Global Calendar Connection, only view. Note: This uses sharing permissions, meaning the connected user must be able to view their co-workers' time slots within the actual calendar system for it to work with Chili Piper.
π Person to Lead/Contact Matching β Compare Fields on the Incoming Person
Filters and tiebreakers in person to lead/contact matching can now compare fields on the incoming person record β bringing it up to parity with lead/person to account matching.
Background:
Until now, filters and tiebreakers could only look at fields on the existing record. So you could say "lead status must equal qualified" β but you couldn't compare a field from the incoming person to a field on the existing lead or contact.
How it works:
In the Matching Hub, filters and tiebreakers now support comparisons like:
- Lead Company is equal to Person Company Name
- Contact Support ID is equal to Person Support ID
Why:
- Personal email addresses: If someone submits a form using mary@gmail.com, you can't be certain they still represent the same company. By comparing the company name on the form to the company name on the existing lead, you can confirm it's the same Mary before matching.
- Support ID verification: A customer wanted to ensure that when someone submits a support form, they provide a Support ID that matches the existing contact. If it matches, treat them as the same contact. If not, create a new record for a different use case.
π HubSpot Contact to Company Matching β Additional Domains Fallback
HubSpot customers can now match incoming contacts to companies using additional domains, not just the primary domain.
Background:
Until now, when matching an incoming contact to a company in HubSpot, we only checked the company's primary domain. This meant contacts coming from an additional domain β even one listed on the company record wouldn't match.
How it works:
When a new contact comes in (via Concierge, Chat, or a ChiliCal link), we check for company matches in two ways:
- Look for existing contacts with the same domain and extension
- Match to a company's primary domain β or fall back to additional domains if no primary match
If we match to multiple companies:
- We pick the one with the most contacts
- If still tied, we pick the most recently updated
Admin Center:
π Custom Email Domains
All our customers can now send reminder emails from their domain instead of @chilipiper.com β so guests see reminders@company.com rather than reminder@chilipiper.com.
How it works:
- Enter your domain in Admin Center β Integrations β Custom Domains
- Add 3 CNAME records to your DNS (for domain verification and DKIM signing)
- Wait for AWS to verify (can take up to 72 hours, usually faster)
- Toggle to activate
Why it matters:
- Brand consistency β emails come from customers domain, not ours.
- Guest trust β recipients see a familiar sender domain.
Limitations:
- Email notification when verification completes is not yet implemented β check back periodically.
- One custom domain per tenant.
See the help article for more.
π New fields available in Zapier and Custom Webhook payloads
What's new:
We've added five new fields to meeting created payloads:
- hostTimeZone β the host's timezone
- assigneeTimeZone β the assignee's timezone (if available)
- bookerTimeZone β the booker's timezone (if available)
- ruleIdChili β the unique ID of the rule that created the meeting
- ruleName β the human-readable name of that rule
These fields are now included in both the Zapier integration triggers and Custom Webhooks configured in Admin Center.
Distro:
π Add to Gong Engage Flow node in Distro
Distro customers can now automatically add leads and contacts to Gong Engage flows directly from their routers.
What's new:
A new "Add to Gong Engage Flow" node is available in Lead and Contact-triggered routers. When you add the node, you can:
- Select which Gong Engage flow to use.
- Choose the flow assignee β either the Lead/Contact Owner or a Selected User from your workspace.
How it works:
- If using Lead/Contact Owner as the assignee, the record must have been assigned via an Assign and Update Ownership node earlier in the router.
- If using Selected User from Workspace, no prior assignment is needed β you're specifying the assignee directly in the node.
Setup Requirements:
If you already have Gong connected, you'll need to disconnect and reconnect the integration to establish the new scopes (read workspaces, read flows, assign to flow). You can do this in Admin Center β Integrations β Gong.
Important Note:
The integration user (the admin who authenticates the Gong connection) will need a Gong Engage seat to query the flows. They'll have access to company flows, their personal flows, and any flows shared by other users.
Admin Center:
π User Provisioning Scheduling Enhancements
Admins now have more control over when their user provisioning automations run.
What's changed:
- Every day: You can now select both the time and timezone (previously locked to midnight UTC)
- Every week: You can now select the timezone β still runs at midnight, but you choose which midnight. Day selection works as before.
- Every month: After picking the day of the month, you can now also select the timezone
Why
?This gives admins more flexibility so they know exactly when to anticipate their provisioning automations running β no more guessing based on UTC.
Chat:
π Set fixed/custom Chat AI greeting
Before, Chat AI would greet visitors slightly differently every time, and some users wanted to fully control the greeting. So we added this capability in the Chat AI node.
You now have the choice of "Smart greetingβ (what we've had before) and a "Fixed greetingβ.
π Remove gradient
You can now remove gradient in the widget as well as control the launcher state on desktop and mobile individually.
Shared Assets:
π CMD+F Search Functionality is now available for Concierge and Handoff Routers
You can now use the CMD+F(Mac) or CTRL+F (Windows) to search within the flow builder in Concierge and Handoff Routers.
π New Admin Settings for the Scheduler for ChilICal and Handoff
Admins can now control when internal bookers can override meeting type settings & scheduling rules in the Scheduler.
These settings live under User Controls β Booker Permissions and apply to both Handoff and ChiliCal in the Scheduler.
- Always Show Availability for All Assignees- When enabled, bookers will always see the combined availability of all assignees in the Scheduler for both ChiliCal and Handoff. They wonβt be able to turn off the βShow availability for Allβ settings.
- Allow Bookers to Override Minimum Scheduling Notice- When enabled, bookers can schedule meetings inside the minimum scheduling notice window.
Example
: Itβs currently 9:00 AM ET, and the minimum scheduling notice is set to 2 hours. Typically, the earliest available meeting time would be 11:00 AM. With this setting enabled, a booker can still schedule a meeting before 11:00 AM.The Booker will see a warning that the meeting is outside the minimum notice window, but they can still confirm the meeting.
- Allow Bookers to Ignore Meeting Type Availability Range- When enabled, bookers can schedule meetings outside the configured availability date range for a meeting type.
Example
: Itβs Monday, December 22, and the meeting type availability range is set to 1 week. Normally, a meeting could only be scheduled through next Monday. With this setting enabled, a booker can schedule beyond that range.The Booker will see a warning that the meeting is outside the availability range, but they can still confirm the meeting.
Why This Matters
Internal teams often need more flexibility than external prospects when scheduling meetings. These settings let admins decide when bookers can override scheduling rules, making it easier to prioritize high-value leads without changing the experience for self-scheduling prospects.
π Improved Meeting Reassignment from Admin Center
When reassigning a meeting in the admin center, you will now be able to choose to reassign via a:
- Team
- Distribution
- Individual
This experience is now the same as when you
edit
the meeting from the reassignment flow in the admin center.Note
: This is not the experience if the meeting was booked via a 1:1 or Group link. In these cases, you should search for the specific person you would like to reassign.Why
? 1:1 & Group links only have a host (meeting should go to this specific person, always for this link), whereas all other links have a host and an assignee (who should this go to based on xyz logic).π Improvements to Chili Agents
Meeting Prep
- Stabilized meeting brief generation. Briefs would previously fail because of agent hallucination.
- Updated UI for brief testing. When it fails, the fail warning is persistent. Previously, it was a pop-up that disappeared.
- Updated UI for meeting brief card, now we show which meeting types are applied.
- Better error handling:
- Now we show what required fields are missing when customers try to save the agent without all the required fields.
Spam Checker
Improvements to the LLM to increase the accuracy of the random/gibberish check.
- Added prompt rules to capture alphanumeric patterns
- Added prompt rules to cross-check form fill information with email. For example, a form filled withName: Andre Spicy andEmail: mauricio.icy will be considered spam.
Distro:
π Distro Merge Records Tooltip Copy Update
We've updated the tooltip copy in the Merge Records node to make the Overwrite Field options easier to understand.
What changed
The three overwrite options now use clearer language:
- Always Replace Valuesβ Replaces all values in the record you keep with values from the other record, even if those values are blank
- Replace Blank Fields Onlyβ Only fills in blank fields in the record you keep, using values from the other record. Existing values are left unchanged.
- Replace Non-Blank Values Onlyβ Replaces existing values in the record you keep only if the other record has a value. Blank values from the other record are ignored.
Previously, these tooltips referenced "master record," a term that doesn't exist in Distro β you're simply choosing which record to keep (existing or incoming).
See this article for more information:
Chat:
π HubSpot CRM Integration for Chat
You can now build Chat journeys and integrate with HubSpot for your CRM actions.
See this article for more information:
π Improvements to Chat AI
Mid-Strategy Switching
Chat AI can now redirect visitors to a different strategy even while theyβre mid-strategy. This means Chat AI can dynamically adapt to the true intent of a conversation.
Example
: A user starts down the Create Trial strategy, but Chat AI detects their real need is support, so it transitions them to the Support Question strategy.Knowledge Base retrieval Improvements
Chat AI will provide more accurate and consistent responses.
Example
: Questions about the Concierge flow builder could sometimes be mixed with content related to Handoff flow builder or Distro. This confusion should now be eliminated.Load More
β