Sending notifications or triggering external actions based on Chat events requires manually adding a notification node for each scenario in every journey. Admins who need to fire a webhook when a visitor starts a chat, when a rep replies, or when no one responds have to configure separate nodes for each outcome, creating journeys that are bloated and hard to maintain. Chili Piper should support global webhook triggers that fire automatically on defined Chat events, such as conversation started, rep replied, or conversation abandoned, without requiring a node to be manually added and configured for each scenario in every journey. This is especially painful for teams using Microsoft Teams for notifications, where there's no direct integration and every notification requires a manually configured webhook node, unlike Slack which has a native integration. A global event-based webhook system would eliminate the need to rebuild and maintain this configuration across every journey.
