> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/introducing-history.md). # Introducing ‘History’ Explore the redesigned 'History' tab in the Marketing Center, your new hub for managing sent emails, drafts, and more—all in one convenient place. {% embed url="" %} We’re thrilled to introduce a streamlined update to the Marketing Center! The ‘My Designs’ button has been replaced with a brand-new ‘History’ tab, now located directly in the sidebar navigation for easier access. Inside the ‘History’ tab, you’ll find everything from your sent emails and drafts to additional categories like Social Posts, Stories, and more, all neatly organized into tabs. This change is designed to save you time and make your marketing tools more intuitive. Whether you're a busy agent tracking your email campaigns or a marketing admin managing multiple assets, the ‘History’ tab keeps everything at your fingertips. This update is part of our commitment to enhancing your experience and giving you the tools you need to succeed. --- # 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://help.rechat.com/whats-new/introducing-history.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.