For customers using Gong Engage with Salesforce, we need a solution that allows Chili Piper (CP) custom fields to be sent to Salesforce even when Gong Engage creates the event, without generating duplicates. This would let CP enrich Salesforce events while Gong handles event creation.

Currently, customers must choose between letting Gong Engage create the event—losing CP data—or having CP create it, which can be uncomfortable. Gong creates events for all external calls, while CP only creates events for meetings booked through it. Often, some teams use CP and others do not, but all teams use Gong. Disabling Gong’s event creation would cause lost events, including those manually added by reps.

It’s unreasonable to expect all teams to adopt CP/Engage, so we should work with this scenario rather than against it.