An email step in the sales process can now be excused, not only sent

Microsoft Dynamics 365 CRM

Every step in the sales process raises a piece of work, and declining a task with a reason has always marked its step excused so the process moves on. An email step had no such route. A rep who judged the email unnecessary had to send something anyway or tick the record by hand. Two […]

In this series · Part 15 of 27

1Dynamics 365 CRM: API integration + change-control repo2Dynamics 365 CRM: Last Contact Engagement tracking on Accounts3Turning a sales-intelligence export into a clean CRM data model4Dynamics 365 CRM: contacts inherit their company’s website, and emails timestamp by send time5Your SEO health now lives as a dashboard inside the CRM6Contact form duplicate detection now reads the request, not just the address7Marketing list members now show engagement and account fit8Campaign responses now create leads behind a confirmation step9Three CRM automations passed their tests without running the code that had just changed10A signature defect that three mailboxes agreed was not there11Why a corrected email signature kept sending the old one12A read-only CRM endpoint for scoring outside the desktop13Choosing what runs the AI layer in the CRM sales process14Asking whether a partner is involved, instead of inferring it15An email step in the sales process can now be excused, not only sent16The rehearsal that guards every process change had been failing silently17A one to one email from a lead left the engagement record blank18Two local dependencies, and only one was obvious19Filing a generated document to the record automatically20One meeting that served two process steps, recorded as two21A setting that stored correctly, read back correctly, and was never in force22Generating a product catalogue from one canonical file23Three date fields that existed on every row, and had never once been written24Unused, unreferenced, and still not safe to delete25A measure that could not record early26A sales automation that runs as itself, not as an administrator27A stage change that was refused, and reported as a success

On this page

Free Revenue Lifecycle Assessment

Connect with Marissa Wright to receive a free Revenue Lifecycle Assessment Report on your own business.

Book a consult →

Every step in the sales process raises a piece of work, and declining a task with a reason has always marked its step excused so the process moves on. An email step had no such route. A rep who judged the email unnecessary had to send something anyway or tick the record by hand.

  • Two fields were added to the email record, an acceptance status that defaults to yes and a reason for decline, mirroring what tasks already carry.
  • A new automation watches for an email cancelled with the status set to no and a reason written, and ticks the step exactly as a sent email would. A cancel on its own, or a decline with no reason, excuses nothing, so duplicates and mistakes stay harmless.
  • It was proven on a throwaway test record with three cases before anything real touched it. The reasoned decline ticked the step and both negatives held.
  • The rehearsal that gates every process change gained a check it was missing, the path where a partner coordination call is correctly not raised. Running it also exposed two checks that had gone stale when a rule changed the day before, and both were corrected.

Other Posts