One agent that answers in whichever language your customer writes in.
Support does not stop at English. If customers write to you in German, French, Spanish or anything else, an agent that only replies in English is only half built. Helpforge answers in the language a visitor actually writes in, refusals and citations included, with no translated FAQ to maintain and no separate setup per language.
Verified live on international customer conversations in German, French and Spanish. Try it in your own customers' language before you pay.
Versendet ihr auch nach Deutschland, und wie lange dauert die Zollabwicklung?
Ja, wir versenden nach Deutschland. Laut unserer Versandseite dauert die Zollabwicklung in der Regel 3 bis 5 Werktage, zusätzlich zur normalen Lieferzeit. Shipping
Où en est ma commande exactement, et quand serai-je remboursé si je la retourne ?
Je n'ai pas accès au statut de cette commande précise ni à l'historique de remboursement, donc je ne peux pas vous donner cette information. Je transmets votre question à notre équipe, qui pourra vous répondre directement.
Shown as written: a German shipping and customs question, answered and cited from the shipping page, then a French order-status question the agent has no way to verify, handed off instead of guessed at.
Reading any language is not the hard part. Answering honestly in it is.
A chatbot that merely detects a language and swaps a greeting has not solved multilingual support. The real work is finding the right answer regardless of language, replying in kind, and staying just as honest about what it does not know.
Cross-lingual retrieval already covers this. The embedding model that matches a question to the right page maps a German or French question into the same space as your English (or any-language) content, so it finds the right page regardless of whether your site and the question share a language. Nothing about your content has to be translated first.
The right page, found regardless of which language asked for it.The agent responds in whichever language the visitor wrote in, not the language your site happens to be published in. That includes the honest outcomes: a refusal and a handoff offer are given in the visitor's own language too, not just a successful answer.
The same honesty, in whichever language it is needed.Translation is instructed to stay strictly faithful to what your page actually says, never to smooth over a gap in your content with a plausible-sounding line in another language. If your policy does not cover a visitor's exact situation, the agent says so in their language rather than guessing to keep the reply sounding natural.
A faithful answer beats a fluent-sounding guess.A grounded answer still names the real page it came from, in whatever language it answers in, so a German or French visitor can check the source exactly the way an English one can.
Sources, not just a confident tone.Nothing to translate, nothing extra to pay.
Multilingual support here is not a paid tier or a project you run once and then maintain forever. It is one behavior built into every agent, live the same day as everything else.
What you get
- An agent that answers a German, French, Spanish or other-language question from your existing content, no translated version required
- The same grounded, cited answers your English visitors get
- The same honest refusal and handoff when your content does not cover something, in the visitor's own language
- No extra fee for however many languages your customers actually use
What you skip
- Writing or maintaining a translated FAQ or help center yourself
- A bot that only replies in English regardless of what was asked
- A confident-sounding answer that papers over a policy gap just to seem fluent
- A separate price or plan for supporting more than one language
One flat build fee, one flat monthly.
No per-seat charges, no per-conversation meter, and no per-language surcharge. The monthly covers hosting, the AI usage of a typical business, monitoring, and re-indexing when your site changes. You see it answer your own international customers before you pay anything.
Free demo on your real site first. Ask it a question in another language, then decide.
Multilingual support, answered honestly.
Does it really answer in the customer's own language, or just detect it?
It replies in the language the visitor wrote in. Retrieval finds the right page from your content regardless of the question's language, and the reply itself, including a refusal or a handoff, is generated in that same language. It is not a canned greeting swap; a German question gets a full German answer.
Do I need to translate my site or write FAQ content in other languages?
No. The agent reads what you already publish, in whatever language you publish it, and answers a visitor's question in the language they asked it in. You do not maintain a second copy of your help content.
Which languages does it support?
It is not a fixed list we hand-built one language at a time: the same retrieval and reply mechanism applies to whichever language a visitor writes in. We have verified it directly on German, French and Spanish conversations. If your customers write in a language you are not sure about, ask us and we will check it on your own content before you commit to anything.
Does it stay honest when it cannot answer, even in another language?
Yes. A refusal and the offer to hand off to your team are given in the visitor's own language, exactly like a successful answer would be. It is not built to guess in a foreign language just to avoid saying "I do not know."
Is multilingual support an add-on or an extra cost?
No. It is included in the same flat monthly fee as everything else, whether your customers write in one language or several. There is no per-language tier to buy.
Can it cite the source page in the visitor's language too?
Yes. A grounded answer names the real page it came from regardless of which language it answers in, so a German or French visitor can check the source the same way an English one can.
How does it find the right page if my site is only in English?
The embedding model behind retrieval maps a question and a page into the same space regardless of language, so a German or French question can match an English page directly. No translation step happens before the match.
Do I need any technical skills to set this up?
No. You send us your website URL, we build and tune the agent, and going live is a single line of code that we can add for you. There is no dashboard to master and no content to write yourself, in any language.
See it answer in your customers' own language.
Give us your website URL and we build a working demo of your agent, usually within 2 business days. You get a private link to test it, including questions in whatever languages your customers actually write in, before any commitment. No call, no credit card.