Customer Onboarding & Sales Handoff Workflow
Three-lane onboarding workflow where the sales team hands the closed deal to the onboarding specialist, who runs the kickoff and setup tasks with the customer.
Five-lane customer onboarding workflow spanning sales, legal, finance, onboarding and the customer, with acceptance gates and a 30-day check-in before activation.
Copy and paste the following FlowZap code into a project in your FlowZap account to see this template diagram.
sales { # sales
n1: circle label:"Lead Qualified"
n2: rectangle label:"Initial Contact"
n3: rectangle label:"Discovery Call"
n4: diamond label:"Good Fit?"
n5: rectangle label:"Prepare Proposal"
n6: rectangle label:"Present Proposal"
n7: diamond label:"Accepted?"
n8: rectangle label:"Send Contract"
n9: circle label:"Deal Lost"
n1.handle(right) -> n2.handle(left)
n2.handle(right) -> n3.handle(left)
n3.handle(right) -> n4.handle(left)
n4.handle(right) -> n5.handle(left) [label="Yes"]
n5.handle(right) -> n6.handle(left)
n6.handle(right) -> n7.handle(left)
n7.handle(right) -> n8.handle(left) [label="Yes"]
n8.handle(bottom) -> legal.n10.handle(top) [label="Review"]
n7.handle(top) -> n9.handle(top) [label="No"]
n4.handle(top) -> n9.handle(top) [label="No"]
}
legal { # legal
n10: rectangle label:"Contract Review"
n11: diamond label:"Terms OK?"
n12: rectangle label:"Request Changes"
n13: rectangle label:"Finalize Contract"
n14: rectangle label:"Contract Signed"
n10.handle(right) -> n11.handle(left)
n12.handle(top) -> sales.n6.handle(bottom) [label="Negotiate"]
n13.handle(right) -> n14.handle(left)
n14.handle(bottom) -> finance.n15.handle(top) [label="Process"]
n11.handle(bottom) -> n13.handle(bottom) [label="Yes"]
n11.handle(right) -> n12.handle(left) [label="No"]
}
finance { # finance
n15: rectangle label:"Setup Billing"
n16: rectangle label:"Process Payment"
n17: diamond label:"Payment OK?"
n18: rectangle label:"Payment Issue"
n19: rectangle label:"Account Active"
n15.handle(right) -> n16.handle(left)
n16.handle(right) -> n17.handle(left)
n19.handle(bottom) -> operations.n20.handle(top) [label="Activate"]
n17.handle(top) -> n19.handle(top) [label="Yes"]
n18.handle(bottom) -> n16.handle(bottom) [label="Retry"]
n17.handle(right) -> n18.handle(left) [label="No"]
}
operations { # operations
n20: rectangle label:"Create Account"
n21: rectangle label:"Setup Environment"
n22: rectangle label:"Configure Settings"
n23: rectangle label:"Assign Team"
n24: rectangle label:"Schedule Training"
n20.handle(right) -> n21.handle(left)
n21.handle(right) -> n22.handle(left)
n22.handle(right) -> n23.handle(left)
n23.handle(right) -> n24.handle(left)
n24.handle(bottom) -> customersuccess.n25.handle(top) [label="Handoff"]
}
customersuccess { # customersuccess
n25: rectangle label:"Welcome Call"
n26: rectangle label:"Product Training"
n27: rectangle label:"Implementation Support"
n28: diamond label:"Ready to Launch?"
n29: rectangle label:"Additional Training"
n30: rectangle label:"Go Live"
n31: rectangle label:"30-Day Check-in"
n32: circle label:"Onboarding Complete"
n25.handle(right) -> n26.handle(left)
n26.handle(right) -> n27.handle(left)
n27.handle(right) -> n28.handle(left)
n28.handle(right) -> n30.handle(left) [label="Yes"]
n30.handle(right) -> n31.handle(left)
n31.handle(right) -> n32.handle(left)
n28.handle(top) -> n29.handle(top) [label="No"]
n29.handle(bottom) -> n27.handle(bottom) [label="Continue"]
}
Install the MCP packagenpm install -g flowzap-mcpMCP documentation
Three-lane onboarding workflow where the sales team hands the closed deal to the onboarding specialist, who runs the kickoff and setup tasks with the customer.
Incident response workflow that documents the current state, traces the root cause, validates controls and creates a prevention protocol before the case is closed.
Work assignment workflow that names an accountable owner, checks for blockers, escalates to the manager and confirms the assignment with everyone involved.
Handoff workflow with a completeness gate: the handoff checklist must be fully met before the receiving team approves and work moves forward.
Customer support workflow that applies the standard greeting and service protocol, then escalates to tier 2 when the standard path cannot resolve the request.
Knowledge capture workflow: document the current process steps, write the step-by-step guide, get it approved and track onboarding to completion.