FlowsBook a callSign inCreate free accountSign up
AI employees and automation

Changing an AI employee with a sentence instead of the settings

Tell a running AI employee what to do differently in plain words: another city, a later hour, a stricter filter. Where to write it, what it changes, and how to undo it.

Part of the guide AI employees

By the xMap team · · 5 min read

You can change an AI employee in xMap Flows by writing what you want in plain words, such as "also look in Nairobi", "send it at 9 instead of 7" or "only keep places rated 4 or more". Ask xMap reads the sentence against the employee's flow, changes the blocks that need changing, checks the result on sample data and tells you what it changed, with a button to undo it. You can write it in the flow's editor or in the employee's thread in the Team inbox.

This article is for people who already have AI employees working and want to adjust them without learning every setting. It covers where to write, which sentences work well, a made-up week of changes to one employee, how to check and undo a change, and when the settings are still the better route.

Two places to write the sentence

  • In the editor. Open the flow and write in the Ask xMap bar at the bottom of the canvas. Select a block first and its name appears as a tag in the bar, so the change applies to that block only. The chat panel keeps the conversation, so you can follow up with "and the same for Madrid".
  • In the Team inbox. Each AI employee has a thread where it posts what it did. Reply there with a change, and it goes to Ask xMap as if you had written it in the editor. The answer in the thread says what changed, with Undo. Short instructions such as pause until Monday, start again, run now or raise the budget are carried out directly.

Both work as you: the change is saved with your name in the flow's history, and people who can only view a flow cannot change it this way.

Sentences that work well

Ask xMap does best with one clear change per message, naming the thing you can see in the flow:

  • Where: "Add Lagos and Accra to the cities", "draw it 5 km around our Lima office instead".
  • What: "Look for pharmacies as well as clinics", "leave out chains".
  • When: "Run on weekdays only, at 8:30 Singapore time", "make it weekly on Mondays".
  • How strict: "Only keep places rated 4.2 or more", "keep the 15 highest scores".
  • What the AI looks for: "When you score, favour places that opened this year".
  • Where results go: "Also send the list to the sales channel in Slack", once the Slack account is connected.

If a sentence leaves something open that matters, Ask xMap asks one short question back with choices rather than guessing. A request for a block your organization cannot use is answered plainly instead of being swapped for something similar.

A worked example: one employee over a week

A made-up case. A distributor of kitchen equipment has a Sales scout that looks for new restaurants in Sao Paulo every morning and emails the 20 best scored. Over one week the sales manager writes four sentences in its Team inbox thread.

DaySentence writtenWhat changed
MondayAlso look in CampinasArea of interest: Campinas added beside Sao Paulo
TuesdayLeave out fast food chainsNearby places: independent places only
WednesdaySend it at 9, not 7Schedule: 09:00 instead of 07:00
ThursdayPause until Monday, the team is at a trade fairPaused; it starts again on Monday

A made-up week, to show the kind of change each sentence makes.

On Tuesday the manager sees the list shrink more than expected: some well-run local groups with three or four branches were counted as chains and dropped. A tap on Undo puts the old setting back. The manager then writes "when you score, mark chains with many branches low", which changes the xMap LLM instructions instead of the filter, so small groups stay on the list and the big chains sink to the bottom.

Checking and undoing a change

  1. Read the words. Every change comes with a plain list of what moved, block by block: "Schedule: 07:00 to 09:00".
  2. Look at the canvas. In the editor the changed blocks flash, and the flow in words above the canvas reads the new version.
  3. Undo straight away if it is wrong. Undo works while nobody has changed the flow since.
  4. Later, use the history. Version history keeps the flow as it was before each Ask xMap change. What changed compares any version with now, and Restore puts it back.

When the settings are the better route

Sentences are quickest for one or two changes. Open the block's settings yourself when you are changing many values at once, typing a long list of addresses or names, connecting a new account, or uploading a table. And when you are not sure what a block does, its settings panel and its film explain it better than a guess in words.

What lands in the inbox afterwards

Nothing new to learn: the employee keeps its role, its thread and its results. Its next daily note in the Team inbox reflects the changed flow, and its emails or messages follow the new settings. Templates such as Watch new competitors and A weekly brief from your AI employees are good employees to practise on, since their blocks, such as Schedule, Area of interest, Nearby places, Filter, xMap LLM and Email, are the ones sentences change most often.

Questions

Do I need to open the editor to change an AI employee?

No. Replying in its Team inbox thread works for changes, questions and short instructions such as pause, run now or start again.

What if Ask xMap changes the wrong thing?

Press Undo on its answer, as long as nobody changed the flow since. Otherwise open the version history, compare with What changed and restore the version before.

Can a colleague who only views the flow change it with a sentence?

No. Changes need the right to edit the flow, and live flows that send need the right to deploy. A viewer can still ask questions in the thread.

Does a sentence change take effect immediately?

It is saved at once and applies from the employee's next run. A schedule change moves the next run time.

Can I make a change from Claude or ChatGPT?

Yes, if you connect them to xMap Flows: they can call the same Ask xMap to change a flow in plain words.

Templates that do this

IndustriesB2B sales

Read next

More on ai employees and automation · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.