The Workflow Library

Library / Customer onboarding / customer-onboarding-006

Round-robin CS owner assignment on deal closed won

Customer onboardingDealSales Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. Every closed-won deal gets a customer success owner the moment it closes, spread evenly across the CS team, with named accounts routed to their existing CSM instead of the rotation pool.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-006
flowchart TD
    A[Deal stage = Closed Won, owner not yet assigned] --> B{Named Account?}
    B -->|Yes| C[Set Onboarding Owner = company's Dedicated CSM]
    B -->|No| D[Rotate record to owner: CS team]
    C --> E[Set CS Owner Assigned Date]
    D --> E
    E --> F[Send internal notification to Onboarding Owner]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when CS owner assignment today is a manual pick, done inconsistently or too late to matter for the handoff.
  • UseUse it when most new customers do not have a pre-existing relationship with a specific CSM, so a fair rotation is the right default.
  • SkipDo not use it if you also need a task and a notification for the handoff itself, add customer-onboarding-001 alongside it, this fiche only sets the owner.
  • SkipDo not use it if onboarding routing should be based on plan tier or deal size, use customer-onboarding-016 or customer-onboarding-039 instead, or combine the branch logic from this fiche with theirs.
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.5 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.