Setting up approval for the messages an AI employee writes
When an AI drafts emails or WhatsApp messages for you, a short review catches the wrong name, claim or tone. How to design that step so it stays quick.
Part of the guide AI employees
To approve the messages an AI employee writes, put an Approval step between the block that drafts them and the block that sends them, set it to approve each item on its own, and let the approver rewrite the subject and body fields. The approver then sees every draft beside the facts it was written from, ticks the good ones, fixes the nearly good ones in place and leaves the rest. Designed well, a batch of fifteen drafts takes a few minutes and nothing leaves your company that a person has not read.
This article is about designing that review so it stays quick and catches what matters: what the drafting step should hand the reviewer, what to look for in each draft, who should approve and how fast, and how to tell from the edits when the AI needs better instructions. It suits sales teams, agencies, recruiters and anyone whose AI employee writes to people outside the company.
Give the reviewer the facts, not only the draft
A draft on its own is hard to check: is the shop really new, is that the owner's name, did they really get 400 reviews? The fix is in the drafting step. Ask xMap LLM for three fields, not one: the subject, the body, and a short line of reasons that cites the facts it used. The Approval page shows each item with the fields you choose in its note, so the reviewer reads "Opened in March, rated 4.7 on 52 reviews, owner Ana Ruiz" above the message and can check the message against it in seconds.
- email_subject and email_body: the message itself, the fields the reviewer may rewrite.
- why: one line of facts the message relies on, for the reviewer only, never sent.
- The item's own fields: name, address, phone, rating and anything a later block will use, so a wrong match is obvious.
What to check in each draft
Reviewers get faster when they look for the same few things every time. Five checks catch most problems.
- The right recipient. Does the name and business in the greeting match the item? A draft addressed to the wrong branch is the most embarrassing kind of mistake.
- Every claim is true. Anything the message says about the business, such as an opening, a rating or a new branch, should appear in the facts line. Delete a claim the facts do not support.
- Nothing promised that you cannot keep. No prices, discounts or dates the reviewer has not agreed.
- The tone fits the place. A message that suits an office may read oddly to a family bakery. Shorten rather than rewrite.
- A clear, small ask. One question or one next step. Cut a second request.
How to set the Approval step
The Approval block stops the run and asks the people you choose: the flow's owner, the organization's admins, or members you name. Set Approve to each item on its own, so one weak draft does not hold back the rest; up to 50 items wait in one approval. Under the approver can change, list the fields to rewrite, such as email_subject and email_body, and the approval page shows them as boxes under each item. Their edited words are what the next block sends.
Choose how long the run waits, from a day to a month, and what happens when nobody answers. For messages to people outside the company, stop the run: an unanswered batch should send nothing. The request arrives by email and in the app, and the block can also post it to Slack, Telegram or WhatsApp with a link to the page, where each item is ticked and answered.
A worked example: a recruitment firm in Singapore
This example is made up. A recruitment firm in Singapore has an AI employee that finds companies posting finance roles each morning, drafts a short note to each hiring manager and sends it after approval. In its first month the reviewer handles about twelve drafts a day: she sends seven untouched, edits four, usually trimming the second paragraph or correcting a job title, and declines one, usually a staffing agency posting on behalf of a client.
Her edits are the useful signal. After two weeks the firm adds two lines to the drafting instructions: keep the note to three sentences, and skip postings where the company is itself a recruiter. The next month she edits one draft in ten instead of one in three, and the review takes her a couple of minutes over coffee.
Mistakes that make approval a chore
- One approval for the whole batch. A single bad draft blocks fourteen good ones. Approve item by item.
- Drafts with no facts beside them. The reviewer then has to open every business to check it. Ask the AI for a facts line.
- Too many approvers. When five people are asked, each assumes another will answer. Name one person and an admin as backup.
- Never changing the instructions. If the same edit is made every day, write it into the drafting step.
- Approving follow-ups one by one. For sequences, use Outreach: you approve each first message, and its follow-ups go on their own and stop when the person replies.
The flow, in order
- A source, such as Nearby places or Job postings, then Only new.
- xMap LLM: write email_subject, email_body and a why line from the item's own fields.
- Approval: each item on its own, the approver can change email_subject and email_body, one named person, stop the run after two days.
- Email, one per item, to each item's own address, or an app block such as WhatsApp.
What lands in the reviewer's inbox is one notice a morning: a link to the day's drafts, each with its facts, ready to tick, edit or leave. A quicker route to the same safety is setting the AI employee to Ask me first, which puts an approval before every block that sends. Templates to start from: full outbound engine: find, research, approve, send, more reviews for my clients: a request message for each and hiring outreach.
Questions
Can the approver edit a message before it is sent?
Yes. List the fields the approver can change, such as the subject and body; their edited words are what the following block sends.
How many messages can wait in one approval?
Up to 50 items when each is approved on its own. Keep daily batches well below that so the review stays quick.
What happens if nobody approves?
The block does what you chose: stop the run, so nothing is sent, or carry on as if approved. For messages to outsiders, stop.
Can I approve from my phone?
Yes. The request can arrive by email, in Slack, Telegram or WhatsApp, with a link to the approval page, which works on a phone.
Templates that do this
Read next
More on ai employees and automation · Every article · Templates