November 13, 2026
ElevenAI Custom Vocabulary: Team Dictation Test (2026)
A practical early-access pilot for names, acronyms and corrections across two accounts.

ElevenAI custom vocabulary needs a two-account test before a team rollout. An archived ElevenLabs product page says added names and acronyms work in dictation and meeting notes, but doesn't say whether one person's additions are visible to everyone. Check the dictionary's scope, then test whether corrections reach a second account.[1]
TechCrunch reported the announcement on November 13, 2026. The experimental app brings together dictation, meeting notes, and agent integration. It launched on November 11, not today. Crypto Briefing covered it on November 13, too.[2][3] This guide is based on published sources, not hands-on testing.
Take a project name that comes up in every Monday meeting. Having to fix its spelling in each follow-up email would get old quickly. ElevenAI's promise about industry terms caught my attention for that reason. I'd want the trial to include whoever will maintain the glossary after the launch demo ends.
What ElevenAI's terminology promise establishes
A November 11 snapshot of the product page says users can add product names, acronyms, and industry terms to help with dictation and meeting notes. It also advertises dictation in more than 90 languages.[1] These are vendor claims, not findings from a comparison test.
Automated access to the live product page was blocked during research. The main evidence is a complete Wayback capture dated November 11 at 23:13:14 UTC. In a separate report published on November 13, TechCrunch describes support for industry-specific terms and says users still need to sign up for early access.[1][2] Check with ElevenLabs for current access before planning a trial.
The two sources we reviewed don't explain how dictionary settings work. An account-wide dictionary, a shared company glossary, or terms inferred from past conversations could make the demos look similar. But each option would give administrators different tasks. Don't assume ElevenAI uses any of these setups until the product or its team confirms it.
The trial below follows one spelling from the first account to a second, then checks it again after an update.
Give two people a deliberately awkward glossary
Use a small fictional project, not a customer call. This is a proposed pilot, not something observed in ElevenAI.
Use "Kestrel Arc" as the project name. Include the fictional suppliers "Maren Works" and "Marin Works," along with the internal abbreviation "PIR," whose intended meaning depends on the sentence. Before recording any sample, write the correct forms in a reference document.
Ask the first participant to add only terms supported by the available dictionary controls. Record each term, where it was added, and which account made the change. If you can't find an administration control, ask ElevenLabs instead of guessing the setup steps from a screenshot.
Let the second participant dictate with their own settings, then compare the transcript with the reference. If their account does better, that's useful to know. But it doesn't prove a shared dictionary caused the improvement. Existing context or ordinary speech recognition could explain it too.
For the next round, record a baseline with a new made-up term on both accounts. Only then add it to the first account's dictionary. Keep each person's microphone, sentence, and app the same in both samples. That gives you a closer comparison of what changed when the term was added.
Add the following sentences to the proposed trial:
- "Send the drawing to Maren Works, not Marin Works."
- "Kestrel Arc needs a PIR review before we order the sample."
- "Keep PIR as an abbreviation in the subject line."
The names are intentionally similar. Make sure the output keeps them distinct instead of defaulting to the dictionary entry. The first sentence is accurate only if it includes both names.
Acronym expansion needs a separate note. The second sentence doesn't let the app decide what PIR means. If your team wants to keep the letters as written, count an unwanted expansion as an editing cost, even if the added phrase sounds plausible.
Test what happens after a term changes
Now change the spelling.
Suppose the approved spelling of your fictional project changes from "Kestrel Arc" to "KestrelARC." Update the dictionary entry using the trial account's available controls. Then ask both participants to dictate a new sentence. Check whether the new name appears in the other account, whether restarting makes a difference, and whether each person has to change it separately. These are questions to investigate, not features promised in the announcement.
Keep the old notes and check whether their text changes after the vocabulary update. Explain what happened either way. If a note stays the same, add a correction beside it if needed. If it changes, show readers what was rewritten. Don't assume that adding a term updates notes that were already saved.
If your team uses more than one language, ask a fluent colleague to write a second sample. Keep product names and abbreviations that shouldn't change. Then compare the final output with your colleague's sample. A tool's advertised language count doesn't prove it can handle mixed languages correctly.
If the product lets you, remove the temporary term and test another sentence. Make sure people know how to undo a bad addition before a plausible misspelling becomes the default in everyone's notes.
Decide who owns recurring corrections
After the pilot, keep a short record of the intended term, the output, the account, the input language, and whether anyone updated the dictionary. Log recognition errors separately from cases where the speaker changed their mind. Otherwise, the glossary will fill up with preferences no one can explain.
Decide who can settle disagreements about names. Use an approved reference for supplier names instead of letting the first colleague who fixes one set the standard. If an abbreviation has several meanings, it may be safer to keep the letters rather than use one expansion for every case.
I build DictaFlow, so I have a commercial interest in it. Its Knowledge Base includes custom vocabulary on the Free plan.[4] If you need personal dictation now, you can try the same small glossary test. This recommendation is for personal dictation. It makes no claim about shared glossary administration or an ElevenAI integration. Our custom vocabulary guide covers that narrower buying decision.
Before the trial ends, ask the second participant to dictate the renamed project once more. Keep that output beside the original reference. Whoever owns the rollout should be able to explain which account changed the spelling and what the other participant had to do to receive it.
Sources
[1] ElevenAI product page, archived November 11, 2026 at 23:13:14 UTC
[2] TechCrunch: ElevenAI launch coverage, November 13