A one to one email from a lead left the engagement record blank

Microsoft Dynamics 365 CRM

Every contact and account carries a last engagement date and type, stamped by three small automations whenever an email, a call or a meeting completes. A reframe email sent one to one from a lead had stamped nothing, and the reason was structural rather than a bug. The automations only recognised an activity filed against […]

In this series · Part 17 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 contact and account carries a last engagement date and type, stamped by three small automations whenever an email, a call or a meeting completes. A reframe email sent one to one from a lead had stamped nothing, and the reason was structural rather than a bug.

  • The automations only recognised an activity filed against a contact or an account. An activity filed against a lead, which is where early conversations live, fell through both branches and the record stayed silent.
  • Each of the three now looks up the lead's parent contact and account and stamps both. All three were proven on throwaway test records before the change went live, and the one real gap was filled by hand.
  • The same session added a yes or no flag on every contact showing whether they are the primary contact for their account, kept true by two automations and set correctly across 255 existing contacts.
  • The twelve month nurturing email series was rebuilt on the one email structure now used everywhere, with months two to twelve created as shells ready for their text.

Other Posts