The Issue -

Currently, the "Update Field" action in Concierge routers — which fires after a meeting is booked — only supports static values. There is no way to pass dynamic data (e.g., Salesforce field values or Chili Piper field values) into the field being updated.

The Problem It Solves -

Without dynamic value support, customers who want to write context-aware data to Salesforce fields after booking must build complex branching logic in either Chili Piper routing rules or Salesforce flows to account for every possible variation. This is difficult to maintain and doesn't scale. A specific pain point: customers want to auto-populate fields like a "Demo Title" with account-specific information (e.g., "Reveal x [Account Name]") that can only be known at the time of booking.

The Proposed Solution -

Allow the Update Field post-booking action to accept dynamic values — similar to how dynamic values can already be imported for meeting type information. At minimum, this should support pulling from matched Salesforce fields (e.g., Account Name resolved via the prospect's email domain) and Chili Piper fields. This would eliminate the need for complex branching rules and give customers a scalable, low-maintenance way to build post-booking automations.