Auto-Draft a Follow-Up When a Deal Stage Changes

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.

Corrected September 27, 2026: Microsoft Dynamics 365 triggers were already available when this post was published — an earlier version listed them as coming soon, and a September 19 note said they had become available since.

Corrected September 27, 2026: a staged CRM action is a written instruction that waits behind its own Run in chat button, not a pre-filled offer with its values shown, and the reply and the CRM action are approved separately — the reply on Send, the action on Run in chat. An earlier version said the two went out together as one approved step.

---

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 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, HubSpot, and Microsoft Dynamics 365 can all trigger a rule — though Dynamics reports a won deal and a lost deal as the same Close stage, so a rule there can’t tell the two apart. 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 engine that runs Insulin’s scheduled work and the same 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 staged as an instruction, not fired live

Alongside the reply, the rule can stage a CRM-side action — an instruction to create a private offer, or to update a field. Crucially, it stages it. The Inbox App is explicit that it “stages CRM actions like offer creation or field updates,” and every CRM action waits in Approvals for a person to run it.

So what shows up in the queue is the instruction itself — for example, create a private offer for this opportunity — in its own block with a Run in chat button. Nothing is live. No offer exists yet, and nothing has been sent to the customer or written to Salesforce. When you click Run in chat, the agent carries out the instruction in the Inbox chat rail, limited to the CRM connection the action came from, and you watch it run.

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 unless you have written an auto-send rule, and a rule fired by a CRM event cannot auto-send. The docs state it flatly — “Insulin never sends email on its own” — and the same holds for CRM writes.

Every email this rule drafts and every staged CRM action lands in the Approvals queue — the draft reply and, beside it, the CRM action’s instruction. From there you decide each on its own. The reply reaches the contact only when you press Send and confirm; a reply that doesn’t read right gets edited first. The CRM action runs only when you click Run in chat. Because both come from the same event and wait side by side, the follow-up and the offer get decided together instead of being 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 when the Inbox App acts and when it 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, HubSpot, and Microsoft Dynamics 365 triggers are all available. 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 written instructions. Each waits in Approvals behind a Run in chat button and runs only when you click it — nothing writes to your CRM first.

Will it send the follow-up email without me? No. A rule fired by a CRM event cannot auto-send, so its draft and its staged CRM action both wait in the Approvals queue: the email goes out when you send it, and the offer action runs when you click Run in chat.

---

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, HubSpot, and Microsoft Dynamics 365 triggers are all available; on Dynamics, a won deal and a lost deal arrive as the same Close stage.
• 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 an instruction — never fired live.
• Every reply and CRM action this rule produces routes through Approvals: a rule fired by a CRM event cannot auto-send, so 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, read the Insulin Inbox documentation, or get a demo.