Changelog

Follow up on the latest improvements and updates.

RSS

More of your routing, logs, and configuration are now readable and writable from outside the product; long-running tools report progress while they work, and tenants can register multiple SAML identity providers.
What This Looks Like in Practice
Connect the MCP to the AI tool you already use, then ask for what you want in plain language:
  • "Show me every meeting the EMEA team booked last week and which distribution sent them there."
    Assignment history is now on the API
  • "Add this prospect to the Enterprise Outbound cadence."
    The full Salesloft surface is now on MCP
  • "Why did this router fail to publish?"
    You get the actual rejection reason instead of a generic failure
  • "Pull the full transcript of that chat conversation."
    Chat transcripts are now readable, with paging for long ones
If you're not sure where to start, connect it and ask the tool what it can do.
Before You Start
Connecting over OAuth, which is the path most AI clients use, requires an Admin on a paid Chili Piper account. If you need narrower access, you can scope an API key per token instead. Supported clients include claude.ai, Claude Desktop, Claude Code, ChatGPT, OpenAI Codex, Cursor, and Gemini CLI.
Everything that changed is below, grouped by area. Skim for what you use.
What's New
1. Working With AI Tools
  • Claude.ai connects to our MCP server. Anthropic's first-party connector can now authenticate and run against our MCP server, joining ChatGPT, Gemini, and the rest. Tools with very large schemas are routed to a summary list so installs stay reliable
  • Live progress while a tool runs. Long-running tools now stream progress back, so you see each step as availability lookups, routing, and booking work through
  • Error messages that tell you what to do next rather than just reporting failure
2. Salesloft on MCP
The full Salesloft surface is available: list cadences and their steps, find a prospect, read users and connection state, and add a prospect straight into a cadence.
3. Routers and Routing
  • Read and write the full CRM-action chain, including a new Create Event action, across Handoff and Concierge routers
  • Convert Lead and Add to Campaign are configurable on Distro routers
  • Author and read Concierge SpamCheck and Enrichment steps, and read the enrichment waterfall
  • A Concierge router path keeps all its meeting types instead of collapsing to one
  • Write assignment-table assignees and read assignment targets on Concierge routers
  • A failed router publish returns the actual reason it was rejected
4. Logs and Visibility
  • Read Web Experience logs from a new endpoint, filterable by flow type
  • Pull a full chat conversation transcript, with paging for long conversations
  • Chat logs return every assignee, not just the first
  • Read assignment history, who received what and when, with optional filters
  • Edit a Web Experience's AI conversation strategy and guidance from MCP
5. Users, Meetings and Configuration
  • Read and update a full user profile
  • Read and edit Smart Parameters on data fields
  • Edit third-party web form trigger mappings
  • Search the API keys list instead of paging through it
  • Create a meeting type with an idempotency key, so a retried request doesn't create a duplicate
  • Set whether the primary guest is marked as attending when you patch a meeting
  • Read the booking source URL, including page, parameters and UTMs, on scheduling link bookings as well
  • Read send-to and send-from on meeting reminders, and meeting notifications on schedule-simple
6. Single Sign-On
  • Multiple SAML IdPs per tenant. A tenant can now register more than one SAML identity provider
  • A rejected SSO login returns a clear access-denied message instead of a server error
7. Fixes
  • Patching meeting attendees no longer drops the primary guest
  • Flexible round-robin handoff no longer errors when several hosts qualify
  • Updating a user no longer wipes fields you left out of the request, and a duplicate slug returns a clear conflict instead of a server error
  • The assignment-tables "by-ids" lookup works again, and Concierge log pages are capped to a sane size
  • Deleting a live Web Experience AI conversation strategy returns a useful hint instead of a 500
