> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/retail-lending/user-journeys.md).

# User Journeys

See how applicants, FI staff and Partners move through Retail LOS, stage by stage.

Retail LOS serves three audiences, and each has its own journey through the same application. An **applicant** is the customer applying, an individual or a business. **Financial Institution (FI) staff** review, decide and fund applications, and FI administrators set Retail LOS up. A **Partner (Broker)** submits deals for customers.

## Stage by stage

<figure><img src="https://2966508920-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff06WQMAu97E0STor0yyS%2Fuploads%2Fgit-blob-aab5b879237cb7fe7fef8df24bce8f069c9a3710%2Fuser-journeys-overview.png?alt=media" alt="Swimlane diagram titled User Journeys for Retail LOS. Three lanes, For Applicants, For FI Staff and For Partners (Broker), run across four stages: Intake, Underwriting, Closing and Funding. Applicants submit and the application appears for FI staff. Staff decide and the applicant sees the outcome. The applicant signs and staff work closing and funding. A Partner&#x27;s deal becomes an application."><figcaption><p>Follow the path from choosing a product to signing. Start with the <a href="/retail-lending/user-journeys/applicant-journey.md">Applicant Journey</a>.</p></figcaption></figure>

<table data-view="cards"><thead><tr><th>Related</th><th data-card-target data-type="content-ref">Page</th></tr></thead><tbody><tr><td>Where to start for your task.</td><td><a href="/retail-lending/start-here.md">Start Here</a></td></tr><tr><td>What Retail LOS is, and who uses it.</td><td><a href="/retail-lending/retail-los-overview.md">Overview</a></td></tr><tr><td>Step-by-step guides grouped by role.</td><td><a href="broken://pages/G0BgDJkKtRodgvWbl6nz">Broken link</a></td></tr><tr><td>What each role can open.</td><td><a href="broken://pages/EebOasKPKQhWq9ggrFQL">Broken link</a></td></tr></tbody></table>

| Stage            | For Applicants                                                                                                                                                    | For FI Staff                                                                                                                                                 | For Partners (Broker)                                                                                                        |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| **Intake**       | Chooses products, verifies an email, completes the form, adds documents and submits. See [Applicant Journey](/retail-lending/user-journeys/applicant-journey.md). | The application appears in **Applications List**. Staff can also [start one for an applicant](broken://pages/PJv5BraYfWZF1MxK4FTX).                          | Starts a deal for a customer in the partner portal. See [Partner Journey](/retail-lending/user-journeys/partner-journey.md). |
| **Underwriting** | Sees an outcome: approved with offers, "In Underwriting Review" or "Application Declined".                                                                        | Claims the application, reviews it and decides. See [Work an Application](broken://pages/lvXMbbnbRDUhZZqPPeJE).                                              | Tracks the deal in the Deal Pipeline.                                                                                        |
| **Closing**      | Accepts an offer and signs the agreement.                                                                                                                         | Works the closing tabs, such as **Financing Offers** and **Contract Generation**. See [FI Staff Journey](/retail-lending/user-journeys/fi-staff-journey.md). |                                                                                                                              |
| **Funding**      | Is told no further action is needed.                                                                                                                              | Works the funding tabs and checks.                                                                                                                           |                                                                                                                              |


---

# 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.uptiq.ai/retail-lending/user-journeys.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.