Changelog
Follow up on the latest improvements and updates.
RSS
You can now enrich Salesforce fields directly inside a Distro flow before routing.
Use cases
- Lead/Contact form submissions – enrich non-Concierge form fills (trial sign-ups, eBook downloads, webinars) before routing
- Bulk list uploads – enrich post-event lead lists before dedupe and routing
- Periodic refreshes – refresh routing criteria on existing records using Schedule Trigger
How it works
Add the Enrich node between the Entry Rule (and any Delay) and the first Routing Rule, CRM Matching, or Duplicate Match node. Inside the node, pick the Salesforce field to enrich and the enrichment waterfall to use. The Provider and waterfall configurations are the same as Concierge and Chat.
The Overwrite toggle controls existing values only:
- Off – we only write the enrichment value when the Salesforce field is empty
- On – we always overwrite the existing Salesforce value
After enrichment, routing rules evaluate against the updated Salesforce values, so you can route on what you just enriched.
The Enrich step appears inline in the log. For each field, you'll see the SFDC field, the previous SFDC data (or "No results found"), the enrichment data, whether Overwrite was on, and the new SFDC data.
Limitations
- Lead and Contact routers only – Account routers to follow
- Enrichment values aren't available in variables yet – you can route on enriched data via SFDC rules, but you can't reference the enrichment output directly in variables (e.g. for notification templates) - will follow...
Learn more here
Spam Checker is now live in Chat! The same checks that filter spam form submissions in Concierge now run inside your Chat Journeys – so bots and fake emails get caught mid-conversation, before they ever reach a rep's calendar.
Two use-cases:
- Protect rep calendars – gibberish, disposable, and role-based emails are filtered out before scheduling is ever offered
- Quiet handling – continue the conversation for flagged visitors without offering scheduling, so spammers never learn they were caught
How it works
- Add the Spam Checker node to your Journey after the visitor's email is collected
- The conversation branches on the result: Not Spam continues to qualification and scheduling, Spam follows whatever path you build for it
- Optionally write the score to the Spam Score data field and map it to your CRM
Things to note
- The node needs the visitor's email, so it must sit after an email collection step
- Checks, weights, and thresholds are configured in the same Spam Checker settings you already use for forms – one configuration covers both
Learn more here
The Chili Piper MCP just got stronger. The latest round of MCP and Edge API improvements include:
- OAuth for MCP. Connect Claude Desktop or claude.ai to your Chili Piper tenant via a custom connector. No API key, no mcp-remote bridge. Admin-only for now, with access to every API scope once connected
- MCP tool calls now show in tenant logs. In Command Center → Integrations → API logs, you can see whether a call came in via MCP or the HTTP API (Edge)
- Reschedule and reassign. The new meeting-patch endpoint lets you change a meeting's time or host
- Run-now for Scheduled Trigger in Distro. Fire a Scheduled Trigger router on demand via Edge/MCP, no need to open the app
- Suggested Times widget + single-use scheduling links. scheduling-link-init now accepts outputs: ["SuggestedTimes", "SingleUseLink"] and returns inline-CSS email HTML for Suggested Times (pair with the Gmail MCP to auto-draft emails with times baked in) and a one-time-use scheduling URL. Handoff supports the same outputs via Edge today, with MCP coming soon
- Richer filters on list endpoints. Agents no longer have to paginate through everything. New filters on meeting-list-put (status), meeting-export-v2-put (assignees, hosts, bookers, meeting types, status), distribution-list-put (name, assignment type), and team-list-put (name, member)
- hostName on meeting responses. Meeting GET and list endpoints now return hostName alongside hostId and hostEmail, removing the need for a follow-up /user/find call
- More data on distribution responses. distribution-list-put now returns current level, who's up next, who's on vacation, who's reached a cap, and when the distribution last reset, in addition to team and weights
Check out the support article for more information.
Scheduled Trigger is out of beta and live for all customers. Distro routers can now run on a recurrence, on a specific date, or on demand. A Records for Processing node fetches the records to route using a SOQL query you define.
What's new since beta:
- Visual SOQL builder. Set conditions with a familiar UI instead of writing raw SOQL (raw SOQL is still available if you prefer it)
- 2,000-record cap removed. Each run was previously capped at 2,000 matched records. It's no longer capped.
A note on record volumes: even with the cap removed, run smaller batches where possible. Split large jobs into multiple narrower queries, and schedule outside business hours or over the weekend to minimize disruption to live routing.
Trigger types available:
- Recurring Schedule – e.g. every day at 8am.
- Specific Date – one-off run at a chosen time in the future.
- On Demand – kick off a run whenever you like. Also callable via the Edge API and MCP (resource-scheduler-run), so you can trigger a routing job from an external workflow, an AI agent, or an automation tool.
Check out the support article for more information.
Shared Assets
🚀 Chili Assist - Now available in Logs
Chili Assist now works in Logs. Ask questions in natural language to understand what happened on a given record, in addition to the existing Rules, Teams, and Distributions use cases. We're continuing to expand where Chili Assist is available across the product.
To access Chili Assist, look for this icon in the top right corner of the Logs, Rules, Teams, and Distribution pages.
🚀 Reminders as a Standalone Asset
Reminders are now a proper Asset, exposed directly in the navigation within Meeting Types. They have always been an Asset under the hood, but the previous UI made it unclear that editing a Reminder inside a Meeting Type affected the underlying Asset. Now, Reminders are easier to manage and reuse across Meeting Types.
🚀 Navigation Update
We've simplified and condensed our navgiation menu. Key changes include:
- Fewer items, with related items bundled together
- All Flow-building capabilities (Concierge, Web Experiences, Handoff, and Distro) live under a single Flow item
- Chat AI is now a Chili Agent
- Knowledge Base is an Asset, so it can be referenced by other agents
- Reminders are explicitly exposed as an asset within Meeting Types
- Can't find what you're looking for? Try searching
You'll see a guided tour of the changes the next time you log in.
Integrations
🚀 Storylane
Chili Piper is now embeddable directly inside Storylane interactive demos. When a prospect hits a moment of genuine interest, a scheduling prompt appears and they book with the right rep without leaving the demo.
Check out the integrations page and our blog post for more information.
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:
🚀 We've launched the 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.
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.Load More
→