Analytics conversations export

Edited

Overview

The Conversations export is one of the export types when you export an analytics report. This file gives you a clean conversation-level view of your data.

  • The exported file contains one row per conversation segment with activity during the selected time period, up to 100,000 rows. 

  • The export currently supports up to 31 days of data per export. If your selected date range is longer, please narrow the date filter before exporting.

  • All timestamps in the file are formatted as YYYY-MM-DD HH:mm:ss, in the requested user's time zone. Information provided reflects the conversation segment data at the time the export was generated.

  • Additional columns will be added to the export in future updates.


Exported fields

  1. Conversation ID*: Internal Front ID of the conversation.

  2. Segment ID: Represents a conversation segment, by concatenating the conversation ID and segment number. This is the basis for the calculation of all segment-level metrics.

  3. Segment: Segment of the conversation.

  4. Ticket IDs: Ticket IDs attached to the conversation.

  5. Subject: Subject of the conversation.

  6. Segment start date: The date and time of the first activity for any new segment.

  7. Status: Current status of the conversation: Archived or Open.

  8. Tags: Tags currently attached to the conversation.

  9. Assignee: Name of the teammate currently assigned to the conversation.

  10. Assignees during period: Names of all teammates assigned to the conversation during the selected time period.

  11. Teammates involved during period: Names of all teammates who touched (performed an action on) the conversation during the selected time period.

  12. Contact names during period: First and last names of contacts involved in the conversation.

  13. Contact handles during period: Email addresses, phone numbers, etc. of contacts involved in the conversation, depending on the source of the message.

  14. Accounts during period: Account(s) the contacts are linked to. Accounts are not retroactively applied to existing messages.

  15. Channels during period: Names of the channels used to send or receive messages in the conversation.

  16. Inboxes during period: Name of the inbox(es) the conversation was located in during the selected time period. 

  17. Messages sent: Count of messages sent in the conversation segment.

  18. Messages received: Count of messages received in the conversation segment.

  19. Replies to resolution: Number of outbound replies for resolved conversation segments. Data is only available for conversations in inboxes with ticketing enabled. Empty if the final resolution is not in the selected timeframe.

  20. Suggested replies sent: Count of messages sent using a suggested reply.

  21. First response time: Duration (in seconds) between the first inbound message and first outbound message in the same conversation. Corresponds to first reply time in analytics reports.

  22. Response time: Duration (in seconds) between an inbound message and the next outbound message in the same conversation. Corresponds to reply time in analytics reports. 

  23. Resolution time: Duration (in seconds) from the start of a conversation segment to the last resolution. Data is only available for conversations in inboxes with ticketing enabled. Empty if the final resolution is not in the selected timeframe.

  24. Reply time goal breaches: Count of reply time goal breaches in the segment.

  25. Time in open: Duration (in seconds) that the conversation spent in the default Open ticket status. Empty if the final resolution is not in the selected timeframe.

  26. Time in waiting: Duration (in seconds) that the conversation spent in the default Waiting ticket status. Empty if the final resolution is not in the selected timeframe.

  27. Time in resolved: Duration (in seconds) that the conversation spent in the default Resolved ticket status. Empty if the final resolution is not in the selected timeframe.


Pricing

This feature is available on the latest Professional plan or above. Some legacy plans may also allow access to this feature.