> ## Documentation Index
> Fetch the complete documentation index at: https://docs.utmkit.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Language

> The console's per-user language setting, how the assistant picks a language for each reply, and where client reports and emails fit in.

UTMKit speaks English and Spanish. Three things choose a language independently: your own console setting, the assistant's reply to a given message, and a client report's own setting — plus where emails you receive fall between the first two.

## Your console language

Open [account settings](https://app.utmkit.co/users/settings) and find **Language**, where **Console language** offers **English** and **Español**. It controls every page and the assistant by default. Until you choose one, the console follows your browser's own language.

## The assistant's language

The assistant answers in the language of the message you just sent, when that message makes one clear — write in Spanish and it replies in Spanish, in that turn, regardless of your console setting. A message with no language signal of its own (a short link pasted alone, a single word) falls back to your console language.

## Client reports

A client report — the page you share with a client and the scheduled mail that links to it — has its own language, one per workspace, set on its branding settings rather than following any member's console language. See [Client reports and branding](/en/analytics/client-reports-and-branding).

## Emails

A transactional email — a magic sign-in link, a billing notice, a workspace update — arrives in its recipient's own console language, because they have an account and a setting to read it from. An invitation to join a workspace, and the weekly digest of broken links, go to people by address rather than by account, so they arrive in the sender's console language instead: the inviter's, or the digest's creator. Either way English is the fallback when nobody's language can be read.