Learn more about connecting to our MCP.
Run into anything? Email support@chilipiper.com. Happy building! 🌶️
The 'On a Website' embed now has an Advanced Options builder, a 4-step form that writes the JS options into your snippet for you.
How It Works
In a Concierge Flow, go to Embed, then 'On a Website', pick your form type, then Advanced Options. 4 steps cover booker, language, meeting type, form identifier, attendees, redirect, campaign, object IDs, and enrichment, each with a tooltip. The last step gives you the finished snippet and a Copy Code button.
What You Can Do Now
  • Event landing page
    : override the Meeting Type, the redirect URL, and the Salesforce campaign in the snippet, instead of editing every path on the router
  • Regional page
    : force French on a FR page without building a second router
  • SDR landing page
    : set the booker so meetings from that page are attributed to the SDR
Things to Note
The snippet article documents every JS option, including the ones the builder doesn't cover.
Learn more in our Concierge Snippet and JS API article.
Assign To and Update Ownership nodes reach Announcements, Offers and Scheduling Flows, Scheduling Flows gain 2 new node placements, double ownership routing works in Chat and Scheduling Flows, and the Announcement bar can be restyled from your own CSS.
1. Assign To and Update Ownership Nodes
Now available in Announcements, Offers, and Scheduling Flows. Assign a Record to a Distribution and update its Owner, wherever the visitor ends up in the flow.
Things to Note
Announcements don't collect email, so use a Routing Rule to check whether you already know the visitor, for example
Person.Email is not null
. That value can come from a previous visit, URL smart parameters, or the JS lead object.
2. Send a Message Node Anywhere in a Scheduling Flow
Tell the visitor what's happening, that you need a few more details, or thank you once they've booked. The button reads 'Continue' mid-flow, and 'Close' when the message ends the path. Any hyperlink in the message opens in a new tab.
3. Send Data Field After the Booking
In Scheduling Flows, you can now place a Send Data Field node after the calendar as well as before it. Ask the qualifying questions before the booking and the nice-to-haves after, for example, "What would you most like to learn about on our call?"
4. Double Ownership Routing in Chat and Scheduling Flows
Place two Ownership Routing Rule nodes one after the other, then under 'Show Availability', add one Owner row per rule, the same as Concierge. Add a 'Navigate To' node on the 'Not Matched' path of the first rule, or the flow will end there.
Every assignee now shows in the meeting confirmation, the Chat Logs, and the Inbox, not just the primary assignee.
5. Style the Announcement Bar From Your Own CSS
An Announcement doesn't have to be a full-width bar. You can restyle the widget frame from your site to make it a centered floating card, or a notch against the top edge. Narrowing it also brings the CTA in next to the text, rather than text hard left and button hard right across a wide screen. The same approach widens or narrows the Offer modal.
Limitations
Fonts, colors inside the widget, and CTA placement sit inside a cross-origin iframe, so they can't be styled this way. Scheduling Flows can't be resized this way either.
Group your Rules and Concierge Flows into named folders for a cleaner view.
How It Works
Click 'Create Folder' at the top right of the Rules or Concierge Flows list and name it, then drag rows in, one at a time or several at once. Folders start collapsed and load their own rows when you open them, so a long list opens fast.
Things to Note
  • Deleting a folder moves everything in it back to All Rules or All Flows.
    Nothing is deleted when you delete the folder
  • A Rule that has never been published can't be moved into a folder until it's published
Still to Come
Meeting Types and Handoff are next, followed by Distro, Distributions, and Teams.
Here's a preview of Rules:CleanShot 2026-09-22 at 09
And a preview of Concierge Flows: CleanShot 2026-09-22 at 09
Keep your territory map, your segment thresholds, and who owns what in a single table, then point your Distro routing at it instead of building a path for every combination.
What's Changed and Why
A lot of routing logic is really just a lookup. "This country plus this company size goes to that team." Previously, when expressed as Rules, 50 territories meant 50 paths to build, 50 paths to maintain, and a reorg meant editing them all.
Now, an Assignment Table holds that same logic as rows, and one Assignment Rule points at the whole table.
What You Can Do Now
When a rep's territory changes, you edit one row instead of hunting through routing paths to find every rule that mentions them.
  • Route by territory on country, state, or postal code, without a separate path per territory
  • Segment by company size, industry, or any picklist, with several values in one cell instead of one row per value
  • Assign each row to a named User or to a Distribution
  • Hand the table to whoever owns the territory map. Download it, edit it in a spreadsheet, upload it back. A reorg becomes a CSV edit
  • Check your work in the logs, which show the row that matched and the assignee it produced
