> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/workflows/route-requests-by-the-requesters-country.md).
# Route requests by country
Send requests to the right team, approver, or inbox based on where the requester is located.
In Siit, every person can have a **Country code**. You can use it in the workflow builder to branch a request based on where the requester works, without duplicating a workflow per country.
The one thing to know before you start: **Country code holds the two-letter code, not the country name.** Germany is `DE`, not `Germany`.
### Step 1 — Check the country code on a person's profile
Open **Context → People**, select someone in the country you want to route, and look at their information panel.
### Step 2 — Add a branch on Country code
Create or open a workflow, then add a **Branch**.
In the condition builder, pick **Requester → Country code**, then enter the code for the country you want to catch.
For example:
* `DE` for Germany
* `FR` for France
* `GB` for the United Kingdom
* `US` for the United States
* `NL` for the Netherlands
You can find the code for any country in the [**ISO 3166-1 alpha-2 list**](https://www.iban.com/country-codes)**.**
⚠️ Enter the code in uppercase, exactly as it appears in that list. Entering a country name such as `Germany` will simply never match, and the workflow will run without ever taking that branch.
### Step 3 — Define the actions for each country
Under each branch, add the actions that should run for that country. Common ones:
* Assign the request to a country or region inbox
* Pick a local approver instead of a global one
* Apply the right business calendar so SLAs follow local working hours
* Reply with a message template in the local language
* Add a country tag for reporting
Add one branch per country, or per group of countries if your setup allows matching several codes in one condition.
### Where else you can use the country code
The same field is available beyond the workflow builder:
* **Audiences in the Service Catalog**, to show a service only to people in certain countries.
* **Filters** in the People list.
* **The API**, where the `country` field on a user takes the same two-letter code. See the [API reference](https://developer.siit.io/api-reference/user/create-user).
---
# 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.siit.io/guides/workflows/route-requests-by-the-requesters-country.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.
