Ukrainian is written in Cyrillic, so the first thing many tools do is auto-detect it as Russian — and from that one wrong guess everything downstream breaks, because Ukrainian is a separate language with its own vocabulary, its own letters, and grammar Russian doesn't share. Picking the wrong language doesn't just add an accent; it produces the wrong words. Then, like its Slavic relatives, Ukrainian carries the meaning in the case endings rather than the word order and forces a done-or-ongoing choice on every verb — distinctions that resolve late and are easy to lose at speed. A line like "supports Russian," or even "auto-detect Cyrillic," on a feature list tells you almost nothing. Here's what actually decides whether a Ukrainian meeting comes back usable.
It's Cyrillic, but it isn't Russian
Ukrainian and Russian share the Cyrillic script and a family resemblance, and that surface similarity is exactly what trips tools up. Ukrainian has letters Russian doesn't use — ї and є and ґ — and a sound contrast Russian lost: the soft, breathy г (a voiced h, as in гарний, "nice") versus the hard ґ (a true g, as in ґрунт, "soil," or ґудзик, "button"). It also keeps a vocative case for addressing someone directly — Іван becomes Іване, пан директор becomes пане директоре — a grammatical form Russian dropped down to a few frozen relics. And the everyday words differ: "thank you" is дякую, not the Russian спасибо.
The reason this matters in a meeting isn't trivia — it's false friends. Неділя means Sunday in Ukrainian; the near-identical Russian неделя means week. A tool that detects the call as Russian can turn "let's meet on Sunday" into "let's meet for a week" and hand you a fluent, confident, wrong sentence. Getting the language right is the first decision, and a tool that guesses Russian has already lost.
The endings carry the meaning, so word order is free
Ukrainian is heavily inflected: nouns, pronouns, and adjectives change their endings to mark case — who is the subject, who is the object, whose is what, to whom — across seven cases. Because the role is carried by the ending rather than the position, word order is free, and speakers reorder words for emphasis and flow, fronting whatever matters most. For a translator that's a trap, because mapping Ukrainian word order onto English subject-verb-object naively will sometimes reverse who did what. The tool has to read the case endings to recover the roles, then rebuild the sentence in fixed English order. Miss an ending — easy to do when fast speech blurs an unstressed final vowel — and you can swap the subject and the object while producing a grammatical English sentence that says the opposite. This is the same "the grammar, not the order, carries the meaning" problem behind Russian ↔ English meeting translation, and it lives in the endings just the same.
Every verb makes you choose: done, or ongoing
Like Russian, Ukrainian verbs come in aspect pairs — imperfective and perfective — and the choice is grammatically obligatory. The imperfective frames an action as ongoing, repeated, or general; the perfective frames it as a single completed whole. Робити and зробити both translate loosely as "to do," but one means "to be doing / to do in general" and the other means "to get done / to complete." In a meeting that distinction is decisions and status: ми робили міграцію ("we were doing the migration") versus ми зробили міграцію ("we completed the migration") is the difference between a task in flight and a task closed. English carries this with tense, auxiliaries, and context, so a tool has to detect the Ukrainian aspect and render it as the right English construction — not collapse both into a flat "do." Get the aspect wrong and a finished commitment reads as still-in-progress, or vice versa, and the summary then propagates the error. For why these meaning-bearing distinctions are easy to lose at speed, see how accurate is AI meeting translation.
Why this specifically stresses real-time captioning
Live translation lives on a tension between latency and committing too early, and Ukrainian loads that tension three ways. First the tool has to get the language right — and "Cyrillic" is not enough, because the words diverge from Russian. Then the ending that assigns a role, or the aspect that marks completion, can sit at the end of the word or the clause: show the caption early and you risk fixing the subject and object before the endings confirm them, or printing "doing" before the perfective resolves it to "done." Wait for the whole clause and you add delay. A tool built for Ukrainian has to identify the language correctly, parse the morphology rather than the order, choose the right aspect, and land the caption once — not flash a guess and revise it on screen. A fluent English sentence that quietly swaps who-did-what, marks a closed task as open, or turns Sunday into a week is more dangerous than an obvious error, because no one in the room stops to question it.
How to do it with Sageio
- Add
bot@sageio.netto your Google Meet calendar invite. It joins on its own — no extension, nothing to install. - Each participant picks their caption language. The Ukrainian-speaking team reads clean Ukrainian — actual Ukrainian, not Russian — and a colleague elsewhere reads clean English, both from the same spoken Ukrainian, at the same time. (Sageio translates into 20+ languages.)
- Everyone speaks naturally — Ukrainian, the free word order, the aspect, all of it. Translated captions appear in about two seconds.
- Afterward, a searchable transcript and an AI summary arrive within about five minutes, shared at the host's discretion.
(Today this runs on Google Meet; Zoom and Microsoft Teams support is coming soon.)
How to test any tool in five minutes
Start with the language itself: say a word that diverges from Russian — неділя ("Sunday," where the Russian look-alike неделя means "week") — and check the English says Sunday, not a week. That one word tells you whether the tool detected Ukrainian or fell back to Russian. Then say an aspect pair in context (ми робили міграцію vs ми зробили міграцію — "we were doing the migration" vs "we completed the migration") and see whether the captions distinguish in-progress from done. Finally, say a sentence with object-before-subject order, where the case endings rather than the position say who did what, and check the English keeps the roles straight instead of reversing them. If it turns Sunday into a week, flattens the aspect, or swaps subject and object, the tool wasn't built for spoken Ukrainian.
Is it private?
For anything that joins your meetings: Sageio doesn't use your meeting content to train AI models, and its AI vendors are contractually restricted from doing the same. Audio is processed in memory and discarded — only the text transcript and summary are kept, encrypted, in the region you choose (US, EU, or APAC). Enterprise customers can self-host the entire stack.
Frequently asked questions
Why does detecting "Russian" instead of Ukrainian produce wrong words? Ukrainian and Russian share the Cyrillic script but are distinct languages with different vocabulary, including false friends — неділя means "Sunday" in Ukrainian and the near-identical Russian неделя means "week." A tool that auto-detects the call as Russian translates the wrong dictionary, so it can hand you a fluent sentence that says the opposite of what was meant.
What makes Ukrainian different from Russian, linguistically? Ukrainian has its own letters (ї, є, ґ), a hard ґ versus a soft, breathy г, a productive vocative case for addressing people that Russian mostly lost, and a separate everyday vocabulary (дякую, not спасибо). It shares the Slavic features of case endings and verbal aspect, but it is not a dialect of Russian.
What is verbal aspect and why does it matter in a meeting? Ukrainian verbs come in imperfective/perfective pairs that mark an action as ongoing or completed — робити ("be doing") versus зробити ("complete"). In a meeting that's the difference between a task in flight and a task closed, so a tool has to render the aspect as the right English construction rather than collapsing both into "do."
How fast are the translated captions? About two seconds, fast enough to keep a live conversation moving, with a searchable transcript and summary within about five minutes after the call.
What does it cost to try? Every plan starts with a free 60-minute trial, no credit card required. After that, Professional is $49/month and Teams is $99 per seat/month (annual billing includes 2 months free); Enterprise is custom-priced.
If your team works in Ukrainian, the honest test is whether a native speaker reads the live captions and hears the actual meeting — in Ukrainian, with the roles assigned from the endings and the aspect kept straight. Add the bot to your next call and let them judge.