The title trap

An AI receptionist, an AI care coordinator, an AI analyst. Each name implies a scope that nobody wrote down, and both the buyer and the model then infer that scope, differently.

A job title is a compression of decades of institutional context: what the role does, what it escalates, what it never touches. Software has none of that context. Handed only the title, it improvises the boundary, and the improvisation is invisible until the day it matters.

Name the task and the contract. Not an AI care coordinator, but a worker that assembles a referral packet from these three sources and hands it to a named reviewer within one business day.

The named version is less impressive in a slide and considerably easier to accept, reject, or improve. That trade is the whole argument.