huntitHelp center

Huntit and your language

The interface is English, always. The reports your clients read and what the AI writes about each post can change language.

There are three language settings, and they do different jobs.

Your agency's language

The one your team works in. It's the Agency row of the AI language block, in Settings → Agency.

It's the default for everything only your team sees: the intelligence brief, the comments intelligence layers, every custom analysis, and a video Claude watches for you.

Changing it goes through support.

Your own language

Below it, Your language lets you pick a different language for the analyses you run. Everyone else keeps the agency's.

A saved analysis stays in the language of whoever ran it, so a colleague who opens your brief reads it in your language.

Each client's language

The one your client meets. You set it on the client's own page, and it words two things: their report, and the AI's reads of their posts.

A new client starts on your agency's language. Change it whenever you like: their existing reports switch right away.

The AI sentences inside a report, and the AI reads of posts already analyzed, keep the language they were written in, so an older report can mix the two. Every AI read after the change follows the new language.

The picker offers your agency's language and English. An agency already working in English has nothing to choose, so no picker appears.

Say your agency works in German, so that's what every brief and analysis comes back in.

One of your clients reports to an international team, so you set that client to English. Their monthly report arrives in English, and so do the AI's reads of every post under them.

Your briefs on those same posts stay in German — they follow your language, not the client's. A colleague who picked English for themselves gets theirs in English.

Quotes are never translated

Huntit's reads of a post follow the client's language: the summary, the value proposition, the visual hook, the filming setup.

The post's own words don't. Its hook, its closing line and the transcript stay exactly as they were said or shown — translating a quote changes what was actually said.

So that client's Spanish competitor post arrives with an English summary and a Spanish hook.

Audience phrases in comments intelligence work the same way: lifted word for word, in whatever language they were written, with a translation added when that isn't the language of the analysis. They're there so you hear how your client's market actually talks.

Now and then a post whose on-screen text is in another language comes back with its read fields in that language too. It's rare, nothing is broken, and there's nothing to fix on your side.

What stays in English

  • the interface — menus, buttons, page names and status labels;
  • the content group and content type on every post — one fixed English set, so a filter means the same thing for everyone. A translated report shows them in the client's language, but filters in the app use the English names;
  • this help centre, the agency view of a report, and Huntit's answers in Claude.