Changelog
Follow up on the latest improvements andΒ updates.
RSS
Admins can now see meeting activity across the entire org, including personal meetings, in a single report in the Command Center.
Why it matters
Meetings scheduled through Personal Links were previously invisible to admins, and Workspace meetings were housed within each individual Workspace Center. That meant organization-wide numbers were incomplete. The new Meetings Report tab in the Command Center brings everything together in one place, so the volume and activity you see reflect what's actually happening across your organization.
What's changed
- See every meeting - from all Workspaces alongside personal meetings - in one table. A WorkspaceName column shows the workspace for workspace-scoped meetings, and a Personal badge marks personal ones
- Filter by meeting type. The filter splits into Personal Meeting Types and Admin meeting types (grouped by workspace), so you can mix and match across both
- Filter by assignee through workspace β team β user
Find it in Command Center > Reports.
Workspace Managers now have a Users table under Assets > Users that shows only users in that Workspace.
What's changed and why
Until now, the only Users table was the organization-wide one in the Command Center. Workspace Managers could open it and edit organization-wide roles and licenses - including demoting Admins.
We've made 2 changes to address this:
- Workspace Managers get a dedicated Users table under Assets > Users
- The Command Center Users table is now Admin-only β Workspace Managers no longer have access to it
What's in the Workspace table?
- Role, Licenses, and Workspaces columns are read-only (even for a full Admin viewing it this way)
- Teams are editable by an Admin or a Workspace Manager
- Bulk actions, the "Open" user-details view, and "Remove user" are hidden
The Chili Piper MCP and Edge API keep getting stronger. Here's the latest round of improvements:
- Distro Logs- the Distro log table is now available via the API. For every record you get the router, the outcome (routed / no-match / error), who it was assigned to, and how they were picked, filterable by status and distribution method.
- Per-rep outcome stats in the distribution list. The final piece for a full API equivalent of the in-app Distribution table. Each user in a distribution now returns outcome counts, assigned, cancelled, no-show, and reassigned in / out.
- See who's calling your API and MCP. The Request Logs view (Integrations β API & Credentials β Logs) now includes a Caller column, the user for MCP calls or the token name for Edge API calls, alongside method, path, status, duration, and auth method. A clean audit trail of your own API and MCP usage.
- Render and validate forms before submit. scheduling-link-init now returns metadata for every guest-form field, its reference, whether it's required / optional / hidden, and its data type. Anything built on the API can render and validate the form up front instead of failing at submit time on a missing field.
- MCP OAuth now works with managed gateways. OAuth sign-in for our MCP now supports managed MCP gateways (such as Runlayer) that broker sign-in on behalf of an entire company. If you route MCP access through a central gateway, that's now supported.
Connect your LinkedIn Lead Gen Forms to Chili Piper so prospects can book a meeting the moment they submit your form.
LinkedIn passes the prospect's email, first name, and last name into Chili Piper, so they go straight to picking a time instead of filling in their details again.
Why it matters
- Speed to lead - immediate opportunity to book a meeting instead of following up manually later
- You're paying good money for those clicks. Offering the chance to book a meeting now makes your ad budget work harder
- Another entry point into your funnel
How it works
- A prospect opens your Lead Gen Form from a LinkedIn ad. LinkedIn pre-fills the form from their profile
- After they submit, the confirmation invites them to book an appointment
- Clicking Book now opens your Chili Piper booking experience with the prospect's email, first name, and last name already passed through
- Concierge qualifies and routes the prospect to the right rep, and they pick a time. With a ChiliCal Scheduling Link, the prospect books directly with the rep or team the link belongs to.
Chili Piper is the only company with a direct integration to LinkedIn Lead Gen Forms.
Check out the support article here for more.
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.
Load More
β