When Gong creates calendar events in Salesforce, it pulls data from the calendar itself (title, host, time) but doesn't include Chili Piper metadata like meeting type name or the person who booked the meeting. Teams using Gong as their event source lose visibility into which meeting types are being used and can't report on meeting type adoption or distribution across their team.

When a meeting is booked through Chili Piper and Gong writes the corresponding calendar event to Salesforce, Chili Piper should pass meeting type name and booker information to Gong so those fields are written to the Salesforce event record alongside the standard calendar data.

Meeting type is often the primary dimension for measuring scheduling adoption, routing effectiveness, and rep workload distribution. Without it in the Salesforce event record, teams relying on Gong as their event source have no way to report on meeting type usage without maintaining a parallel reporting system outside of their primary BI pipeline.