Language should not be a detour
Tourism, care, agriculture and hospitality teams often include people with different language backgrounds. A first phone call can stall when nobody is available to interpret. Vencur is intended to make the first step easier, so applicants can explain their availability and experience themselves.
The pilot is focused on a conversation in the applicant’s language and a summary for the employer. The website and product information are in German and English; product conversation languages are a separate matter and will be tested in the pilot.
What translation cannot do
A machine-generated summary can miss nuance. Teams should check important points against the quoted answers and ask a person directly when something is unclear. Vencur is not intended to infer suitability from someone’s accent, origin or confidence in a language.
- Questions stay tied to the role.
- Applicants are told before starting that AI is involved.
- A person reviews the information and decides what happens next.
Validate languages in the pilot
The languages supported in a specific pilot will be agreed in advance. We will not describe a language as available before the quality and workflow have been checked. The pilot form asks about your country and annual hiring volume.
Frequently asked questions
Which languages are available now?
Conversation languages are being checked with pilot teams. German and English are the website languages; that is not the same as a confirmed list of product languages.
Will answers be translated automatically?
Multilingual capture and summaries are in pilot development. Teams should review important statements in context and against the supporting quotes.
Does Vencur score accents or language ability?
No. A person’s origin, accent or confidence in a language should not be used as a measure of job suitability.
Can applicants choose a language?
The conversation should make the available choice clear. Each pilot team will agree which options it can offer before the workflow begins.