{"Status":true,"Message":"","Response":{"post":{"postuid":"e3ff8ff7-39b7-46d9-bcbe-8cba5febb475","tenantuid":"d8b744fc-2e70-4089-bb80-dd1d08f6c7b2","projectuid":"fc6490ac-7527-4f49-b06e-46f701280e85","title":"Exporting Chat Data","slug":"article/exporting-chat-data","html":"\u003Cp\u003EThe \u003Cb\u003EExport\u003C/b\u003E page downloads a messenger\u0027s conversations, and its tickets when ticketing is on, as CSV files you can open in Excel, Google Sheets or a BI tool. Open a messenger and click \u003Cb\u003EExport\u003C/b\u003E in its sidebar, just below \u003Cb\u003EReports\u003C/b\u003E.\u003C/p\u003E\u003Cp\u003EAnyone who can see \u003Ca href=\u0022/article/chat-reports\u0022\u003EReports\u003C/a\u003E can use Export: the Owner, Admin, User and Reports roles.\u003C/p\u003E\u003Ch2 id=\u0022download_a_file\u0022\u003EDownload a file\u003C/h2\u003E\u003Cp\u003EEach file has its own card with its own period. Choose \u003Cb\u003ELast 7 days\u003C/b\u003E, \u003Cb\u003ELast 30 days\u003C/b\u003E (the default), \u003Cb\u003ELast 90 days\u003C/b\u003E or \u003Cb\u003ELast 12 months\u003C/b\u003E, then click \u003Cb\u003EDownload CSV\u003C/b\u003E.\u003C/p\u003E\u003Cul\u003E\u003Cli\u003EThe conversations period runs back from now, for example the last 30 \u00D7 24 hours.\u003C/li\u003E\u003Cli\u003EThe tickets period counts whole days in your \u003Ca href=\u0022/article/chat-support-hours\u0022\u003Esupport hours\u003C/a\u003E time zone, or your own when support hours are off.\u003C/li\u003E\u003Cli\u003ETimes in both files are in UTC. Durations are in seconds (conversations) or hours (tickets).\u003C/li\u003E\u003C/ul\u003E\u003Ch2 id=\u0022conversations\u0022\u003EConversations\u003C/h2\u003E\u003Cp\u003EOne row for every conversation started in the period with a question or a reply. Conversations opened without either, such as a proactive message that was opened and closed, are left out. If you\u0027ve chosen to leave out your team\u0027s testing in Reports, it\u0027s left out here too.\u003C/p\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EColumns\u003C/th\u003E\u003Cth\u003EWhat they contain\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003Econversation_id\u003C/code\u003E, \u003Ccode\u003Estarted_utc\u003C/code\u003E, \u003Ccode\u003Estatus\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EWhich conversation, when it started and whether it\u0027s open, snoozed or closed\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003Ehandled_by\u003C/code\u003E, \u003Ccode\u003Eassignee\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EWho had it (the AI, waiting, or a person) and the teammate it was assigned to\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003Eoutcome\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EHow it ended: \u003Ccode\u003Eai_confirmed\u003C/code\u003E, \u003Ccode\u003Eai_assumed\u003C/code\u003E, \u003Ccode\u003Ehuman_handled\u003C/code\u003E, \u003Ccode\u003Eteam_started\u003C/code\u003E, \u003Ccode\u003Emissed\u003C/code\u003E, \u003Ccode\u003Ewaiting\u003C/code\u003E or \u003Ccode\u003Eother\u003C/code\u003E\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003Eai_answers\u003C/code\u003E, \u003Ccode\u003Eai_no_answers\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EHow many times the AI answered, and how many questions it couldn\u0027t answer\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003Ehanded_off_utc\u003C/code\u003E, \u003Ccode\u003Ehandoff_reason\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EWhen and why it was handed to your team\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003Efirst_human_reply_utc\u003C/code\u003E, \u003Ccode\u003Efirst_response_seconds\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EThe first reply from a person and how long after the handoff it came\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003Eclosed_utc\u003C/code\u003E, \u003Ccode\u003Etime_to_close_seconds\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EWhen it closed and how long it was open\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003Erating\u003C/code\u003E, \u003Ccode\u003Erating_comment\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EThe customer\u0027s rating (1 to 5) and comment\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003Estart_page\u003C/code\u003E, \u003Ccode\u003Eproactive_message\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EThe page it started on and the proactive message it replied to\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003Ecountry\u003C/code\u003E, \u003Ccode\u003Echannel\u003C/code\u003E, \u003Ccode\u003Edevice\u003C/code\u003E, \u003Ccode\u003Evisitor_type\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EWhere the customer was, how they reached you (website, email, WhatsApp), their device, and whether they were verified, identified or anonymous\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003Evisitor_messages\u003C/code\u003E, \u003Ccode\u003Eteam_replies\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EHow many messages the customer sent and how many replies your team sent\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003Efollow_up_rule\u003C/code\u003E, \u003Ccode\u003Efollow_up_details\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EThe question rule that collected follow-up details, and the details as \u0022Label: value; Label: value\u0022\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Ch2 id=\u0022tickets\u0022\u003ETickets\u003C/h2\u003E\u003Cp\u003EThe Tickets card appears when \u003Ca href=\u0022/article/setting-up-ticketing\u0022\u003Eticketing\u003C/a\u003E is on. It downloads one row for every ticket opened in the period, open ones first and the longest open first, with the columns \u003Ccode\u003Enumber\u003C/code\u003E, \u003Ccode\u003Esubject\u003C/code\u003E, \u003Ccode\u003Ecustomer\u003C/code\u003E, \u003Ccode\u003Eaccount\u003C/code\u003E, \u003Ccode\u003Estatus\u003C/code\u003E, \u003Ccode\u003Epriority\u003C/code\u003E, \u003Ccode\u003Etype\u003C/code\u003E, \u003Ccode\u003Eassignee\u003C/code\u003E, \u003Ccode\u003Eopened\u003C/code\u003E, \u003Ccode\u003Eclosed\u003C/code\u003E, \u003Ccode\u003Eopen_hours\u003C/code\u003E, \u003Ccode\u003Eoverdue\u003C/code\u003E and \u003Ccode\u003Erating\u003C/code\u003E.\u003C/p\u003E\u003Ccite class=\u0022recommended\u0022\u003E\u003Cspan class=\u0022title\u0022\u003EExporting one ticket view\u003C/span\u003E\u003Cp\u003ETo export just the tickets in a view, with its filters, use \u003Cb\u003EExport\u003C/b\u003E on the ticket table in the inbox. See \u003Ca href=\u0022/article/working-with-tickets\u0022\u003EWorking with Tickets\u003C/a\u003E.\u003C/p\u003E\u003C/cite\u003E\u003Ch2 id=\u0022opening_the_files\u0022\u003EOpening the files\u003C/h2\u003E\u003Cp\u003EThe files are UTF-8 CSV, which Excel opens directly. A value that starts with a character a spreadsheet would read as a formula (such as =, \u002B, - or @) begins with an apostrophe, so text a customer typed can\u0027t run as a formula. How long conversations are kept depends on your \u003Ca href=\u0022/article/chat-data-retention\u0022\u003Edata retention\u003C/a\u003E setting, so older periods only include what\u0027s still stored.\u003C/p\u003E","publish_status":0,"post_type":"Article","author":{},"featured_image_updating":false,"meta_description":"Learn how to export messenger conversations and tickets as CSV files for analysis in Excel or BI tools, with details on available data and filters.","display_toc":true,"has_workingcopy":false,"allow_indexing":true,"total_views":0,"date_published":"2026-11-15T17:38:37.787","date_updated":"2026-11-15T17:38:38.657","date_created":"2026-11-15T14:17:51.857"}}}