--- title: "AI Email and CRM Automation, With Approval" url: https://www.insulin.dev/blog/ai-email-crm-automation-with-approval/ canonical: https://www.insulin.dev/blog/ai-email-crm-automation-with-approval/ type: Blog description: "How AI can watch your inbox and CRM, draft the reply, stage the matching record update, and hold both in an approval queue until a person says go." --- # AI Email and CRM Automation, With Approval > Canonical HTML version: https://www.insulin.dev/blog/ai-email-crm-automation-with-approval/ 1. [Home](/) 2. / 3. [Blog](/blog/) 4. / 5. AI Email and CRM Automation, With Approval # AI Email and CRM Automation, With Approval The reply and the CRM update are the same piece of work, done twice. How to automate both as one flow that still waits for a person before anything leaves. ![Shirley Guo](/authors/shirley-guo.jpg) Shirley Guo Aug 27, 2026 ![AI Email and CRM Automation, With Approval](/images/blog/ai-email-crm-automation-with-approval/hero.png) Explore AI Summary [![](/logos/company/openai.svg)](https://chat.openai.com/?q=Read%20and%20summarize%20https%3A%2F%2Fwww.insulin.dev%2Fblog%2Fai-email-crm-automation-with-approval%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Inbox%20App%2C%20Integrations. "Summarize with ChatGPT")[![](/logos/company/anthropic.svg) ](https://claude.ai/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.insulin.dev%2Fblog%2Fai-email-crm-automation-with-approval%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Inbox%20App%2C%20Integrations. "Summarize with Claude")[![](/logos/company/gemini.svg)](https://www.google.com/search?udm=50&aep=11&q=Read%20and%20summarize%20https%3A%2F%2Fwww.insulin.dev%2Fblog%2Fai-email-crm-automation-with-approval%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Inbox%20App%2C%20Integrations. "Summarize with Gemini")[](https://www.perplexity.ai/search/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.insulin.dev%2Fblog%2Fai-email-crm-automation-with-approval%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Inbox%20App%2C%20Integrations. "Summarize with Perplexity") Table of Contents - [The shape of the workflow](#the-shape-of-the-workflow) - [By default, nothing leaves without a person](#by-default-nothing-leaves-without-a-person) - [What connects today](#what-connects-today) - [Where to start](#where-to-start) - [Frequently asked questions](#frequently-asked-questions) - [Takeaways](#takeaways) _AI email and CRM automation with approval is a workflow where an assistant monitors your inbox and CRM, drafts the reply and stages the matching record update, then holds both in an approval queue until a person decides on each._ _Corrected September 23, 2026: Microsoft Dynamics 365 works as a CRM trigger and for CRM actions, alongside Salesforce and HubSpot — an earlier version of this post said it had not shipped. The post also now names the one exception to the approval queue: an email rule you set to send automatically._ _Corrected September 27, 2026: a CRM update is staged only by a rule that a CRM event triggers, such as a deal changing stage — an email rule can draft a reply but cannot stage a CRM action — and the reply and the CRM action are approved separately: the reply goes out on **Send**, the CRM action runs on its own **Run in chat**. An earlier version said one approval covered both._ * * * Look at what actually happens when a customer email arrives. Someone reads it, works out what it is about, checks the CRM for context, writes a reply, sends it, and then — sometimes, when there is time — goes back and updates the record. That last clause is where the data quality goes. The reply is urgent and visible; the CRM update is neither. So the email always happens and the record update happens sometimes, and six months later the pipeline report is wrong in ways nobody can reconstruct. The fix is not discipline. It is raising the reply and the record update together, so the update is never left to memory. * * * ## **The shape of the workflow** Six steps, and only the last one needs a person. 1. **Monitor** — the inbox and the CRM are both watched. A reply can start from either side, but a CRM update is staged only by a rule that a CRM event triggers, such as a deal changing stage. 2. **Match** — an incoming message or CRM event is checked against rules you define, so only the relevant ones enter the flow. 3. **Gather** — the assistant pulls the context that a human would have looked up: who this is, what the open records say, what was last discussed. 4. **Draft** — a reply is written [in your voice](/blog/ai-that-writes-in-your-voice/), grounded in that context rather than in a template. 5. **Stage** — the matching CRM action is written as an instruction alongside the draft. Not applied — prepared. 6. **Approve** — both land in the same queue: a person sends or edits the reply, and runs the CRM action separately with **Run in chat**. The staging step is the one that changes the outcome. Because the record update is prepared at the same moment as the reply and waits beside it in the queue, it stops being the thing that gets skipped — even though each still takes its own click. ## **By default, nothing leaves without a person** This is the property that makes the workflow safe to turn on. In Insulin’s [Inbox App](/inbox-app/), matched emails and CRM actions go to Approvals for review, where you can send, edit, or discard before anything reaches a contact or your CRM. The one exception is an email rule you deliberately set to send automatically, which replies without review; CRM actions always wait for a person to run them. So the failure mode of a bad draft is a discarded draft, not an email to a customer. That asymmetry is what lets you start with a broad rule and tighten it, rather than the reverse — and it is why the approval queue is a default rather than a setting you remember to switch on. Where the boundary between acting and asking should sit is covered in [when the Inbox App acts, and when it asks](/blog/when-the-inbox-app-acts-or-asks/). Every action is logged and reviewable afterwards, which matters the first time somebody asks why a particular reply went out. ## **What connects today** Be precise about this before you design around it. Mail comes from **Gmail or Outlook**. CRM monitoring and actions cover **Salesforce, HubSpot, and Microsoft Dynamics 365**. Check the [changelog](/changelog/) for the current state rather than relying on a blog post’s snapshot. ## **Where to start** Pick one narrow, high-volume, low-risk message type. Not “all customer email.” Good first candidates share a shape: they arrive often, the right reply is fairly predictable, and any record update is mechanical. For email rules, that means inbound renewal questions, straightforward support acknowledgements, and inbound interest that needs routing. For the paired reply and record update, start with a deal moving to a stage you name — only a rule a CRM event triggers can stage the update. What does not qualify as a starting point is anything where a wrong reply is expensive — pricing negotiations, escalations, anything legal. Run it with approval on and read every draft for the first week. You are calibrating the rules, and the fastest way to do that is to watch what the assistant matched that you would not have. Setting those rules up is covered in [email rules without code](/blog/email-rules-without-code/); the CRM-triggered version, where a stage change raises both the outreach and the record update, is in [auto-draft a follow-up when a deal stage changes](/blog/crm-trigger-draft-reply-and-offer/). * * * ## Frequently asked questions **What is AI email and CRM automation with approval?** A workflow where an assistant monitors your inbox and CRM, drafts the reply and stages the matching record update, then holds both in an approval queue until a person decides on each. **Can it send email on its own?** Not by default. Matched emails and CRM actions go to Approvals for review, where you send, edit, or discard. The exception is an email rule you set to send automatically, which replies without review; CRM actions always wait for a person. **Which email and CRM systems does it work with?** Gmail or Outlook for mail, and Salesforce, HubSpot, or Microsoft Dynamics 365 for CRM. **Why stage the CRM update with the reply?** Because separately, the reply always happens and the record update happens sometimes. Raising both from the same CRM event puts the update in the queue beside the reply, so it gets decided instead of forgotten. **What should I automate first?** One narrow, high-volume message type where a wrong draft is cheap — renewal questions, routine acknowledgements, inbound routing. Not pricing negotiations or escalations. ## Takeaways - The reply and the CRM update are one piece of work. Automating them separately is why the record update gets skipped. - Staging both from the same CRM event, so the update waits beside the reply, is the step that fixes data quality — not more discipline. - By default nothing reaches a contact or your CRM before a person approves — a bad draft is a discarded draft. - Mail is Gmail or Outlook; CRM is Salesforce, HubSpot, or Microsoft Dynamics 365. - Start with one narrow, high-volume message type where a wrong draft is cheap, and read every draft for the first week. * * * See how the approval queue works in the [Inbox App](/inbox-app/), or [book a demo](/schedule-demo/). ## Sources Primary sources for the platform rules cited above. Last verified August 27, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure. - [Fours docs: Insulin Inbox](https://doc.fours.com/insulin/inbox/) — The connected mail and CRM providers, the approval queue, and the send/edit/discard behaviour described here. ## Keep reading - [IntegrationsEWS Retirement and Your AI Email AssistantOct 8, 2026](/blog/ews-retirement-ai-email-assistant/) - [Inbox AppThe AI Email Assistant for Outlook vs GmailSep 30, 2026](/blog/ai-email-assistant-on-outlook-vs-gmail/) - [Inbox AppAI Email Rule Templates: Exact Text, Word for WordOct 8, 2026](/blog/ai-email-rule-templates/) - [SecurityRead-Only Access for AI Agents: Where It's SetOct 8, 2026](/blog/read-only-access-for-ai-agents/) [Browse every post on the Insulin Blog](/blog/) ### Stay Updated New posts, product updates and marketplace strategy are shared on LinkedIn as they publish. [Follow Fours on LinkedIn](https://www.linkedin.com/company/suger-inc)