--- title: "Auto-Draft a Follow-Up When a Deal Stage Changes" url: https://www.insulin.dev/blog/crm-trigger-draft-reply-and-offer/ canonical: https://www.insulin.dev/blog/crm-trigger-draft-reply-and-offer/ type: Blog description: "Wire a Salesforce stage change to a voice-matched follow-up and a staged private offer — with an approval gate so nothing sends until you say so." --- # Auto-Draft a Follow-Up When a Deal Stage Changes > Canonical HTML version: https://www.insulin.dev/blog/crm-trigger-draft-reply-and-offer/ 1. [Home](/) 2. / 3. [Blog](/blog/) 4. / 5. Auto-Draft a Follow-Up When a Deal Stage Changes # Auto-Draft a Follow-Up When a Deal Stage Changes Wire a Salesforce stage change to a voice-matched follow-up and a staged private offer — with an approval gate so nothing sends until you say so. ![Max Ma](/authors/max-ma.jpg) Max Ma Aug 18, 2026 ![Auto-Draft a Follow-Up When a Deal Stage Changes](/images/blog/crm-trigger-draft-reply-and-offer/hero.png) Explore AI Summary [![](/logos/company/openai.svg)](https://chat.openai.com/?q=Read%20and%20summarize%20https%3A%2F%2Fwww.insulin.dev%2Fblog%2Fcrm-trigger-draft-reply-and-offer%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Inbox%20App%2C%20Automation. "Summarize with ChatGPT")[![](/logos/company/anthropic.svg) ](https://claude.ai/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.insulin.dev%2Fblog%2Fcrm-trigger-draft-reply-and-offer%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Inbox%20App%2C%20Automation. "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%2Fcrm-trigger-draft-reply-and-offer%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Inbox%20App%2C%20Automation. "Summarize with Gemini")[](https://www.perplexity.ai/search/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.insulin.dev%2Fblog%2Fcrm-trigger-draft-reply-and-offer%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Inbox%20App%2C%20Automation. "Summarize with Perplexity") Table of Contents - [What “a CRM trigger” actually means here](#what-a-crm-trigger-actually-means-here) - [You describe it in plain English; Insulin builds the rule](#you-describe-it-in-plain-english-insulin-builds-the-rule) - [The reply is drafted in your voice, not a template](#the-reply-is-drafted-in-your-voice-not-a-template) - [The private offer is created as a draft, not fired live](#the-private-offer-is-created-as-a-draft-not-fired-live) - [The approval gate: nothing sends until you say so](#the-approval-gate-nothing-sends-until-you-say-so) - [Frequently asked questions](#frequently-asked-questions) - [Takeaways](#takeaways) _A CRM stage change is a signal that a person should do something next. This is how to wire that signal to a drafted, voice-matched reply and a staged private offer — with an approval gate so nothing reaches a contact or your CRM until you approve it._ * * * The moment a deal moves to Proposal, three things should happen and usually one of them doesn’t. The rep should send a follow-up. Someone should spin up a private offer with the right dates. And the CRM should reflect both. In practice the stage flips, the rep is in another meeting, and the follow-up lands two days late — if it lands at all. The stage change already happened. The system already knows. What’s missing is the boring middle step between _the deal moved_ and _the customer heard from us_ — and that middle step has a fixed shape every single time. Fixed-shape work triggered by an event is exactly what you hand to a rule instead of a person’s to-do list. * * * ## **What “a CRM trigger” actually means here** A CRM trigger is a change in your CRM — a Salesforce opportunity moving to a new stage, a HubSpot deal advancing — that Insulin’s [Inbox App](/inbox-app/) watches for and reacts to. You don’t poll for it or check a dashboard. When the event fires, the rule fires. The Inbox App documents this directly: it reacts to opportunity stage changes in Salesforce and deal movements in HubSpot, then produces the next action. So the thing that starts the chain isn’t you noticing the deal moved. It’s the deal moving. Two things worth saying plainly. **Salesforce and HubSpot triggers are available today, with Microsoft Dynamics 365 coming soon** — so if you’re on Dynamics, this is a “soon,” not a “now.” And the trigger is one specific event, not a vague “when something changes.” You pick the CRM, the object, and the condition that matters. * * * ## **You describe it in plain English; Insulin builds the rule** You do not write code or wire a workflow builder. You say what should happen in a sentence, and Insulin turns it into a structured rule. The Inbox App page puts the example in exactly the terms you’d say it out loud: _“when a Salesforce stage changes to Proposal, draft a follow-up and create a private offer” — and Insulin turns it into a structured rule, powered by the same Jobs and Agents that run the rest of Insulin._ That last clause matters. This isn’t a bolted-on email macro. The rule runs on the same [Jobs](/jobs/) engine that runs Insulin’s scheduled work and the same [Agents](/agents/) that do reasoning and grounded drafting everywhere else in the product. A rule is just an _event-triggered_ job with an agent doing the work — so it inherits the same drafting quality, the same access to your context, and the same execution history as everything else you run. Under the hood the plain-English sentence becomes a few concrete fields: the **trigger** (Salesforce — opportunity stage changed), the **stage** to match (Proposal), optional conditions like a minimum amount, and the **context sources** the agent reads before it drafts. You said one sentence. Insulin filled in the structure. * * * ## **The reply is drafted in your voice, not a template** The follow-up isn’t a mail-merge template with the deal name slotted in. Insulin drafts it in your voice — your greeting, your sign-off, your usual openers and closers — learned automatically from your recent emails, so the draft reads like you wrote it rather than a bot. That’s the difference between automation people trust and automation people quietly turn off. A generic templated blast gets caught and resented. A draft that sounds like the rep, grounded in the actual deal context, is one the rep is happy to approve and send as-is. The point of the rule is not to remove the rep’s voice from the follow-up. It’s to remove the ten minutes of writing it while keeping the voice. * * * ## **The private offer is created as a draft, not fired live** Alongside the reply, the rule can stage a CRM-side action — a private offer with the right dates, or a field update. Crucially, it _stages_ it. The Inbox App is explicit that it “stages CRM actions like offer creation or field updates — all routed through Approvals before anything sends.” So the offer shows up as a draft you can inspect: the partner, the dates, the amount, the CRM record it will attach to. Nothing is live. Nothing has been sent to the customer or written to Salesforce yet. You’re looking at a proposal for what the automation _would_ do, with every value visible. This is the whole reason a CRM trigger is safe to leave running. The event side is automatic; the _consequence_ side is held. * * * ## **The approval gate: nothing sends until you say so** The single rule that makes all of this safe: Insulin never sends on its own. The docs state it flatly — “Insulin never sends email on its own” — and the same holds for CRM writes. Every matched email and every staged CRM action lands in an approvals queue, with the full context attached: the draft reply, the staged offer, the deal it came from, the reason the rule fired. From there you send, edit first, or discard. A reply that doesn’t read right gets fixed. An offer with the wrong dates gets corrected or dropped. Only when you approve does the email reach the contact and the CRM action run — and the Inbox App runs the two together, so the follow-up and the offer go out as one approved step rather than two things you have to remember to line up. The reversible parts — watching, reading, drafting, staging — run unattended. The irreversible part — sending to a customer, writing to your CRM — stays a human decision. That’s the same principle behind [every Insulin action that acts versus asks](/blog/when-the-inbox-app-acts-or-asks/): let the work run, keep the send a choice. * * * ## **Frequently asked questions** **Can Insulin auto-draft a follow-up when a Salesforce deal stage changes?** Yes. The Inbox App watches for a Salesforce opportunity stage change and, when it fires, drafts a follow-up in your voice and can stage a private offer — all held for your approval before anything sends. **Which CRMs can trigger a rule today?** Salesforce and HubSpot triggers are available today, with Microsoft Dynamics 365 coming soon. A trigger is a specific event, like an opportunity moving to a chosen stage — not a vague any-change signal. **Do I need to write code to build the rule?** No. Describe what should happen in one plain-English sentence and Insulin turns it into a structured rule — trigger, match conditions, and context sources — powered by the same Jobs and Agents that run the rest of Insulin. **Does the private offer get created live automatically?** No. Insulin stages CRM actions like offer creation or field updates as drafts. They route through Approvals with every value visible, and only run when you approve — nothing writes to your CRM first. **Will it send the follow-up email without me?** No. Insulin never sends email on its own. Matched replies and staged CRM actions land in an approvals queue where you send, edit, or discard — the email and the offer go out together only once you approve. * * * ## **Takeaways** - A CRM stage change is a trigger. The Inbox App reacts to a Salesforce opportunity stage change or a HubSpot deal movement — you don’t watch a dashboard for it. - Salesforce and HubSpot triggers are available today; Microsoft Dynamics 365 is coming soon. - You describe the rule in one plain-English sentence and Insulin builds the structured version, powered by the same Jobs and Agents that run the rest of the product. - The follow-up is drafted in your voice, and the private offer is staged as a draft — never fired live. - Every reply and CRM action routes through Approvals. Insulin never sends on its own; the send stays your decision. Ready to wire a stage change to a drafted reply and a staged offer? See how the [Inbox App turns a plain-English rule into a CRM automation](/inbox-app/), read the [Insulin Inbox documentation](https://doc.suger.io/insulin/inbox/), or [get a demo](/schedule-demo/). ## Sources Primary sources for the platform rules cited above. Last verified August 18, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure. - [Suger Insulin docs: Inbox](https://doc.suger.io/insulin/inbox/) — The Inbox App reacts to CRM events like a Salesforce opportunity stage change, drafts a reply for review, and never sends email on its own — every action goes through an approval queue first. ### Stay Updated Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.