AI employee approval before sending: who signs off, how long it waits, and when to stop asking
A sign-off step is only useful if someone answers it. How to pick the approver and the wait, put an automatic check first, approve from your phone, and loosen it later.
Part of the guide AI employees
AI employee approval before sending works when it is designed like any other team process: one named person or small group answers, they know how long they have, a machine check has already removed the obvious errors, and the step is relaxed once the work has proved itself. In xMap Flows that means an Approval block with the right people, waiting time and fallback, a Check the work block before it, and the Approve buttons in the app people already watch.
Plenty has been written about what to read in each draft. This article is about the plumbing around the approval: who answers, what happens when nobody does, and how to stop approvals turning into a queue nobody clears.
Decide which sends need a person
Not every send deserves a stop. A rough sorting that most teams agree with:
| What the AI employee sends | Approval? |
|---|---|
| A list to your own team by email or Slack | Rarely: a mistake costs a minute |
| Rows into your own sheet or database | Rarely, once the columns are right |
| Emails or WhatsApp messages to people outside | Yes, at least for the first weeks |
| Anything that commits money, a date or a promise | Yes, always |
| A record created in a CRM other teams use | Often, until the fields are trusted |
A starting point; adjust it to how costly a wrong item would be.
Put a machine check first
A person approving twenty drafts should not be the one spotting a missing phone number. Check the work sits right after the AI block that drafted the messages and tests each item against rules in plain words, such as every email names the business, no numbers that are not in the data or under 120 words. What code can check (a phone, a website, an email, word limits, personal data) is free. With If it fails set to send it back to be redone, the AI gets the item again with what was wrong, up to three times. The approver then sees only drafts that already pass the basics, each marked with check_passed and any check_issues left.
Choose who answers and how long they have
The Approval block asks the flow's owner, the organization's admins, or members you name by email. Any one of them can answer, and the first answer counts. Two habits help:
- Name a small group, not everyone. Two people who know the customers beat ten who each assume someone else will answer.
- Match the waiting time to the message. Outreach to new businesses can wait two days; a same-day event alert cannot. If the moment passes, a late approval is worse than none.
Then set what happens when nobody answers: Stop the run, so nothing goes out, or Carry on, as if someone had approved. Stopping is the safe default for anything outside your company. A stopped run is not a failure, and the step says why it stopped.
Answer where people already are
Approvers get an email with Approve and Decline buttons and a notice in the bell. The block can also ask in Slack, Telegram or WhatsApp, with the buttons in the message, so the run carries on or stops as soon as someone taps. Set Approve to each item on its own when the drafts differ; the approver ticks the good ones, and only those go on. With The approver can change naming the draft's fields, such as email_subject and email_body, they can rewrite a line before approving.
A worked example (made up)
A corporate catering firm in Sydney writes to offices that have just opened nearby. Its AI employee runs every weekday:
- Nearby places finds new corporate offices and coworking spaces within its delivery area.
- Only new drops the ones already found.
- Apollo finds the office or facilities manager at each, from the firm's own Apollo account.
- xMap LLM drafts a short introduction for each, from the office's details.
- Check the work: names the company, mentions the street, under 100 words, no prices; failures sent back to be redone.
- Approval: the two account managers, each item on its own, email_body editable, also asked in Slack, two days to answer, then stop.
- Email, one per item, to each manager's address.
Most mornings the Slack message lists four or five drafts. One account manager taps through them on the way to work, fixes a greeting, declines one office that is already a customer, and approves the rest.
When to stop asking
Watch the declines. If a month goes by with almost none and few edits, the approval is costing time and protecting little. Move the employee from Ask me first to Act and tell me in its panel: it sends on its own and posts a note in the Team inbox saying what it sent, so you can still read everything after the fact. Keep approval on anything that commits money or a date. Approval blocks you added yourself stay whatever you choose there.
Mistakes to avoid
- Asking the whole organization and getting no answer at all.
- Leaving Carry on as the fallback for messages to customers.
- Approving item by item when every item is the same report; one approval for the whole list is enough.
- Forgetting that only real runs ask: a test run goes straight through and says who a real run would ask.
For a ready-made pipeline that finds, drafts, waits for approval and sends, start from the full outbound engine. The AI employees guide covers how much each employee should do alone.
Questions
Can someone approve from their phone?
Yes. The email's buttons open a short confirmation page, and an Approval set to also ask in Slack, Telegram or WhatsApp puts Approve and Decline in the message itself.
What happens if the approver declines?
Nothing after the Approval block runs or is sent, and the run is marked stopped, not failed. With each item on its own, only the ticked items go on.
Can an approver who cannot open the flow still answer?
Members who were asked and organization admins can answer even if they cannot open the flow.
Does Carry on now skip an approval?
No. Carry on now on a waiting run cannot skip an approval; someone asked must answer.
Templates that do this
Read next
More on ai employees and automation · Every article · Templates