> For the complete documentation index, see [llms.txt](https://docs.littlebaytech.com/templates/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.littlebaytech.com/templates/messaging-template/release-notes/06-14-guide.md).

# 06/14/19 Guide on New Conversation Functionality

## How to Add the Needed Actions to the Create New Conversation Functionality

{% hint style="info" %}
Please note this is only applicable to applications created with the Messaging Template before 06/14/19.  
{% endhint %}

**Step 1: Remove the "Trigger View Conversation - Mobile" and "Trigger View Conversation - Desktop" actions from the following workflow:**

On the messages page, in the **"E. New Conversation"** workflow folder, remove the Trigger View Conversation - Mobile and Trigger View Conversation - Desktop actions from the `Button Send Message (inside Floating Group - Create New Conversation), *only when Group Conversation's Container's ExistingConversation is empty` workflow event: 

![](/files/-LhJzMh7nLTvYjxshFz_)

**Step 2: Add the following "Go to page" action in that same workflow event**\
In that same workflow event, add the "Go to Page Messages" action to the end of the workflow, with the parameter c=(Step 1's Create a New Conversation's...)'s unique ID:

![](/files/-LhK0kSbYOWhMGUiT3PR)

*Workflow Notes:*\
Go to the messages page, with the parameter c=\[Step 1's Create a new Conversation's... unique ID)\
This action navigates the Current User to the messages page, and removes the "v" and "u" parameters from the page URL.  When the page is reloaded, the pageload workflows will then automatically trigger the "View Conversation - Desktop" or "View Conversation - Mobile" custom events so the new Conversation is shown. 

**Step 3: Remove the "Trigger View Conversation - Desktop" and "Trigger View Conversation" mobile actions in the second Button Send Message Workflow (when the ExistingConversation custom state is not empty)**\
On the messages page, in the **"E. New Conversation"** workflow folder, remove the "Trigger View Conversation - Mobile" and "Trigger View Conversation - Desktop" actions from the `Button Send Message (inside Floating Group - Create New Conversation), *only when Group Conversation's Container's ExistingConversation is not empty` workflow event: 

![](/files/-LhK-apH8wj9MqJYLg-R)

**Step 4: Add the following "Go to page" action**\
In that same workflow event, add the "Go to Page Messages" action to the end of the workflow, with the parameter c=(Step 3's Make Changes to a Conversation's...)'s unique ID:

![](/files/-LhK0RvpUwhOaC_DGIIR)

*Workflow Notes:*\
Go to the messages page, with the parameter c=\[Step 3's Make Changes to a Conversation's... unique ID)\
This action navigates the Current User to the messages page, and removes the "v" and "u" parameters from the page URL.  When the page is reloaded, the the pageload workflows will then automatically trigger the "View Conversation - Desktop" or "View Conversation - Mobile" custom events so the existing Conversation is shown.


---

# 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.littlebaytech.com/templates/messaging-template/release-notes/06-14-guide.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.