> For the complete documentation index, see [llms.txt](https://docs.ai.insly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ai.insly.com/nora/onboarding/broker-mapping.md).

# Broker mapping

## What it is

Decides which broker is attached to the quote in Ledger, based on who sent the email. More reliable than AI extracting the broker from the documents.

## What you decide

* **Broker from Ledger user OR from a mapping:** A) Broker from Ledger user means fetching the user that corresponds to the sender’s email and taking the broker from there. It also sets that user as the quote’s agent. No list to maintain, but senders must be Ledger users. B) A mapping is a manually compiled list which maps sender address or domain to Ledger broker entity. An address match beats a domain match. The list needs to be maintained.
* **Broker required in follow-up OR fallback broker:** A) Required in follow-up – When no broker matched in extraction, a follow-up will go out to ask for one. B) When broker not required, but no broker matched in extraction, it’s possible to choose one specific Ledger broker to fall back to for all submissions.

## What to send us

* A) Broker from Ledger user OR B) from a mapping?
  * If A, confirm that senders are Ledger users.
  * If B, in the mapping, use broker names exactly as they appear in Ledger.
* A) Broker required in follow-up OR B) fallback broker?

## When

* Demo test decisions and mapping: 🟡 **TESTING**. Map a few of your own team’s addresses to test brokers so you can check the result in Ledger.
* Prod decisions and mapping: 🟢 **GO-LIVE**

## Good to know

* A broker name that doesn’t match anything in Ledger is ignored, never written to the quote.