Feature Requests

Concierge always requires a form submission to trigger the scheduling flow. When a visitor's data is already known, from a CRM match, logged-in state, or external enrichment, making them fill out a form they've already completed or that duplicates known data creates unnecessary friction. Admins should be able to pass known visitor data directly to Concierge via parameters or API, triggering the routing and scheduling flow without requiring a form submission. For customers with identified visitors or enriched intent data, bypassing the form is a meaningful conversion improvement at a moment of peak intent.

The customer requests a feature for automatic translation of meeting descriptions in Chilipiper, allowing the descriptions to adapt to the recipient's language, similar to the existing functionality for time and date prompts.

Meeting Types are configured in a single language. Teams serving multilingual audiences either have to create duplicate Meeting Types for each language or accept that some prospects see content in the wrong language. Meeting Types should support multiple language configurations so that details are automatically presented to the prospect in their preferred language, without requiring separate Meeting Types per language. Creating duplicate Meeting Types for each language is operationally expensive and hard to maintain. Native multi-language support eliminates that duplication and ensures every prospect sees a localized experience.

AI-generated meeting briefs aren't delivered to internal reps in an editable format. Requested behavior: Allow internal users to receive the AI-generated brief for an upcoming meeting via email or in-app notification, and edit or annotate it before the meeting starts. Why it matters: Reps going into meetings without context miss personalization opportunities. Editable briefs let reps correct AI errors and add their own notes, improving meeting quality.

The chat AI displays to all visitors regardless of where they're located. Teams that only serve specific geographies, or that want to show different chat experiences to visitors from different countries or regions, can't use location as a trigger or suppression condition. Requested behavior: Allow admins to configure the chat AI to activate, suppress, or branch differently based on the visitor's detected geographic location, such as country or region, so location becomes a first-class targeting dimension. Why it matters: Many companies serve different markets with different products, languages, or routing teams. A chat that ignores geography risks presenting irrelevant experiences to visitors who can't be served by the available reps or offerings.

Chat visitors who haven't provided an email can't be identified, limiting the ability to personalize the chat experience or route them based on account data. Chili Piper should integrate with reverse IP solutions to identify the account a visitor likely belongs to before they provide an email, enabling account-aware routing and personalization from the start of the session. Anonymous visitors represent a significant portion of website traffic. Identifying them earlier in the session allows for more relevant chat experiences and improves the chance of converting high-value accounts.