> For the complete documentation index, see [llms.txt](https://docs.ur.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ur.app/design/user-experience/messaging-hierarchy.md). # Messaging hierarchy What to lead with, what to support with, and what to avoid. Order your messaging so the account leads and the card supports. This section lists what to emphasize first, what to introduce next, and what to avoid. ### Primary messaging Lead with the account. Put the total account balance front and center, break it down by currency, and surface the actions that make the account useful: deposit, send, and convert. ### Secondary messaging Once the account value is established, introduce spending. This is where the multi-currency debit card, card management, and transaction history belong; they round out the account rather than define it. ### What to avoid Do not position UR primarily as a card. Framing such as "get your crypto card", a payment card service, a crypto card offering, or any card-first value proposition buries the account that funds it. --- # 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://docs.ur.app/design/user-experience/messaging-hierarchy.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.