Feature Requests

There's no structured way to snapshot or export Chili Piper data on a schedule for ingestion into a data warehouse or lake. Today CP data only reaches the warehouse indirectly through Salesforce events, which is incomplete and not a clean source of truth, so data teams can't treat Chili Piper as a primary GTM data system the way they do Salesforce or Gong (which has a data cloud). Provide a way to export/snapshot all Chili Piper data on a configurable (e.g. daily) cadence into a warehouse, meetings, activity, and historical logs (e.g. a meeting that was rescheduled N times) with stable IDs, via a managed connector / data cloud / scheduled bulk export, rather than a live pipeline or manual support pulls. Enterprise data teams build forecasting, segmentation, and show-rate analysis on warehoused data, and increasingly feed it to AI/agents. Routing CP data only through Salesforce events loses fidelity and historical signal. A Gong-style data cloud / daily snapshot makes Chili Piper a first-class GTM data source instead of a black box.

Chili Piper can capture UTM parameters from the current page URL, but it can't read UTM values stored in a visitor's cookie. When a lead was originally cookied with UTM data on an earlier visit and that data isn't present in the URL at submission time, the original attribution is lost. Chili Piper should support reading UTM parameters from cookies (e.g. the first-touch UTM the visitor was cookied with) and writing them to the mapped lead and contact fields, alongside the existing URL-parameter capture. Cookie-based capture is more accurate than URL parameters because it preserves the original campaign source even when the lead converts on a later, untagged pageview. Without it, teams relying on UTM for attribution under-credit the campaigns that actually drove the lead.

There should be a way to export all Concierge logs with just one export. Currently, you'll have to go through the Concierge logs one by one to export.

There's no way to export the list of assignees in a distribution along with their weighting configurations. Managers who need to share or audit weights, especially distributions with 20+ assignees where the UI becomes difficult to read, have to do it manually. Allow admins to export the active assignee list for any distribution queue as a CSV that includes each rep's name, their assigned weight, and their current active/inactive status. Distribution weighting directly affects lead distribution fairness. Without an exportable view, auditing weights for large queues is slow and error-prone, and sharing queue configuration with stakeholders requires screenshots or manual data entry.

Add export logs functionality to run the analysis per the routed lead.

When a form is submitted through Chili Piper, the submitter's IP address is not captured or surfaced anywhere in the product. Admins and the support team who need to identify the IP address behind a specific submission, for example to investigate spam, duplicate submissions, or abuse, currently have to open a support ticket and wait for the information to be retrieved manually. There is no self-serve way to access it. Chili Piper should log the IP address associated with each form submission and make it accessible to admins in the submission record or reporting view. IP address is a standard data point captured by virtually every web form tool and is frequently needed for abuse investigation, spam filtering, and compliance purposes. Requiring a support ticket to access it every time adds unnecessary overhead for both admins and the support team. Surfacing it directly in the product would make routine investigations self-serve and reduce support volume for a request that should never need human intervention to answer.

There is no way to export a summary of routing rules from Chili Piper. Admins who need to audit their rule library, track which rules are active or inactive, identify stale configurations, or share a snapshot of their routing setup with stakeholders have no way to get this information out of the product in a structured format. Admins should be able to export a CSV report of their routing rules that includes at minimum the rule name, active/inactive status, last published date, and last modified date. Routing rule libraries grow quickly and become difficult to manage without an external view. A simple metadata export gives ops teams the ability to audit their configuration, identify rules that haven't been updated in a long time, and maintain documentation of their routing setup without manual data entry. This is a basic governance capability that's standard in any tool managing complex configuration at scale.

Lead export data doesn't include the name of the router that processed each lead. Teams that want to analyze routing performance by router in Excel have no way to get this data out. Lead exports should include the router name associated with each record so teams can filter and analyze routing performance by router in Excel without needing to cross-reference manually. Router-level attribution is essential for diagnosing routing performance issues. Without it in the export, teams can't do the basic analysis needed to maintain and improve their routing setup.

Teams that centralize their data in Snowflake or a similar data warehouse have no native way to get Chili Piper data there. Routing activity, meeting outcomes, and form submission data can't be piped into their data environment without building custom API integrations. Requested behavior: Provide a native Snowflake integration or support for data pipeline creation that allows Chili Piper data to flow into a customer's data warehouse on a configurable schedule. Why it matters: Data warehouse-first teams can't include Chili Piper data in their broader analytics and reporting without building and maintaining custom pipelines. A native integration removes that burden and makes Chili Piper data a first-class citizen in the customer's data stack.

There's no way to export the form data collected through Chili Piper. Admins who need to analyze submission data, audit responses, or move data into another system have to extract it manually or rely on CRM sync alone. Requested behavior: Allow admins to export all form submission data collected through Chili Piper as a CSV file, with filtering options by date range, form, or Router. Why it matters: Direct data access is a baseline expectation for ops and analytics teams. Without export capability, any analysis of form performance or submission quality requires working around the product rather than through it.