The Workflow Library

Library / Customer onboarding / customer-onboarding-031

Onboarding completion notice to originating sales rep

Customer onboardingTicketService Hub ProfessionalSimple~20 min to buildFull spec

Outcome. When an onboarding ticket reaches its Completed stage, the sales rep who closed the deal gets a short notification, so the rep knows when to check in on the account or start expansion conversations.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-031
flowchart TD
    A[Ticket pipeline stage = Completed] --> B{Originating Sales Rep known?}
    B -->|No| C[Copy owner from associated deal]
    B -->|Yes| D{Rep known now?}
    C --> D
    D -->|No| E[End, no associated deal]
    D -->|Yes| F[Send internal notification email]
    F --> G[Create check-in task]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when the deal owner (sales) and the ticket owner (customer success) are different people, and the rep otherwise has no visibility into onboarding status once the deal closes.
  • UseUse it when your Onboarding ticket pipeline (see customer-onboarding-005) has a single stage that reliably means finished, for example Completed.
  • SkipDo not use it if the same person owns the deal and runs onboarding, they already know it finished.
  • SkipDo not use it as the customer-facing completion message, that is customer-onboarding-020.
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.4 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.6 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.