> 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.md).

# User experience

- [Introduction](https://docs.ur.app/design/user-experience/introduction.md): What UR provides, and what it is not.
- [Messaging hierarchy](https://docs.ur.app/design/user-experience/messaging-hierarchy.md): What to lead with, what to support with, and what to avoid.
- [Copy guidelines](https://docs.ur.app/design/user-experience/copy-guidelines.md): Recommended terminology for account opening and feature descriptions.
- [Partner positioning of UR](https://docs.ur.app/design/user-experience/partner-positioning.md): How to introduce UR in banners and provide persistent account access.
- [Visual hierarchy](https://docs.ur.app/design/user-experience/visual-hierarchy.md): How much screen prominence to give the account, actions, and card.
- [Account creation](https://docs.ur.app/design/user-experience/account-creation.md): The authentication paths for creating a UR account, and the URID.
- [KYC](https://docs.ur.app/design/user-experience/kyc.md): The three-part KYC flow and how to show the URID throughout it.
- [Card activation](https://docs.ur.app/design/user-experience/card-activation.md): Currency authorization and card activation by integration mode.
- [Card management](https://docs.ur.app/design/user-experience/card-management.md): The card hub for security and spending controls.
- [Off-ramp](https://docs.ur.app/design/user-experience/off-ramp.md): Converting digital assets to fiat in the UR account.
- [Bank transfer](https://docs.ur.app/design/user-experience/bank-transfer.md): Receiving funds from external bank accounts into the UR account.


---

# 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.md?ask=<question>&goal=<user_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.