Flowchartio
Sign inTry it freeTry free

Process mapping

Customer onboarding flowchart: a worked example

A typical customer onboarding flowchart has four owners (customer, sales, back office, system), a loop that sends incomplete applications back to the customer, a KYC check with a rejection branch, and an automated account creation followed by a welcome message.

By Flowchartio · Updated · 2 min read

The process in words

"A customer submits an application. Sales reviews it. If information is missing, the application goes back to the customer. Otherwise the back office runs the KYC check. If the check fails, the application is rejected and the customer is informed. If it passes, the system creates the account and sends a welcome email."

That paragraph contains everything the chart needs: four owners, two decisions and three outcomes.

Owners (lanes)

  • Customer: submits the application and completes missing information.
  • Sales: reviews completeness.
  • Back office: performs the KYC (know your customer) check.
  • System: creates the account and sends the email.

In a swimlane diagram, each becomes a column.

Steps and decisions

  1. Start: application received.
  2. Customer: submit application.
  3. Sales: review application.
  4. Decision: is the application complete? No → back to step 2, Yes → continue.
  5. Back office: run KYC check.
  6. Decision: KYC passed? No → reject application → inform customer → end. Yes → continue.
  7. System: create account (automated step).
  8. System: send welcome email (automated step).
  9. End: customer onboarded.

The loop needs an exit

As drawn above, an incomplete application can bounce between customer and sales forever. In practice there is a limit: "If the customer has not completed the application within 14 days, close it." Add a delay step and a second exit, as explained in decisions and loops.

Automated steps and APIs

Steps 7 and 8 are done by software. If you have an API specification, each can be linked to the endpoint that performs it, for example POST /accounts and POST /emails. That turns the chart into documentation developers can use, which is the subject of documenting an API workflow.

Where onboarding slows down

On real maps, the slowest points are usually:

  • the hand-off from sales to back office (queues, unclear priority),
  • the missing-information loop (vague requests to the customer),
  • manual re-entry of data between tools.

These are typical targets for process improvement.

Build your own version

Copy the paragraph at the top, replace the roles and rules with yours, and paste it into Flowchartio: you get this chart with your own lanes in seconds, then refine it in conversation. Generate your onboarding flowchart.

Turn your process into a flowchart

Describe it in a few sentences. Flowchartio draws the flowchart, then you refine it in conversation.

Generate a flowchart