Define Customer Onboarding Before Automating It
Build and validate a SIPOC that makes the unit, boundary, supplier-input links, customer requirements and next analysis explicit.
22 minutes
Scenario
A B2B software company wants an AI agent to automate customer onboarding. Sales, Finance, Implementation and customers use different start and end events, and 38% of provisioning requests arrive without validated integration settings.
- Your role
- Process analyst preparing the automation boundary
- Method
- SIPOC
Evidence pack
Sales start
Sales measures from verbal agreement.
Finance gate
Provisioning cannot begin until billing status is verified.
Request quality
Thirty-eight percent of requests lack validated integration settings.
Customer outcome
Customers consider onboarding complete after authorised users perform the first core task.
Support dependency
Support needs an access and exception record for every workspace.
Evidence
Event logs contain signed-order, billing-verification, provisioning and first-use timestamps.
Constraints
- Use observable state changes, not department names, for the boundary.
- Keep the process to four to seven major steps.
- Do not select an automation before validating the SIPOC.
Case steps
Work through each prompt using the evidence pack. These guided cases support self-directed practice; server-scored attempts are not available yet.
Define the unit of work, purpose, observable start and observable end.
Create four to seven major steps and link critical outputs to customers and requirements.
Connect required inputs to suppliers and identify the boundary weakness.
Validate one normal and one exception case, then select the next method and owner.