A shared inbox like info@ or sales@ may receive questions about opening hours, prices, stock and delivery dates. An AI email assistant is software that reads incoming mail and prepares replies. It may look like an easy way to reduce the team's workload, but consider the connection carefully.

When connecting a tool, decide who approves what goes out, whether it may send on its own and how long it keeps copies of your customers' mail. This article explains AI email assistant settings in plain terms, so you can check them in the consent screen, the window where you grant the app permissions, and in the tool's own settings before you connect anything.

What you are actually approving when you connect a mailbox

Microsoft's permissions window lists the permissions an app requests before you approve the connection.³

Read the requested permissions carefully, because they can give access to the whole mailbox: once approved, they cover the mailbox, not one folder or one conversation.² Depending on what you agree to, the assistant may be able to read, draft, send and sort email.²

Think about your shared info@ inbox. It holds price questions, but it may also hold correspondence with a supplier about a disputed invoice, a job candidate's CV and a customer complaint with a phone number and home address. An assistant we build only reaches the tools and data its task needs, such as the customer questions that arrive every day.¹

Work accounts may behave differently. On work accounts, an IT administrator may stop users from granting permissions to outside apps themselves, or require administrator approval.³ Do not try to get around this. It gives you a second check.

Setting one: can it send, or only draft?

We can design an assistant to prepare drafts for review, and we agree with you which actions need approval and which can happen automatically.¹ A draft stays in your drafts folder until a person opens it. A sent message has already reached the customer.

An app with Mail.Send may send messages on behalf of the user who is signed in to the account.³ In the assistants we build, anything that leaves the business can wait for a person to approve it.¹

Tools handle this in different ways. These are examples, not recommendations:

  • Mailopoly MCP uses separate grants for reading, writing and sending,⁴ and it can send through a connected address only when it has the send permission.⁴
  • Mailopoly says its Poly assistant sends nothing without the user's involvement.⁴
  • Inbox Zero marks emails that need an answer and puts a draft reply in the drafts folder.⁵
  • Fyxer puts its replies in drafts for the user to review and says it does not send them automatically.⁶
  • OpenClaw works differently: once it is connected to email and other tools, it can send messages without a person confirming each step.⁷

Check those descriptions against the permissions window, not just the sales page. If the window asks for permission to send and the tool claims to be draft-only, ask the vendor why.

Draft-only setups are usually lower risk than automatic sending, because a person reviews each message before it leaves the mailbox.³ For a shared inbox, start with draft-only. Later, you can allow automatic sending for one specific, everyday task. A wrong price that has already gone out is much harder to correct.

Setting two: who approves a draft before it goes out

A draft is only safe if someone actually checks it. With a shared inbox, it is easy for everyone to assume someone else did. Tool settings alone are not enough: your team also needs to agree who checks the drafts and who handles non-standard cases.

One practical guide says that for high-priority messages, the assistant can draft the reply, but you should review and send it yourself.⁷ The same source advises keeping approval switched on before any email goes to a client.⁷ For risky work such as sending email, it recommends approval steps, limited permissions and activity logs.⁷ We make the assistant's runs traceable, so you can check later what it did.¹

Workflow · Shared inbox enquiry to a reply a person has approved
  1. Trigger

    Enquiry arrives in the shared inbox

    A customer email or a forwarded WhatsApp question arrives in info@.

  2. Prepared by the system

    Draft prepared in the drafts folder

    The system drafts a reply from the price list and service details. It has no permission to send.

  3. Checked by a person

    Named person checks the draft

    The assigned team member corrects facts and tone, then approves or rewrites the draft.

  4. Checked by a person

    Non-standard cases go to the responsible person

    A responsible person handles complaints, discount requests and unclear cases, and decides how to reply.

  5. Result

    Reply sent by a person

    A person sends the approved reply from the mailbox, and the activity log records what was drafted and who sent it.

An email assistant only sees what reaches the inbox. Decide how orders from other channels will reach the workflow, and apply the same approval rule.

These things still wait for a person: every reply a customer sees, anything about money or a complaint, and any case where you are not sure the facts in the draft are correct. The system can write the text from your price list. It cannot know that you promised this customer a discount on the phone last week.

If you also want order details copied into a spreadsheet, treat that as a separate step and check which access rights that step needs. Have a person check each row before anyone acts on it.

Write down the routine before you give the tool more access. Teams are advised to agree on a clear workflow and approval process before expanding automation across customer-facing campaigns.⁶ For more detail, see our article on building AI workflows with human review.

Setting three: what it keeps and for how long

Check whether the tool keeps copies of your email and, if so, for how long. Check the tool's retention settings before approving access. Look in the tool's settings or privacy policy, or ask the vendor.

Start with one question: does the tool store your email, or only process it to write the draft?³ Vendors describe different retention practices.⁴,⁸ For example, MailMates says it processes emails in real time and does not keep them.⁸ Mailopoly says it keeps data for 30 days after an account is deleted and then destroys it.⁴ Fyxer says email data is not used to train external AI models.⁶

