Skip to content
Console(opens in a new tab)

Building a compliant customer onboarding flow

Every onboarding flow begins with a set of questions:

  • How does a prospect apply to become a customer?
  • What information must a prospect provide?
  • What checks must be performed on a prospect before they can become a live customer?
  • Under what conditions should a prospect automatically pass these checks, vs. be routed to human review to gather further information before they can be approved as a customer?

These requirements must balance compliance and regulatory requirements, with the user experience and friction of an onboarding flow.

For example, you might have a “Sign Up” page on your website, which leads a new prospect to fill in an application form to become a customer. This is the first stage in the onboarding flow.

In order to check whether a prospect meets your criteria to become a customer, you will first need to collect information from them. At minimum this will include some basic identity and contact information for the prospect and person applying, such as:

  • Business name
  • Business address
  • Person applying on behalf of the business

You may also want to collect other information to help route the prospect to the correct internal sales or customer team, or to better identify the business and personalize further product offerings.

You will need to decide which fields are required vs. optional during the first stage of your onboarding flow.

Information Purpose Required status for initial application page
Business name Identity, Verification checks Required
Business address Identity, Verification checks Required
Person name Identity, Verification checks, Contact details Required
Person email Identity, Contact details Required
Annual revenue GTM territory assignment, personalizing offers Optional
Industry GTM territory assignment, personalizing offers Optional
Business website Identity, personalizing offers Optional
Articles of Incorporation Regulatory requirements Optional

Now that you have collected information from the prospect, you must they meet the criteria you have for all new customers. For example, you might need to verify that:

  1. The business name is correct and is how they are legally recognized by the government
  2. The business is verified at the address they applied with
  3. The business has an active secretary of state registration
  4. The person applying on behalf of the business is verified as being linked to that business

Designing the workflow and decision process

Section titled “Designing the workflow and decision process”

Now that you have your requirements and have laid out what information needs to be collected from customers, you need to determine the decisions you will make during the onboarding flow, depending on the information you get and the outcome of the verification checks.

For example:

An example onboarding decision flowA customer visits the sign-up page, fills in the form and provides the required information, and four verification checks run: business name matches legal name, business address is correct, active registration where the business operates, and person name is linked to the business. If all four pass, the customer is approved, routed to the relevant customer team, and onboarding starts. If any check fails, the applicant is routed to manual review, where a person either confirms the requirements are met and approves them, or emails them for additional information and awaits their response.Customer visits “Sign Up” pageCustomer fills in form,provides required informationRun verification checks1. Business name matches legal name (govt records)2. Business address is correct3. Active registration where business operates4. Person name is linked to the businessAll 4 checkspass?Route applicant to manual reviewApprove as customerHuman confirmsrequirements met?Route to relevant customer teamInitiate onboarding(e.g. welcome email)Onboarding startedEmail applicant requestingadditional informationAwait applicant responseNo: any failsYes: all passYesNo / more info needed

Now that you have collected the data, listed your requirements, and built the workflow and decision process, you are ready to integrate with Enigma’s KYB API to automate the checks and optimize your onboarding flow.

In the example above, Enigma’s KYB API is integrated into the “Run Verification Checks” stage.

  • Inputs: Provide the business name, address, person as inputs in the request to Enigma’s KYB API.
  • Outputs: Check the results of the relevant verification tasks in Enigma’s response to confirm whether the applicant is auto-approved, auto-rejected or routed to manual review.
Business Requirement Enigma Verification Task Required outcome
Provided business name matches the legal name for the business (on the registration) sos_name_verification SUCCESS
Provided business address is verified as an address for this business address_verification SUCCESS
Provided person name is verified as being linked to this business person_verification SUCCESS
Business has an active registration in the states in which they operate domestic_registration SUCCESS

Enigma’s KYB API is also integrated into the manual review portion of the workflow:

  1. The data portion of Enigma’s KYB API response body shows further context Enigma has about the matched business, providing additional information to support manual review.
  2. If further information is needed during manual review, Enigma’s KYB API also supports add-on attributes and tasks such as returning business reviews, screening for negative news or checking whether the business has ever filed for bankruptcy.