The Workflow Library

Library / Customer onboarding / customer-onboarding-023

Executive sponsor introduction email sequence

Customer onboardingContactMarketing Hub ProfessionalSimple~25 min to buildFull spec

Outcome. A new customer's primary contact receives an introduction to their executive sponsor within a few days of becoming a customer, without a rep having to remember to send it manually.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-023
flowchart TD
    A[Lifecycle stage = Customer, Executive Sponsor Name known] --> B[Delay 3 business days]
    B --> C[Send executive sponsor intro email]
    C --> D[Set Executive Sponsor Email Sent Date]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when your company assigns an executive sponsor (a named leader, not the day-to-day CS owner) to new or strategic accounts as a relationship-building practice.
  • UseUse it when the sponsor's name is known and stable enough to reference in an automated email rather than needing a person to pick one per deal.
  • SkipDo not use it if executive sponsors are only assigned to a subset of accounts (large deals, for example), add a filter on deal amount or plan tier so the email only sends where a sponsor actually exists.
  • SkipDo not use it as a substitute for the sales-to-CS handoff itself, see customer-onboarding-001, this fiche is a customer-facing touch, not an internal handoff.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.3 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the customer onboarding pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.