Name

What do we call this thing? Is it a bot, AI, ChatGPT, an agent, or something else?

Users deserve to know what or who they are interacting with. Naming sets expectations, signaling whether this is a tool, a partner, or something in between. It also allows for customization: a name can be branded by the company, chosen by the user, or even adapted to a specific context. This makes the AI feel less like an abstract system and more like something that belongs in the user’s world.

AI names are an ambiguous pattern. If users already know they are dealing with AI, a generic label like “AI assistant” may suffice. But naming is also a brand decision and an opportunity to establish voice. Intercom calls their AI “Fin,” an approachable name that pairs with a disclosure badge so users know they are interacting with AI.

Salesforce’s “Einstein” ties into the company’s broader identity. GitHub’s “Copilot” communicates role and relationship, while Notion keeps things simple with “Ask AI.” Each choice positions the AI differently, framing it as either a teammate, a tool, or a brand persona.

Naming conventions are converging around four common approaches:

  • AI as a persona: A human-like name that implies individuality or personality.
  • AI as the company: Branded directly with the product’s or company’s identity.
  • AI as an entity: A functional title like Copilot or Assistant that emphasizes role.
  • AI as a technology: A generic technical label such as “AI.”

Alongside these, a secondary pattern is often used: badges that make it clear when the interaction is with AI versus a human. These signals support transparency, but they also work alongside naming choices to reinforce brand and user trust.

Design considerations

  • Make disclosure unambiguous. Even with creative or branded names, users should never mistake the AI for a human. Pair names with badges, context cues, or onboarding language that makes the AI nature explicit.
  • Use naming to reinforce brand strategy. A name is an extension of positioning. “Einstein” signals intelligence with a playful nod to Salesforce’s brand. “Copilot” frames GitHub’s AI as supportive, not directive. The name should amplify the product’s identity rather than feel bolted on.
  • Allow personalization when it adds value. Giving users the option to rename their AI can increase attachment and make the tool feel integrated into their workflow. A sales rep may call their assistant by one name, while a student may choose another. Personalization must still preserve disclosure and guard against impersonation risks.
  • Balance personality with utility. Names that overpromise human qualities can backfire when the system fails to live up to them. Keep the name aligned with what the AI can realistically do, so expectations and outcomes stay in sync.
  • Think cross-surface. The name appears in chat headers, notifications, voice prompts, and even API documentation. It should work consistently across contexts and languages, and avoid cultural references that won’t localize well.

Examples

Cognition’s AI Developer “Devin” is referred to by its name within the interface and when users communicate with it.
Intercom has given the name “Fin” to its personified AI, however the AI is always associated with clear AI disclosures.
The AI assistant Howie can be renamed so users can @ mention it in their emails without giving away its role as an AI tool.