A table routing US accounts by size looks like this:
Screenshot 2026-09-22 at 2
How It Works
  1. Build the table under Rules, then Assignment Tables. Attribute columns are what you match on: single text, number, true/false, or multiple text values. The assignment column is who gets the Record
  2. Create an Assignment Rule that points to the table and defines how incoming record fields compare to the attribute columns
  3. In a Distro flow, select that Assignment Rule in the Routing Rule node. The Assign & Update Ownership node automatically locks to it
Rows are evaluated top-down, and the first match wins, so put your most specific rows above your catch-alls.
Things to Note
  • Currently only live for Distro / CRM Routing flows
  • An empty cell means the field must be empty. Turn on "Treat empty cells as a match" if you want an empty cell to mean any value instead
  • A row missing its assignment value is skipped rather than failed, and the next row down assigns the record. An incomplete row quietly changes where things land, so it's worth a scan before you upload
  • A CSV upload replaces every row rather than merging. Download, edit, upload
  • Attribute columns don't support dates or ranges. For a range, use 2 number columns with greater-than and less-than
  • Assignment columns set assignment only - they can't populate field updates or add a record to a campaign
  • Fallbacks aren't available on paths that use an Assignment Rule.
Still to Come
  • Assignment Tables for Concierge and Web Experiences, for Meetings, Records, and Conversation assignments
  • Assignment Tables for Live Chat reading Conversation Assignment columns
Learn more in our Support Article.
Every field on your LinkedIn Lead Gen Form now reaches Chili Piper, not just email, first name, and last name.
What's Changed and Why
Previously, LinkedIn only passed 3 fields to Chili Piper: email, first name, and last name. Anything else the prospect answered on LinkedIn was either asked again on your form or lost. Now it all comes through..
How It Works
Each field arrives as a parameter named
linkedin_
followed by the field name in lowercase with spaces and punctuation removed, so Company Size arrives as
linkedin_companysize
. Add that as a Smart Parameter on the matching Data Field in Command Center, and Concierge can route on it. The full list of standard fields is in the support article.
Things to Note
  • Map every field you care about. If you miss one and that field is required on your Concierge form, the prospect gets asked for it again even though they already answered it on LinkedIn. If it's optional, the form skips it, and the answer is lost.
  • LinkedIn is enabling this gradually, so it may not be live on your account yet.
  • Consent and disclosure checkboxes aren't included.
Learn more in our Support Article.
The Meetings report now shows past and upcoming meetings together in a single date range, so you no longer have to toggle between two tabs and reconcile the lists yourself.
What You Can Do Now
  • Pick a range that spans today, like this month or a custom window, and get everything in it, including the meetings that already happened and those still to come
  • Filter and sort on Created date, the day someone first booked the meeting. It doesn't move when they reschedule, so you can answer "what did we book last week?" without opening meetings one by one
  • Filter by Workspace, Team, and Distribution. These cascade, so picking a Team narrows the Distribution filter to that team's distributions.
Still to Come
  • Team and Distribution columns aren't in the CSV export yet
  • Filtering by Team returns only ownership-assigned meetings; round-robin meetings don't appear. Use the Distribution filter
  • Picking a Team or Distribution excludes Personal Meetings; picking a Workspace includes them
When several members are tied on credits and any of them could be next, Chili Piper can now pick one at random instead of always taking the first in the group.
What's Changed and Why
Previously, when members ended up with the same credits and each was eligible to be picked next, the first of that group was always chosen. Over time, that skewed volume toward whoever sat at the top. The new Tie-Break Order setting lets you randomize instead.
Where to Find It
Two places:
  1. The Workspace default sits at Distributions, then Credits & Adjustments, then Tie-Break Order
  2. Each individual Distribution has its own Tie-Break Order with three options: Inherit Workspace Default, As Configured, or Random, so a single Distribution can go either way regardless of the Workspace setting
