Chili Piper's webhook for new meetings fires for all Concierge meeting data with no way to scope it to specific routers. Teams that only need data from certain Concierges are forced to add a filtering layer in their own automation platform, such as Power Automate or Zapier, to exclude irrelevant events before they can act on them. This adds unnecessary processing overhead on the customer side and increases data transfer volume on both ends.

Chili Piper should allow admins to configure webhook subscriptions to include or exclude specific Concierges or routers, so only the relevant meeting events are sent to the endpoint.

Webhook consumers shouldn't need to build their own filtering logic to compensate for missing configuration options in the source system. Scoped webhooks reduce noise, lower processing overhead for both parties, and make integrations simpler to build and maintain, particularly for teams running complex automation workflows against high-volume meeting data.