The different types of steps on Particeep Plug
This article is intended for the following people:
Insurers/Bankers Brokers/Distributors Sellers
For more information on roles on Plug, please see. this article.
What do you need to know before creating your subscription journey?
This document is intended to guide you in the construction of your subscription journey by taking into account the specificities of the solution.
What steps do we have in Plug?
- Identity
- Phone
- Address
- Price
- Payment schedule
- Payment
- Document viewing
- Signing documents
- Final
- Standard
Why are they important?
With the exception of steps Identity and Standard, all other steps are connected to single microservices. To ensure the smooth operation of microservices, we recommend keeping these steps as they are and not bundling them together.
- Example 1: Do not have the "mail" field (from the mail step) and the "phone" field (from the phone step) on the same step.
- Example 2: It is not possible to add input fields, other than those already present, on the Price step.
What are the specifics of each step?
Identity
Introduction:
The step Identity is composed of 2 input fields, "First name" and "Last name", which allow the user of the subscription journeys to provide information about their identity.
Position in the journey:
Ideally at the beginning of the course
Associated microservice:
None
Phone
Introduction:
The stage Telephone is composed of a single "Telephone" input field that allows the user in the subscription journey to enter their telephone number.
Position in the journey:
Wherever you want it
Associated microservice:
This step comes with the ability to verify the given phone number with an SMS and a verification code to be entered on the platform. This feature can be activated and deactivated.
Particularity:
If you choose not to enable this microservice, then the phone field can be grouped with the "First Name" and "Last Name" fields on the same step.
Introduction:
The step Mail is composed of two input fields, "Email" and "Password" which allow the user to either create an account or log into their account.
Nb: This step is subject to change or only email will be requested.
Notes:
If the email address has never been provided on this subscription journey, the step is considered a registration. The "Email" and "Password" values will therefore be entered into the database afterwards. (As shown in the image above)
If the email address has already been provided on this subscription journey, the step is considered a login. The "Email" and "Password" values will be compared with the values already present in the database to authenticate the user in the subscription journey.
Position in the journey:
As soon as possible. This step is the only step that registers a user's email address. If you wish to send reminder emails for an unfinished course, the user will need to have entered their email address first. For more information on emails, please see our article on e-mails
Associated micro service:
This step is the only one that can register an email address so it is necessary to send emails to the user in the subscription journey. It also allows the user to create an account and authenticate themselves.
Particularity:
No other questions or fields can be added on this step.
Address
Particularity:
If you choose not to enable this microservice, then the address fields can be grouped with the "First Name" and "Last Name" and/or phone fields on the same step.
Price
Introduction:
The stage Price is composed of several "cards" displaying different amounts. This step allows the user of the subscription journey to choose the subscription he/she wants in relation to the amounts offered.
Position in the journey:
After the necessary steps to calculate the proposed amounts.
Associated micro service:
This step connects to a database that allows a certain amount to be displayed depending on the values previously provided by the user of the subscription journey.
Particularity:
No other questions or fields can be added on this step.
Payment Schedule
Introduction:
The step Payment schedule is composed of several input fields, "Desired effective date" and "Desired periodicity", allowing the user of the subscription journey to set up a payment schedule.
Position in the journey:
Where you want it after the step Price.
Associated micro service:
This particular display for payment schedules is only possible with this step.
Particularity:
No other questions or fields can be added on this step.
Payment
Introduction:
The step Payment is composed of several different input fields allowing the user of the subscription journey to pay either by Credit Card or by SEPA Direct Debit.
Position in the journey:
Wherever you want after the "Price" step.
Associated micro service:
Payment functionality is provided by Stripe.
Particularity:
No other questions or fields can be added on this step.
Notes:
It is possible, from the Broker instance, to set up which payment types you want to have on your subscription journey: Bank Card, SEPA Direct Debit or both.
Viewing documents
Introduction:
The step Document Viewing is divided into 2 parts: The first to view "non-dynamic" documents, the second to view "dynamic"documents.
The "non-dynamic" documents in the image above are the two documents at the top of the page. When the user clicks on one of these documents, it will be downloaded to the user's device.
The "dynamic" (Subscription form or membership form) documents on the image above are the 2 documents that can be previewed directly on the page. These documents are enriched with values provided by the user in the subscription journey (Example: his name, his address, the chosen offer etc...)
Position in the journey:
For non-dynamic documents: Wherever you wish.
For dynamic documents:Ideally at the end of the subscription journey, after the steps necessary to generate a document.
Associated microservice:
The part about generating and previewing dynamic documents is only possible in this step.
Particularity:
No other questions or fields can be added on this step.
Document signing
Introduction:
The step Document signing is powered by Universign. It consists of a preview of the document to be signed, as well as a signature confirmation system by entering a code received via SMS.
Position in the course:
Wherever you want after the user provides their name, phone number and other values present on the document to be signed.
Associated microservice:
Document signing is done through Universign.
Particularity:
No other questions or fields can be added on this step.
Final
Introduction:
The step Final is a simple step to indicate to the user of the subscription journey that the journey is complete. The special feature of this step is that it can then redirect the subscription journey user to their customer area, where they will see a summary of the information they have provided.
Position in the journey:
This is the final step in your underwriting journey.
Associated micro service:
The particularity of this step is that it is the only one that can redirect the user from the subscription journey to his customer area where he can find the details of his subscription.
Standard
Introduction:
The stage Standard is a special step compared to the others shown previously. It is the only step that allows the complete modification of its content. It can be filled with different types of questions.
Position in the course:
Wherever you wish.
Associated micro service:
None.
Why would I use the other steps when I could make my route with only Standard steps?
It is technically possible to make a course only with stages Standard. However, Standard stages will not be able to inherit the microservices specific to other stages.
For example: you can have one step Standard with one input field called "Email" and the other "Phone". However, these input fields will not be able to trigger a user to register as well as verify the phone number by sending a confirmation SMS.