Learn more in our support articles on Credits & Adjustments and Setting up your Distributions.
Reps can book a meeting or hand the prospect off to the right rep while they're still on the phone - all through the Nooks Dialer.
Before You Start
Nooks identifies prospects by name, and a booking needs a guest email, so the icon only appears once the prospect's email is showing on the prospect view. Go to Customize View, add Prospect Fields, click Configure, turn on Email, then Done Editing.
Where to Find It
The icon sits at the right end of the prospect header. It's in the expanded row in your call list and in the dialog during a live call.
How It Works
Click the icon and the Scheduler opens with that prospect already in as the main guest, the same Scheduler you use in Gong, Gmail, and Salesforce. From there you can:
  • Book on your own calendar, picking any meeting type you have access to
  • Select a Handoff router to send the prospect to the right rep or team by your routing rules, instead of hunting for the right owner yourself
01-nooks-dialer-booking
Learn more in our Support Article.
Three updates to Chat Journeys and Scheduling Flows are live: bookings can be made with multiple assignees (i.e., double round-robin), the flow can skip questions it already has answers to, and Marketo and Salesforce nodes can sit on the same path.
1. Multi-Assignment and Double Round Robin
The Display Calendar node now takes a list of assignees instead of one, so double round robin and other multi-assignment patterns work the way they already do in Concierge, Handoff, and ChiliCal.
How It Works
Under 'Show Availability of', click 'Add' and pick Owner, Team, Team Member via Round Robin, or Individual. Repeat per assignee, and drag to reorder; the order determines who becomes Assignee 1, 2, or 3. Required groups narrow the times shown; optional ones just join the invite.
What You Can Do Now
  • Put an AE and an SE on one booking, with both calendars cross-checked, so there's no follow-up email to find a time
  • Route to the Account Owner and round-robin a specialist alongside them
  • Add a manager or note-taker as Optional, so they join the invite without narrowing availability
Learn more in our Support Article.
2. Use What We Already Know About a Visitor
A 'Send Data Field' node can now skip a field when we already hold a value, and dynamic tags resolve from any source.
How It Works
Every Data Field row in the node has a new Visibility setting:
  • Default
    - skips when the value came from Enrichment, a Smart Parameter, or the JS Lead Object
  • Skip if known
    - skips when we hold it from any source, including a previous visit or another Flow
  • Always ask
    - shows the field every time
Existing fields start on Default, so nothing changes in a live Flow until you pick something else. If every field in the node is skipped, the node is skipped entirely and the visitor goes straight to the next one.
What You Can Do Now
  • Recognize a returning visitor and skip straight past questions they already answered
  • Greet someone by first name or company name using a value from enrichment, or in-app from the lead object, since dynamic tags in guest-facing messages now resolve from any source, not just Smart Parameters
  • Pass values collected by other tools in the browser into the JS snippet and use them the same way
Still to Come
Chat Logs will show what was collected, how it was collected, and whether it was mapped to a Smart Parameter, similar to the recent Concierge update.
Learn more in our Support Article.
3. Marketo and Salesforce Nodes on the Same Path
What's Changed and Why
We previously blocked the two from co-existing because there was no mechanism to handle the delay between Marketo creating a lead and us matching it in Salesforce. Two new node options handle that now.
  • SFDC Update or Create Record node has a new Retry matching to lead or contact option. Instead of creating a record, Chili Piper waits and matches the newly created Lead via the Marketo-to-Salesforce sync, as Concierge does today. Add the SFDC node after Marketo, and the option comes pre-selected
  • Routing Rule node has a new 'Wait for CRM updates' before this rule runs toggle. It holds the journey until an earlier CRM update finishes saving, so the rule evaluates against the latest record
Learn more in the 'Using Marketo and Salesforce on the same path' section of our Support Article.
Happy building! 🌶️
Load More
→