# Export Message Data

The **Export Message Data** feature allows you to download a CSV file containing message logs from QuickReply. This is useful for reporting, reconciliation, analytics, compliance, and internal audits.

You can access this option from the **Settings** tab in your QuickReply dashboard.

{% hint style="info" icon="star" %}
This feature is only visible to the Owner (agent role) of the account
{% endhint %}

{% embed url="<https://youtu.be/JOYyw9TYuR0>" %}

### Overview

Export Message Data enables you to:

* Generate a **Message Dump (CSV file)** for a selected date range
* Download and re-download the generated file for up to **90 days**
* Export detailed message-level information including delivery status, message types, templates, automation sources, and more across supported channels

### When to Use

You may use Export Message Data when you need to:

* Review message delivery and failure statuses
* Audit chatbot, journey, campaign, or broadcast performance
* Share conversation data with internal BI or analytics teams
* Maintain compliance or internal reporting records
* Reconcile channel-wise messaging activity, including template usage and applicable charges where relevant

### Accessing Export Data

1. Go to **Settings**
2. Click on **Export Data**
3. Select your filters (see below)
4. Click **Generate Export Now**

### Filters

#### 1. Date & Time (UTC) — *Mandatory*

You must select a date and time range to generate the export.

> All timestamps in the exported file are in **UTC**.

#### 2. Additional Filters — *Optional*

Two additional filters are available. These are optional and help narrow down the export scope.<br>

### Export Limits

* You can generate exports **up to 5 times per month**.
* If you attempt to compute more than 5 times, you will see:

> **“Your monthly limit is exhausted – Please contact support.”**

* Once a file is generated:
  * It remains available for **90 days**
  * You may download it multiple times during this period
  * The file name is system-defined (controlled by backend)

### Export States

When you click **Generate Export Now**, the system enters a **Generating** state:

* A loading popup appears
* File preparation happens in the background
* Once complete, a **Download** option becomes available

## CSV File Structure

The exported CSV contains the following fields:

| Column                 | Description                                             |
| ---------------------- | ------------------------------------------------------- |
| Date & Time (UTC)      | Timestamp of the message (UTC)                          |
| Message ID             | Unique identifier of the message                        |
| Conversation ID        | Unique identifier of the conversation                   |
| Phone                  | Customer’s WhatsApp number                              |
| Direction              | Inbound (user → business) or Outbound (business → user) |
| Message Type           | Type of message (see full breakdown below)              |
| Message Content        | Actual message text or payload                          |
| Delivery Status        | SENT, DELIVERED, READ, FAILED                           |
| Failure Reason         | Error details (if failed)                               |
| Template ID            | WhatsApp template ID (if applicable)                    |
| Template Category      | Template category (e.g., Marketing)                     |
| Amount Charged         | WhatsApp conversation charge (if applicable)            |
| Automation Source Type | Source of automation (journey, broadcast, etc.)         |
| Automation Source ID   | Internal ID of the automation                           |

## Field Values Explained

Below is a structured explanation of supported values.

{% tabs %}
{% tab title="Message Types" %}
The `Message Type` column represents how the message was generated or what interaction occurred.

Below is a structured explanation of supported values.

### 1. User Messages (Inbound)

These are messages sent by the customer.

| Type                | Description                    |
| ------------------- | ------------------------------ |
| USER\_TEXT          | Plain text message             |
| USER\_ATTACHMENT    | Media attachment               |
| USER\_FILE          | File upload                    |
| USER\_LOCATION      | Location shared                |
| USER\_BUTTON\_REPLY | WhatsApp button reply          |
| USER\_LIST\_REPLY   | WhatsApp list reply            |
| USER\_FLOW\_REPLY   | WhatsApp Flow response         |
| USER\_ACTION        | User-triggered action          |
| USER\_PAYMENT       | Payment event                  |
| FB\_CAPTURE\_EMAIL  | Captured email                 |
| FB\_CAPTURE\_PHONE  | Captured phone number          |
| USER\_SYSTEM\_TEXT  | System message visible to user |

***

### 2. Agent Messages (Outbound – Human or Bot)

These are messages sent from QuickReply.

#### Standard Responses

| Type                | Description        |
| ------------------- | ------------------ |
| AGENT\_TEXT         | Text message       |
| AGENT\_ATTACHMENT   | Media/file sent    |
| AGENT\_LOCATION     | Location shared    |
| AGENT\_QUICK\_REPLY | Quick reply        |
| AGENT\_RATING       | Rating request     |
| AGENT\_WEBVIEW      | Webview opened     |
| AGENT\_YOUTUBE      | YouTube embed      |
| AGENT\_SLIDER       | Slider interaction |

#### Forms & Structured Inputs

| Type                     | Description             |
| ------------------------ | ----------------------- |
| AGENT\_FORM              | Form message            |
| AGENT\_FORM\_DATEPICKER  | Date picker form        |
| AGENT\_QUESTION\_FORM    | Question-based form     |
| AGENT\_MULTI\_SELECTION  | Multi-selection message |
| AGENT\_TRIGGER\_QUESTION | Trigger question        |

#### Product & Commerce

| Type                     | Description           |
| ------------------------ | --------------------- |
| MULTI\_PRODUCT\_CATALOG  | Multi-product catalog |
| SINGLE\_PRODUCT\_CATALOG | Single product        |
| CATALOG\_ORDER           | Order from catalog    |

#### WhatsApp-Specific Types

| Type         | Description               |
| ------------ | ------------------------- |
| WA\_TEMPLATE | WhatsApp template message |
| WA\_CTA      | Call-to-action template   |
| WA\_LIST     | WhatsApp list             |
| WA\_FLOW     | WhatsApp Flow             |
| WA\_CONTACT  | Contact card              |

***

### 3. Automation & System Messages

| Type                         | Description                                   |
| ---------------------------- | --------------------------------------------- |
| SYSTEM\_TEXT                 | Internal system message (not visible to user) |
| SYSTEM\_WARNING\_TEXT        | System warning (not visible to user)          |
| AGENT\_INTERNAL\_NOTE (NOTE) | Internal note                                 |
| HIDDEN                       | Hidden message                                |
| CLIENT\_JAVASCRIPT           | JavaScript execution event                    |
| WAIT                         | Wait/delay step                               |
| TEXT\_RESPONSE               | Automated text response                       |
| AGENT\_TRIGGERS              | Trigger execution                             |
| AGENT\_RECO                  | Recommendation message                        |
| CAROUSEL                     | Carousel message                              |
| FILE\_UPLOAD                 | File upload event                             |

> Some system-level messages may not be visible to end customers but are included in exports for audit purposes.
> {% endtab %}

{% tab title="Delivery Status" %}
The `Delivery Status` column indicates WhatsApp delivery lifecycle:

* **SENT** – Message accepted by WhatsApp
* **DELIVERED** – Delivered to user device
* **READ** – Read by user
* **FAILED** – Failed to send (see Failure Reason)
  {% endtab %}

{% tab title="Automation Source Type" %}
This field indicates what triggered the message.

| Value         | Meaning                           |
| ------------- | --------------------------------- |
| journey       | Sent as part of a Journey         |
| broadcast     | Sent via Broadcast                |
| campaign      | Sent via Campaign                 |
| chatbot       | Sent by Chatbot automation        |
| other         | Sent manually or system-triggered |
| {% endtab %}  |                                   |
| {% endtabs %} |                                   |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.quickreply.ai/product-modules/settings/export-message-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.