Naming your AI employees so the whole team knows which one is which
Seven AI employees all called News watcher is a puzzle in every inbox. A simple naming pattern, where names show up, and how to rename one in two clicks.
Part of the guide AI employees
Name an AI employee after what it watches and for whom, not after the kind of work it does: Lisbon openings for the west team tells a colleague more than Opening watcher, which is what xMap Flows calls it by default. Every AI employee already has a role worked out from its blocks; once you have two of the same role, give each its own name from the card's menu with Rename. The name then shows wherever the employee speaks: its card, the Team inbox, notifications, the morning briefing, the Monday email and results.
This article is for whoever sets up AI employees for a team: a sales manager with a dozen scouts, an operations lead watching several cities, an agency running employees for clients. It explains how the default names are made, a naming pattern that scales, a worked example and the small habits that stop confusion.
How an AI employee gets its name today
xMap Flows reads each flow's blocks and gives it a role and a subject. A flow that searches for new places with Only new becomes an Opening watcher; one that scores places for sales is a Sales scout; job postings make a Hiring scout; road incidents a Road watcher; news feeds a News watcher. The subject comes from the area and the kind of place, such as Toronto pharmacies or restaurants in Madrid and 2 more.
That works well for the first few. It stops working when one team has several employees doing the same job in different places, or for different people: seven News watchers look identical in a list of notifications, and nobody knows which one needs attention.
Each AI employee also belongs to a flow, which has its own name. The two are separate on purpose: the flow's name is for whoever builds and edits it, the employee's name is for everyone who reads what it sends.
A naming pattern that scales
A good name answers, in under 40 characters, the question a colleague asks when a message arrives: what is this about, and is it for me? A pattern that works for most teams is what it watches, where, and for whom:
| Default | Better name | Why |
|---|---|---|
| News watcher | Port news for the logistics desk | Says the subject and the reader |
| Sales scout | New cafes, Lyon east, for Ana's patch | The kind, the area and the owner |
| Road watcher | Closures near our Durban depots | Readers see at once if it affects them |
| Rival watcher | Brand X branches in Vancouver | The rival and the city, nothing else needed |
Made-up examples of default roles and the names a team might give them.
A few rules keep a set of names tidy:
- Lead with the difference. If all your employees watch openings, do not start every name with Openings; start with the city or the client.
- Name the reader when it is one person or team. It tells everyone else they can ignore the message.
- Avoid people's first names for the employee itself. A name like Sam reads like a colleague; when Sam the person joins the team, every message is ambiguous.
- Keep the role in mind, not in the name. xMap Flows still shows the role the blocks give it, so you do not need to repeat it.
Where the name shows up
Once renamed, the employee uses its own name across the product:
- Its card on the Flows page and the panel that opens from its picture.
- Its thread in the Team inbox, where it posts its daily note and where you can reply to it.
- Notification cards and the notification centre.
- The morning briefing, the weekly review and the Monday email with each employee's report card.
- The org chart of your AI employees, and the results it found.
- Client views, if you share an employee's work with a client.
A worked example: a media monitoring team
This example is made up. A small team that monitors news for clients has built seven AI employees over three months, each reading different feeds for a different client. All seven are News watchers. Every morning the team's notification centre shows seven cards with the same title, and the Monday email lists seven identical report cards.
- List the employees on the Flows page and note, for each, the client and the topic it watches.
- Choose the pattern: client, then topic. Short client codes keep names short.
- Open each card's menu, choose Rename, and type the employee's name, such as Harbour Co: shipping news, leaving the flow's name as it is.
- Check the Team inbox: each thread now carries the client's name, so the account lead for each client can find theirs.
- Agree that every new employee is named on the day it is hired, using the same pattern.
The change takes a few minutes. The next Monday email is readable at a glance, and when one employee fails overnight, the notification says which client is affected.
How to do it with an AI employee
Naming is not a block, but the blocks decide the default role, so they are worth knowing when you plan a set of employees. A typical pair for one city might be:
- Schedule, Area of interest, Nearby places and Only new, then Email: an Opening watcher. Rename it, for example, Nairobi openings for the field team.
- Schedule, News with your feeds and words, then Email: a News watcher. Rename it, for example, Nairobi retail news for the board.
What lands in the inbox is the same as before, but the subject line, the notification and the Team inbox thread now carry the name you chose, so the right person opens it. Starting points: New places every morning, only new and Rival openings and closures every month.
Questions
Does renaming an AI employee change what it does?
No. The name is a label; the blocks, the timetable and where it reports stay exactly as they were. The role worked out from its blocks is still shown beside the name.
What is the difference between the flow's name and the employee's name?
The flow's name is for the people who build and edit it. The employee's name is what everyone sees in messages, notifications and reports. You can change either from Rename on the card's menu.
How long can a name be?
Up to 40 characters. Clearing it, or typing the role itself, puts the default role back.
Can I rename an employee from Claude or ChatGPT?
Yes, if you connect an AI assistant to xMap Flows: there is a tool to rename an employee and its flow. Ask xMap, the assistant in the app, can do it too and asks you to confirm first.
Templates that do this
Read next
More on ai employees and automation · Every article · Templates