Calendly Scheduling Platform

1 Summary

Calendly provides meeting scheduling with CSV export integration for client booking data collection and meeting analytics. Legacy scheduling platform with manual data export workflow for historical meeting analysis.

2 Support Channels

3 Key Integrations

  • Meeting Analytics: CSV event exports feed meeting aggregation pipeline
  • Contact Resolution: Attendee email matching via unified contact index
  • Historical Data: Legacy booking records for client relationship timeline analysis
  • LACRM Integration: Processed meeting data updates client interaction metrics

4 Technical Implementation

  • Authentication: Manual CSV export (no direct API integration)
  • Data Format: Event exports with attendee details, timestamps, event types
  • Processing Pipeline: CSV import → normalization → contact matching → meeting aggregation
  • Data Flow: Manual export → /data/calendly/ → processing scripts → DuckDB catalog
  • Automation: Referenced in process: meeting-aggregation, contact-management

5 Data Processing

  • Event Normalization: Standardized meeting format across all booking platforms
  • Contact Matching: Email-based attendee resolution to LACRM contact records
  • Meeting Classification: Event type analysis for portfolio review identification
  • Historical Integration: Legacy meeting data preserved for relationship continuity

6 Export Workflow

  1. Manual Export: Download event data from Calendly dashboard as CSV
  2. File Placement: Store exports in data/calendly/ directory with timestamp
  3. Processing: Automated detection and normalization via process_calendly_events.py
  4. Integration: Processed data feeds meeting aggregation and contact metrics

7 Risk Notes

  • Manual Process: CSV export dependency creates potential data gaps if not performed regularly
  • Data Freshness: No real-time integration - meeting data delayed until manual export
  • Contact Matching: Email variations can create orphaned meeting records requiring manual review
  • Historical Data: Legacy platform transition requires careful data migration to maintain client history

8 Operational Dependencies

  • Contact Index: Essential for mapping Calendly attendees to LACRM contact records
  • Meeting Aggregation: CSV data feeds comprehensive meeting analytics across all platforms
  • Client Timeline: Historical booking data maintains complete client relationship history
  • Manual Oversight: Regular export schedule required to maintain data currency

9 Migration Considerations

  • Platform Transition: Legacy system with migration to Cal.com for new bookings
  • Data Continuity: Historical meeting records preserved for client relationship analysis
  • Dual Processing: Temporary overlap period requiring processing from both platforms
  • Contact Attribution: Consistent email-based matching across legacy and current systems
Owner: Ops: Client Experience
Last reviewed: 2025-09-24
SLA: N/A
Controls: ?invalid meta type:ops_controls
Commit: 8f0c18729ae96125ef5caf6824600a75c4928c16