Next, if the assistant remembers details from your mail to improve later drafts, it should let you see what it remembered and delete it.² If the tool has no screen for this, ask the vendor how to clear that memory.

Also check how much of each email the tool reads. The MailMates listing says it reads the full thread, not only the last message, when it writes a draft.⁸ The same listing says it handles personal communications and personally identifiable information.⁸ In a shared inbox, one thread can include names, phone numbers, delivery addresses and details of a customer's problem. That is personal data, and your business is still responsible for where it goes.

What revoking access does and does not undo

When a test goes badly, the natural reaction is to revoke the app's access and consider the problem solved. Revoking Microsoft access may not delete email content the app already processed or stored.³

Warning

Revoking Microsoft access may not delete email content the app already processed or stored.[³](https://flymail.ai/app/outlook-ai-email-app-permissions) Revoking an app's Microsoft access may not delete email content it has already processed or stored.[³](https://flymail.ai/app/outlook-ai-email-app-permissions) Google's note on revoking access says nothing about what the app has already copied, so check the tool's own deletion settings too.[²](https://getequerry.app/guides/ai-email-assistant)

Work accounts have a second limit. If an administrator approved an app for you in a Microsoft work or school account, you cannot revoke those permissions yourself.² Agree in advance who can revoke a connection's access, and write that name next to the name of the person who approves drafts.

A short check of AI email assistant settings before you connect

Run through this check before anyone clicks Allow. One general recommendation is to review permissions, retention settings, excluded contacts and internal data policies before you connect a mailbox with sensitive content.⁶

Read the permissions window carefully

Read every permission on the list. If someone else manages your work accounts, ask them first, because they may need to approve the app.³ If you use a browser extension, a small add-on installed in Chrome or another browser, such as Mailmeteor, review its permissions before switching on features that reach the whole mailbox.⁶

Leave sending switched off

Approve draft-only access at first. If the tool cannot work without permission to send, make a deliberate decision about that rather than accepting it by default.

Start with one folder

Begin with read-only access to a single label or folder and low-stakes messages, then give the tool more access later.⁷ Questions about opening hours are a good place to start. Complaints are not.

Name the people

Write down who checks drafts, who handles complaints and discounts, and who can revoke the tool's access.

Get retention answers in writing

Ask the vendor about storage, memory, training and how long it keeps data after you close your account. Ask about running costs too: whether the price is per user, whether a shared inbox counts as a user, and what changes after the trial. The other cost is the time your named person spends checking drafts.

Specify which emails the tool must not process

Decide which senders the tool must leave alone, such as payroll, legal or medical correspondence, and check that this matches your own data rules.

Test in your customers' languages

Run a test week with real enquiries in Latvian, Lithuanian, Estonian, Russian and English. Compare the drafts with what your team would have written, and check grammar and tone separately in each language. A tool that writes good English may still get Latvian order details, product names or dates wrong. So judge whether the tool fits by the results of the test in your own business.

Set aside time to read the permission screens, ask questions and check drafts. If you are still deciding which task to hand over first, read how to choose your first AI automation. You can also see our approach to working with clients. Consider a setup that prepares drafts in your existing mailbox, has a named teammate approve them, and leaves sending to a person unless you choose otherwise.

Frequently Asked Questions

Can an AI email assistant send emails without anyone approving them?

It depends on the permissions you approve: a connected assistant may be able to read, draft, send and sort email.² An app with Mail.Send may send messages on behalf of the user who is signed in to the account,³ and OpenClaw, once connected to email and other tools, can send messages without requiring manual input at every step.⁷ Inbox Zero and Fyxer put reply drafts in the drafts folder;⁵,⁶ Fyxer and Poly say they do not send drafted emails automatically or without the user's involvement.⁴,⁶ Draft-only setups are usually lower risk, because a person reviews each message before it goes out.³

Does revoking an app's access delete the email data it already has?

No. Revoking Microsoft access may not delete email content the app already stored.³ Revoking Microsoft access may not delete content that the app has already processed or stored.³ Google's note on revoking access also says nothing about what the app already copied.² Check the tool's own deletion settings and ask how long it keeps data after you close your account. Mailopoly says it retains data for 30 days after account deletion.⁴

Why can't I revoke an app's permissions on my work Microsoft account?

If an administrator consented to the permissions for you in a Microsoft work or school account, you cannot revoke them yourself.² Whoever manages your accounts may also block outside apps or require administrator approval for work accounts.³ Agree with that person, whether a contractor or someone on your team, on who approves new mailbox connections and who can revoke their access.

Should the assistant get access to the whole shared inbox from day one?

No. Approved permission usually covers the whole mailbox, not one folder or thread.² One guide suggests starting with read-only access, a single label or folder and low-stakes messages.⁷ Agree on a clear workflow and approval process before expanding automation across customer-facing campaigns.⁶

Sources (8)

Have a process you'd like to talk through?

Book a call (opens in a new tab)