01Start with the assistant's personality
Every naming decision flows from one question: who is this assistant to its users? A customer-support chatbot should feel like a patient colleague; a developer tool's assistant should feel like a sharp pair-programmer; a kids' learning companion should feel playful and safe. Write down three adjectives for the personality first — warm, precise, witty, calm — and reject any name that clashes with them. Personality is also set by naming style: human first names (Ava, Milo) create warmth and familiarity, techy blends (Nexora, Synthix) set honest expectations that the user is talking to software, and abstract words (Lumen, North) feel premium but distant.
Consistency matters more than cleverness. If your brand voice is plain-spoken, a whimsical name will feel like a costume. Pick the personality, then let the generator's style filter do the narrowing.
02Design for the ear, not just the eye
Assistant names are spoken far more than they are read — in voice interfaces, in demos, in word of mouth. Say every candidate out loud three times. If you stumble, users will too. Short names with clear syllable stress win: two to three syllables is the sweet spot. Avoid names that are easily misheard by speech recognition (names that sound like common commands cause real confusion in voice assistants), and avoid unusual spellings of familiar sounds — if you have to spell it every time, it is the wrong name.
A useful test: call the name across a noisy room. If a colleague can repeat it back correctly on the first try, it passes the ear test.
03Match the name to the audience
Enterprise buyers, consumers, developers and children all read names differently. Enterprise assistants do best with credible, pronounceable names that would not embarrass anyone in a board meeting — think clean constructions rather than jokes. Consumer assistants can be warmer and more characterful. Developer tools reward short, typeable names that work as commands and package names. Kids' products need names that are friendly, obviously non-threatening, and easy for a child to say.
Also consider culture: check that a name has no unfortunate meaning in the languages of your target markets before you fall in love with it.
04Test names with real users
You cannot think your way to the right name — you have to test it. Show a shortlist of five to eight names to people who resemble your users and ask three questions: what kind of assistant does this sound like?, how would you spell it?, and what does it remind you of? The first answer tells you if the personality lands, the second tells you if it is spellable, and the third surfaces collisions with existing products you had never heard of. Five conversations will eliminate most bad candidates.
05Run the availability checklist
Before you commit: search the exact name on the web, check the .com domain at a registrar, search trademark databases in your markets, and check app stores plus major social platforms for handle availability. Our best-practices checklist walks through each step. Do this before you design the logo — renaming after launch is far more expensive than renaming a shortlist.
A name is a promise about personality. Pick the personality first, test the name with real ears, and clear it before you commit.