> 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/seller-report.md). # Seller Report Show Sellers the Work Behind Their Listing Your sellers want to know what you’re doing to market their home. The new **Seller Report** gives them a clear, professional view of the work happening behind the scenes, including emails, social posts, ads, print pieces, and the results behind them. Everything is brought together in one report that is ready to share. {% embed url="" %} ### What Is the Seller Report? The Seller Report is a new Rechat feature that turns your listing marketing into a clean, easy-to-read report for your seller. Instead of sending a few numbers or explaining your activity piece by piece, you can show the full story of how the listing has been marketed. The Seller Report can include: * Marketing emails * Email performance, including opens and clicks * Social media posts * Digital advertising * Print marketing * A timeline of marketing activity ### Get Started Create a Seller Report from the Marketing Center and share your listing marketing as a downloadable PDF or interactive flipbook. Learn More --- # 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/seller-report.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.