The Workflow Library

Library / Customer onboarding / customer-onboarding-007

Sales-to-CS handoff summary notification with deal context

Customer onboardingDealSales Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. The CS owner gets one email that pulls together everything sales knew about the deal, contract length, stakeholders, special terms, so onboarding starts from full context instead of a Slack message or a scramble to find the rep.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-007
flowchart TD
    A[Deal stage = Closed Won, owner known, summary not sent] --> B[Delay 1 hour]
    B --> C{Amount above threshold?}
    C -->|Yes| D[Notify Onboarding Owner + CS manager]
    C -->|No| E[Notify Onboarding Owner only]
    D --> F[Set Handoff Summary Sent = true]
    E --> F
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when the handoff task from customer-onboarding-001 exists but reps still get pinged for context CS could have had upfront.
  • UseUse it when deal size or complexity varies enough that some handoffs need a manager copied in and some do not.
  • SkipDo not use it as a replacement for customer-onboarding-001, run both, that one creates the accountable task, this one delivers the context.
  • SkipDo not use it if the deal record itself has so few populated fields that a summary email would mostly be blank, fix data entry at the deal stage first.
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.6 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.5 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 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.