1. The Problem / Current Limitation Currently, exporting conversation data out of Intercom is fragmented. The native CSV exports lack the granular depth required for advanced analytics, compliance, and auditing. Specifically, we cannot easily export the full, chronological event logs (e.g., routing history, SLA breaches, tag additions, snoozes, internal notes) alongside the conversation transcript and metadata across every channel (chat, email, social, SMS).
2. The Use Cases Having access to a complete, uncompromised export of conversations and their associated event logs is critical for several business functions:
-
Advanced BI & Analytics: Data teams need to ingest complete conversation histories and metadata into data warehouses (like Snowflake, BigQuery, or Redshift) to build complex attribution models, analyze support routing efficiency, and join Intercom data with internal CRM data.
-
Compliance & Auditing: Highly regulated industries (finance, healthcare, legal) require complete, timestamp-verifiable records of customer interactions, including exactly when automated bots or human agents took specific actions.
-
Quality Assurance (QA): Support managers need the full timeline of a ticket—not just the chat bubbles, but the invisible metadata (when a ticket was reassigned, when it was snoozed, and what backend events fired) to accurately grade agent performance and system routing.
3. Current Workarounds & Their Shortcomings
-
Intercom API: Building custom scripts to hit the REST API and piece together conversations, metadata, and events. This requires dedicated developer resources, is subject to rate limits, and requires constant maintenance to handle pagination and API updates.
-
Third-Party Tools: Relying on paid marketplace apps to extract data. This introduces additional vendor costs and potential security/privacy risks by passing sensitive customer PII through a middleman.
-
Native UI Exports: Using the out-of-the-box CSV exports, which drop critical event logs, truncate complex metadata, and do not provide a unified view across all modern conversation channels.
4. Proposed Solution We request a native, unified export feature (available via the UI as an on-demand download and as a scheduled delivery to external storage like AWS S3/Google Cloud Storage) that includes:
-
Comprehensive Metadata: User attributes, custom data attributes, device info, and complete participant IDs.
-
Full Event Logs: A chronological, timestamped record of every action taken within the conversation (assignment changes, state changes, tags added/removed, bot interactions, internal notes).
-
Omnichannel Consistency: A standardized export format (preferably JSON or multi-table CSVs) that normalizes data across Web Chat, Email, WhatsApp, SMS, and all other supported channels.
5. Business Impact Releasing this feature would significantly reduce the engineering burden on Intercom customers, empower data and ops teams to uncover deeper insights about the customer journey, and make Intercom a much more viable solution for enterprise businesses with strict compliance and auditing requirements