Support customers in their own language
English docs, answers in the customer's language.
Your docs are in English but your customers are not. Translating and maintaining docs in five languages is unaffordable, so non-English customers file more tickets, get slower answers, and churn at higher rates.
BeforeQuery answers in the language of the question while retrieving from your English knowledge base, with citations back to the original docs. Workspace analytics break down questions by language so you can see which markets are asking what — and prioritize translation only where data says it matters.
How it works
- 1Keep writing docs in English (or your primary language) — no translation project required.
- 2BeforeQuery retrieves from your knowledge base regardless of the question's language.
- 3Answers are generated in the language of the question, with citations to the original docs.
- 4Language analytics show which markets ask what, so you translate only where data says to.
What you get
Features that make it work
Frequently asked questions
Do I need to translate my docs first?
No. The assistant retrieves from your existing docs and answers in the language of the question. Citations link to the original pages so users can still verify the source.
Which languages are supported?
Answering follows the language of the question — the underlying LLM handles the major world languages users actually ask in. Workspace analytics break down question volume by language so you can see coverage in practice.
How do I know which languages my customers use?
The workspace analytics overview includes top languages across questions, alongside questions per week and top sources — a data-driven view of where multilingual demand is concentrated.
How long does setup take?
Most teams are live the same day. You connect a source — a docs URL, GitHub repo, Notion workspace, or a file upload — and BeforeQuery crawls, normalizes, chunks, and embeds the content automatically. The website widget is a single script tag, and the Slack/Discord bots install in a few clicks. There is no model to fine-tune and no infrastructure to run.
Are answers backed by citations?
Yes. Every answer includes a structured citations list with the URL, title, and excerpt of each source used, and the answer text cites sources inline. Users can click through to verify any claim against the original document — which is what makes the answers trustworthy enough for support, sales, and internal use.
Is my content used to train AI models?
No. Your indexed content, embeddings, and conversations are isolated to your workspace and are only used to answer your own questions. Content is never shared across customers, and data is encrypted at rest and in transit. Enterprise plans add OIDC/SAML SSO, audit logs, and data-residency options.
Which knowledge sources can I connect?
18+ source types: websites, GitHub, GitLab, Notion, Confluence, Google Drive, SharePoint, Shopify, Zendesk, Jira, Linear, Salesforce, Slack, Discourse, Stack Overflow, YouTube, OpenAPI specs, and direct file uploads (PDF, Markdown, TXT, HTML). Sources sync on a schedule, and GitHub/GitLab can re-index automatically via webhooks on every push.
What happens when the AI is not confident in an answer?
Answers are confidence-scored. When retrieval confidence falls below your threshold, BeforeQuery returns a transparent, configurable fallback — typically pointing users to your support channel — instead of guessing. Those unanswered questions are logged in knowledge gap analytics so you can close the gap in your docs.
Related use cases
Deflect repetitive support tickets
Answer common questions before they become tickets.
Fix slow first response times
Give customers an accurate answer in seconds, not hours.
Deflect tickets at the support form
Answer the question while the user is still typing it.
Ready to support customers in their own language?
Connect your knowledge sources and see cited AI answers in minutes — free, no credit card required.
Get Started Free