# User Experience

<figure><img src="/files/GLcMH91KJeFqXwJgYSky" alt=""><figcaption></figcaption></figure>

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: 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:

```
GET https://doc.moost.io/best-practices/user-experience.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.