Review, approve and undo AI actions
When the Mesy AI co-pilot wants to change your data or send an email, it shows you a card first. You approve or discard the card in the conversation, and every pending card is also listed on the Approvals page.
Approve a change set in chat
Section titled “Approve a change set in chat”A proposed change appears below the conversation as a card headed Review changes, followed by a one-line summary. Each row names the record and carries a chip: Create, Update, Delete, Link or Run. Expand a row with Edit fields to change any value before you approve; an update shows the previous value as “was:”. When a required field is missing, the approve button stays off until you fill it in.
To approve the card:
- Check each row and edit any values you want to change.
- Click Confirm, which names the number of changes it applies.
- Read the card’s new heading, Changes applied, with a status beside each row.
Click Discard to drop the proposal. Clicking the cross collapses the card to a chip reading “staged changes”; click the chip to reopen it. Sending the co-pilot a new message replaces a pending card, so approve it before you move on.
Choose between duplicates
Section titled “Choose between duplicates”If a proposed record looks like one you already have, a card headed Possible duplicate lists the matches. Click Use this one beside a match to use the existing record, or click Create new anyway. When the matches themselves look like duplicates of each other, Merge… opens a comparison so you can merge them.
Send an email the co-pilot drafted
Section titled “Send an email the co-pilot drafted”An email draft appears as a card headed Review before sending, showing To, Cc, Subject and the body. Click Send to send it from your connected mailbox, or Discard. The heading changes to Email sent once it goes. The co-pilot never sends mail on its own, whatever its tier. A drafted workflow arrives as a chip reading Review workflow draft, which opens the workflow builder.
Find pending and past cards on the Approvals page
Section titled “Find pending and past cards on the Approvals page”Click Approvals in the sidebar. The Needs me column groups your pending cards by where they came from: Email, Marketing, Workflows, Telegram, Teams, WhatsApp and Co-pilot. A card from a chat conversation shows as a row with Review in chat, which opens the conversation at that card, and Dismiss. A card with no conversation, such as a workflow proposal or an email capture, expands in place with Review or Approve. A campaign launch shows Approve & send.
When nothing is waiting the column reads “Nothing needs you right now.” If email auto-linking is off, a line says proposals won’t arrive. Admins also see a link to turn it on under Admin, Organization.
The Done for me column shows what the co-pilot has done. It counts the emails it linked and the records it created in the last seven days. It lists Recent AI actions, with a link to All AI changes, and Linked emails. Expand History to see settled cards, each marked Approved or Closed without executing, with links back to the message, run or conversation it came from.
Undo an action
Section titled “Undo an action”When the co-pilot runs an action without a card, the conversation shows a line such as Created, Updated or Completed task with an Undo button. An applied change-set row has its own Undo. Undo puts the item back as it was and marks the line Undone.
Undo covers records (create, update, delete, restore and bulk delete), tasks (create, update, complete) and notes (update, delete). Anything else the co-pilot does, including linking, merging, tagging and file changes, has no Undo. A note can only be undone by the person who wrote it.
Undo is refused when someone edited the record after the co-pilot did. You see “Couldn’t revert. It changed since the AI touched it” and the later edit stays.
How the permission tier decides what asks first
Section titled “How the permission tier decides what asks first”An admin sets a tier for each AI specialist under Admin, on the AI Permissions tab:
- Read-only: the co-pilot only reads data.
- Review: every write shows you a card first.
- Auto-write: writes run directly; deletes still show a card.
- Full: writes and deletes run without a card.
A specialist with no tier set is Read-only. Team changes, merges and calendar invites always show a card, and email always waits for Send. Your own notification and AI preference settings change without a card at every tier above Read-only. Members never get the manager or admin tools, and managers never get the admin tools.