> For the complete documentation index, see [llms.txt](https://docs-latam.messaging.sinch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-latam.messaging.sinch.com/reports/viewing-and-exporting-reports/new-whatsapp-conversation-report.md).

# New WhatsApp Conversation report

### What are the new concepts 

In view of Whatsapp's new business model, based on conversations and no longer on the number of templates sent (in effect since February/2022), our report has been updated to reflect these changes. 

Now there is the concept of conversation, which is a fixed 24-hour session always initiated with the proactive sending of the first message by the company or when the company responds to the contact initiated by the user. 

There are two types of conversations: those that are initiated by the user (your customers), called "user initiated conversations", and those that are initiated by the company (you), called "business initiated conversations". 

![](/files/TahjUzfmgyci9pZIYmXL)

In the "Detailed Messages (MT)" report screen we have added 2 new filters: the Conversation ID and the Conversation Type (to see who started the conversation: business / user / free entry point).

![](/files/1NYFkip4z8pU8UtAw7Ts)

By applying the on-screen filters and extracting your detailed message (MT) report, you will see 3 new columns: Conversation ID **(1)**, Conversation Type **(2)** and Conversation Expiration Date. \
 

**(1)** Filtering by conversation ID, you can see how many messages belong to the same conversation, i.e. the same ID. Remembering that the session is now fixed (24h), that is, for each completed session I will have a conversation ID. \
 \
\&#xNAN;**(2)** Conversation Type: can be Business Initiated, User Initiated and Free Entry Point. \
 \
\- **Business Initiated:** the company initiates a conversation by sending a message to the user/customer \
 \
\- **User Initiated:** the user initiates a conversation by sending a message to the business/company and the company responds \
 \
\- **Free Entry Point:** conversations from Click to Whatsapp Ads and Facebook CTA are not charged. \
 \
In addition to adding new filters and information to the "Detailed Messages (MT)" report, we also created two new reports: Consolidated and Detailed Conversations. \
 \
1\. **View All conversations:** number of conversations that were Business Initiated and User Initiated \
2\. **View Free Conversations:** number of conversations that refer to Free Entry Point and Free Tier \
3\. **View Paid Conversations:** number of conversations that were Business Initiated and User Initiated 

![](/files/k2f5yZWxO0jkWfJW9k0v)

Another new concept is the Free Tier, where every month, the first thousand conversations will be free (for each WABA ID – WhatsApp Business Account), and can be initiated by both the company and the user. It is important to emphasize that even if the conpany has several WhatsApp numbers created in the same WABA, the limit of free conversations will still be 1.000 (and not 1.000 per number).  


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs-latam.messaging.sinch.com/reports/viewing-and-exporting-reports/new-whatsapp-conversation-report.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.