Changed: Improved Call Sync Accuracy to External Systems
Call activity records now sync only after a call is fully completed, ensuring external systems always receive finalized data, including summaries, transcripts, and metadata.
What's Included
- Call delivery status validation added before syncing activity to the database
- Sync now triggers only on completed call states: call_completed and call_completed.agent_hangup
- Active or in-progress calls are excluded from the sync queue until completion
- Applies to all connected external integrations, including Avionté and Aqore
How It Works
Previously, Whippy pushed call activity records to external systems as soon as a call was logged, even while still in progress. Since call summaries, transcripts, and metadata are only generated after a call ends, external systems received incomplete records containing little more than a link back to the Whippy conversation.
Now, Whippy validates the call delivery status before saving or syncing any activity. A record only enters the sync database once the call reaches a completed state. At that point, the full record, including the call summary, transcript, and metadata, is available and synced in a single, complete entry.
Why It Matters
Incomplete call records create noise in external systems: missing context, placeholder links instead of summaries, and data inconsistencies that require manual cleanup.
This update ensures that every synced record is ready to use, with the full context your team and your integrations need to act on it. Whether you're tracking outreach activity in a staffing platform or logging calls in a CRM, the data that arrives is complete and accurate from the first sync.
Notes
- No configuration changes are required. The updated sync behavior is applied automatically.
- Calls that ended before this update was released are not retroactively resynced.
- If your integration previously relied on receiving in-progress call records, those will no longer appear until the call reaches a completed state.