Overview
The Call Rescheduled webhook is triggered whenever a previously booked call is rescheduled to a new time in your iClosed.io account. This event provides complete details about the rescheduled call, including the new timing, original timing, and rescheduling information.Event Details
- Event Type:
callRescheduled - Trigger: When a call is rescheduled to a different time
- Payload: Complete call information with new and original timing details
Webhook Payload
The webhook payload contains detailed information about the rescheduled call:Key Differences from Call Booked
Rescheduling Indicators
old_start_time: The original start time before reschedulingis_reschedule: Set totruefor the invitee objectreschedule_reason: Optional reason for the reschedulecanceled: Remainsfalse(not cancelled, just rescheduled)
Hook Type
hookType: Set to “Call rescheduled” to distinguish from booking events
Key Fields Explained
Event Type Information
event_type: Configuration details of the event typeuuid: Unique identifier for the event typekind: Booking strategy (e.g., “Round Robin”, “Direct Assignment”)slug: URL-friendly event namename: Display name of the eventduration: Call duration (typically unchanged)owner.type: Type of owner (closer, setter, etc.)
Event Details
event: Information about the rescheduled calluuid: Unique call identifier (same as original booking)old_start_time: Original start time before reschedulingstart_time/end_time: New scheduled timesstart_time_pretty/end_time_pretty: Human-readable new timesutc_start_time/utc_end_time: UTC timestamps for new timescanceled: Remainsfalse(not cancelled)assigned_to: Team member assignment (may change)type: Call type (STRATEGY_CALL, DISCOVERY_CALL, etc.)
Invitee Information
invitee: Details about the person who rescheduledis_reschedule: Set totrueindicating this is a reschedulereschedule_reason: Reason for rescheduling (if provided)canceled: Remainsfalse(not cancelled)previewUrl: Link to view the contact in iClosed.ioname: Full name of the inviteeemail: Invitee’s email addresstext_reminder_number: Phone number for SMS reminderstimezone: Invitee’s timezone
Questions and Responses
questions_and_answers: Original booking form responsesquestions_and_responses: Object format of responses
Tracking Information
tracking: Original UTM parameters and attribution data- Preserved from the original booking
Rescheduling Reasons
Common rescheduling reasons include:- Schedule Conflict: Original time no longer works
- Better Availability: Found a more convenient time
- Time Zone Confusion: Clarified timezone differences
- Preparation Needed: Need more time to prepare
- Technical Issues: Platform or connectivity problems
- Personal Emergency: Temporary personal situation
- Business Priority: Higher priority meeting came up
- Travel Delay: Delayed arrival or departure
Use Cases
This webhook is useful for:- Calendar Updates: Update calendar events with new times
- CRM Synchronization: Update opportunity records with new timing
- Team Notifications: Alert team members about schedule changes
- Analytics Tracking: Monitor rescheduling patterns and frequency
- Customer Communication: Send confirmation of new timing
- Resource Management: Update team member availability
- Reporting: Track rescheduling metrics and team performance
- Workflow Automation: Trigger follow-up actions for rescheduled calls
Response Requirements
Your webhook endpoint should:- Return a 2xx status code to acknowledge receipt
- Respond within 5 seconds to avoid retries
- Handle duplicate events (idempotency)
- Log the call UUID and rescheduling details for debugging
- Compare
old_start_timewith newstart_timeto confirm changes
Best Practices
- Time Comparison: Use
old_start_timeto identify what changed - Reason Tracking: Monitor
reschedule_reasonfor patterns - Calendar Management: Update all calendar entries immediately
- Team Communication: Notify assigned team members promptly
- Customer Confirmation: Send confirmation of new timing
- Availability Updates: Update team member availability slots
- Follow-up Timing: Adjust any automated follow-up sequences
- Data Consistency: Ensure all systems reflect the new timing
Rescheduling Workflows
When Invitee Reschedules
- Send confirmation of new timing
- Update calendar entries
- Notify assigned team member
- Adjust any automated reminders
- Update CRM with new timing
- Trigger rescheduling analytics
When Host Reschedules
- Send apology and explanation
- Offer alternative times if needed
- Update internal calendars
- Notify relevant team members
- Track rescheduling reasons
- Update availability management
Time Zone Considerations
timezone: Always use invitee’s timezone for local timesutc_start_time: Use UTC times for system integrationsstart_time_pretty: Use pretty format for customer communications- Timezone Changes: Handle cases where timezone itself changes
Rescheduling vs Cancellation
Key Differences
- Rescheduling: Call is moved to a new time,
canceled: false - Cancellation: Call is completely cancelled,
canceled: true - Rescheduling: Preserves all original booking data
- Cancellation: May require new booking process
Handling Both Events
- Monitor both
callRescheduledandcallCancelledwebhooks - Use
canceledflag to determine event type - Implement different workflows for each scenario
- Track both metrics for business intelligence