> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/bot-studio/actions/customer-management/how-to-use-the-close-conversation-feature.md). # How to Use the Close Conversation Feature Learn how to use the 'Close Conversation' feature on DoubleTick. Automate chat closures to prevent SLA breaches and manage resolved customer interactions. Efficiently managing chat conversations is essential for delivering timely assistance and meeting service level agreements (SLAs). With the "Close Conversation" action component, businesses can automate the process of closing chats, providing valuable support to agents in preventing SLA breaches. Let's delve into how this action works and its practical application: 👇 ### **Automating Chat Closure:** * At the conclusion of your bot flow, implement the "**Close Conversation**" action component. * This action serves to automatically close the conversation once the customer reaches the end of the interaction. ### **Marking Conversations as Resolved:** * Upon application of the "Close Conversation" action, the conversation is marked as done and moved to the "Resolved" status. * This designation signifies that the customer's query or issue has been addressed satisfactorily, allowing agents to focus on other incoming inquiries without leaving lingering open chats. ### **Example Scenario:** Imagine a customer contacts a telecommunications company's support chatbot to inquire about upgrading their service plan. After engaging with the bot and receiving relevant information about available plans and pricing, the customer expresses satisfaction with the provided details. At this point, the bot triggers the "**Close Conversation**" action, automatically concluding the chat session. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://learn.doubletick.io/bot-studio/actions/customer-management/how-to-use-the-close-conversation-feature.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.