When Chili Piper creates a meeting, it writes a standard Salesforce Event. Customers who have built their scheduling workflows around a custom activity or task type end up with a duplicate record alongside their existing custom object, or have to abandon their existing type entirely.

Chili Piper should support writing the meeting record to an existing custom activity type in Salesforce, with the ability to map fields from the booking to the fields on that custom object.

For some customers, the custom event type is load-bearing infrastructure: it drives SDR compensation calculations, triggers exception reporting for undispositioned meetings, and captures metadata that doesn't exist on a standard Event. Replacing it is not a near-term option. Supporting it as a write target would let these customers adopt Chili Piper's scheduling automation without a disruptive CRM migration.