Introduction

Electronic Know Your Customer (eKYC) is the most preferred way for FinTechs companies to verify customers and it is often mandated by regulatory bodies. However, the eKYC process can often be lengthy and need users to submit details that are not readily available to them. This is one of the most common yet difficult situations to handle for marketers especially with the current short span of attention of the digital users. We can set up Flows aimed at bringing the customers back to the app and nudging them to complete the KYC. This can help in higher conversion rates and thus help us avoid losing new users and revenue.

Generally, eKYC applications have two stages: filling personal information and uploading relevant documents. In this article, we will create a Flow campaign to nudge users to complete their eKYC process, depending on the stage they dropped off.

Expected Result

Users receive a Push Notification on their phone to complete their KYC:

Create a Flow

In this section, let us create a Flow to nudge your customers to complete their eKYC process.

Add Flow Details

1. Navigate to Engage > Flows and click + Create Flow or navigate to the sidebar, click + Create new, and then click Flow.
2. Click + Start with a blank canvas to start building your flow for the use case. You are taken to the first step “Details and goals”.
3. Enter the following details:
   
   • Flow name: Enter a flow name. For example, "eKYC Abandonment Journey".
   • Flow tags: Select the required flow tags.
4. Under the Conversion goal section, turn the Exit on conversion toggle on to exit users who convert by doing the event “eKYC Submitted”. This is your primary conversion goal, which triggers when a user submits their eKYC.
   
5. Click Next to move the second step “When will users enter the flow”. This step helps you define when to allow the user by mentioning the trigger conditions. For our example, the event can be “eKYC Started”.
6. Under Users enter the flow section, select On event trigger.
7. In the IF user section, select the event “eKYC Started” which gets triggered when a user starts their eKYC process.
8. In the THEN enter the user section, select the Immediately option.
   
9. In the Flow schedule section, define a start time and an end time to the flow if required. By default, the flow will start “As soon as possible” and will never end.
10. Do not turn the Limit user entry into this flow toggle on to define the maximum time a user can enter the flow.
    Note that the users are highly likely to match the eKYC Application Abandonment flow’s entry rules more often and thus might enter the flow too many times. Defining such limits helps you control users from re-entering the flow repeatedly and thus avoid spamming them too much, which in turn provides a better user experience.
    
11. Click Next to move to the third step “Who will enter the flow”. This is where you select the target audience for your Flow.
12. In the Audience section, select All users. For a user to be eligible to enter an event-triggered flow, they must be part of the target audience before they do the required event.
    
13. Click Next to move to the canvas section where you can define the Flow structure that you want the user to move through.

Define Flow Structure

1. Click the + icon. A drawer is displayed.
2. Under Conditions, add the entry condition as “Conditional Split”. 
3. Define the possible movement of your users down the steps of eKYC approval process by starting with: 
   
   • Branch 1 checking for the “eKYC submitted” event 
   • Branch 2 having the “eKYC_DocumentsUploaded” event 
   • Branch 3 having the “eKYC_PersonalDetailsFilled” event
     Note that the reason to have the checks in the reverse order is because of the ranking each branch of a conditional split has. For more information, refer to to Branching of Users via Condition Stages. 
4. Turn the Keep evaluating for the next toggle on to define the maximum time to wait for the user to execute the event. For our use case, enter 30 mins.
   
5. Add corresponding communications to each branch of the conditional split to acknowledge their eKYC application being successfully completed by suggesting their next course of action or nudge them to move to the next step in the process based on their current stage.
   For example, a user moving down branch 3 has completed personal information but did not share their documents for approval. So the communications in branch 3 should focus on the same. If a user moving through the default branch has not completed the first step of sharing the personal information itself, the default branch should have communications to nudge them to do the same.
6. The strategy is to create a drip campaign and thus after every communication stage, you can have a Has done event stage to look for the event to be triggered as the next step. The “Yes” path of the stage can have a "Goto" stage connecting it to the first communication in the previous branch; the “No” path can have another communication.
   For example, the default branch should have a Has done event to look for the “eKYC_PersonalDetailsFilled” event and the Yes path has a "Goto" stage connecting the first communication from Branch 3 to the user. The No path has another communication to target the user to get them to fill in their personal details.
   
7. Add as many action campaigns you want to nudge the user for both getting their feedback and sending a message. Make sure to have some gap between any two communications to avoid spamming the user by using a Wait stage, especially in the Yes path of your “Has done events”. For more information, refer to Add Controls to Flow.
8. Click Publish.

Conclusion

In this use case, we created a Flow campaign to nudge users to complete their eKYC process, depending on the stage they dropped off.

• Now that we have published the Flow, we can analyze how well our Flow is performing.
• We can understand how many users entered the flow because of our campaign. Create a segmentation on the “User Entered Flow” event by mentioning the “Flow ID”. For more information, refer to Users who have entered/exited the Flow.
• We can also understand how many users actually completed their eKYC because of our campaign. Create a segmentation on the “Flow Trip Conversion” event by mentioning the “Flow ID”. For more information, refer to Conversion Tracking and Attribution in Flows.