Website & Buyer Experience

The chat widget is the primary way Chili Piper surfaces buyer-facing interactions, but there's no support for proactive pop-ups, ribbon banners, or offer overlays. Teams that want to serve contextual CTAs or announcements to site visitors without requiring them to open the chat have no native way to do it. Requested behavior: Support configurable pop-up and ribbon-style offer placements on the website that can be triggered by visitor behavior, page context, or intent signals, independently of the chat widget. Why it matters: Not every visitor interaction starts with a chat. Pop-ups and banners allow teams to proactively surface relevant offers or CTAs at key moments in the browsing experience, expanding conversion opportunities beyond the chat entry point.

When the AI responds to a visitor in chat, there's no way to see which knowledge base article or content source the response was drawn from. Admins who want to verify accuracy, identify gaps, or troubleshoot incorrect answers have no visibility into what the AI actually used to generate a response. Requested behavior: Display the source article or content reference for each AI-generated response, either in the admin view or inline in the conversation, so admins can audit responses and trace them back to the underlying knowledge base content. Why it matters: AI accuracy depends on knowledge base quality. Without knowing which source drove a response, it's impossible to systematically improve the AI's answers or catch cases where it's pulling from outdated or incorrect content.