Huntit and your language
The interface is English, always. Your reports and what the AI writes about each post can change language.
There are three language settings, and they do different jobs.
Your AI language
The one your team works in.
It's the Organization row of the AI language block, in Settings → Organization, and it's read-only.
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 organization's.
A saved analysis stays in the language of whoever ran it, so a colleague who opens your brief reads it in your language.
Your reports' language
It's the Language field in Settings → Organization, and it words two things: your reports, and the AI's reads of your posts.
You pick it when you set up your organization. Change it whenever you like: your reports switch right away, including ones you've already shared.
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 field offers your AI language and English. When your AI language is English there's nothing to choose, so the field doesn't appear.
Say your team works in German, so that's what every brief and analysis comes back in.
Your reports go to an international board, so you set your reports' language to English. Your monthly report arrives in English, and so do the AI's reads of every post.
Your briefs on those same posts stay in German — they follow your AI language. A colleague who picked English for themselves gets theirs in English.
Quotes are never translated
Huntit's reads of a post follow your reports' 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 a Spanish competitor's 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 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 your reports' language, but filters in the app use the English names;
- this help centre, and Huntit's answers in Claude.