> For the complete documentation index, see [llms.txt](https://doc.moost.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.moost.io/best-practices/user-experience.md). # User Experience Guidance on delivering recommendations clearly and effectively for maximum user engagement.
A powerful recommendation engine is most effective when its output is presented to the user in a clear, timely, and intuitive manner. The User Experience (UX) surrounding your notifications and recommendations is critical for user adoption, engagement, and satisfaction. This section provides best practices for designing and implementing various user-facing components that deliver recommendations from the MOOST platform. A well-thought-out UX strategy ensures that users see value in the recommendations and can act on them with minimal friction. This guide is divided into the following sub-sections: [Onboarding](/best-practices/user-experience/onboarding.md) How to build user trust from the start and maximize your notification opt-in rates. [Designing Rules](/best-practices/user-experience/designing-rules.md) Best practices for defining effective rule logic in the Rule Configurator. [Writing Notifications](/best-practices/user-experience/writing-notifications.md) How to write clear, actionable content for your recommendations. [Notification Center](/best-practices/user-experience/notification-center.md) Best practices for creating a persistent, in-app space for users to review all past recommendations. [In-App Notifications](/best-practices/user-experience/in-app-notifications.md) Guidance on using in-app modals, banners, or pop-ups for less urgent recommendations. [Push Notifications](/best-practices/user-experience/push-notifications.md) How to leverage immediate, actionable push notifications for time-sensitive advice. --- # 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://doc.moost.io/best-practices/user-experience.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.