> For the complete documentation index, see [llms.txt](https://docs.inogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inogic.com/whatsapp4dynamics/features/store-chat-history-in-chat-sessions.md).
# Store Chat History in Chat Sessions
WhatsApp4Dynamics provides the functionality to store chat history in chat sessions. This means that when you communicate with customers your WhatsApp Business Account from within the CRM, the entire conversation history is recorded and stored as a chat session.
Users can maintain **WhatsApp chat history** associated to each **Record with Dynamics 365 CRM** and track communication.
* To means the customer/partner with whom you would be chatting.
* Regarding defines the associated Record. (Record that was created from within the Chat UI)
* “Start /End Date & Time” will be mentioned for each session. (Each chat session will be maintained for 24 hours as per UTC Standard Time.)
* Configuration describes from which WhatsApp channel you are communicating.
Below is a screenshot showcasing the listicle view of the chat sessions.
Chat History can also be accessed from within the Chat UI.
{% hint style="success" %}
For further queries, reach out to us at
{% endhint %}
---
# 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.inogic.com/whatsapp4dynamics/features/store-chat-history-in-chat-sessions.md?ask=&goal=
```
`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.