Skip to main content

Sign In Module

Introduction​

Customers enter their email addresses to sign in. Stored in CRM. Customers can log in again later and access their profile. If they log in on a different device or another channel (WhatsApp, Facebook, WeChat, Alexa, Google) they receive a PIN to verify their identity. The time for sending the code can generally be chosen by the editor.

Typical Use Cases​

This process module is necessary for every process module that collects personal information like first name or birth date.

sign_in_demo

How to Use the Module​

Code / OTP email​

An email containing a verification code (or one time password, OTP) is sent in case (a) a customer that has registered in the chat before comes back and signs in with the same email address again or (b) that the customer database is disabled in your tenant.

Then this UI element appears and asks that user to enter the code that they received via email:

Slide1 2

This email verification step is important so that no data can be leaked or settings can be changed for a previously registered user. If we would not verify the users on their second log in, anyone could log in with any email address.

By applying the setting Verify email with code on first use you can instruct LoyJoy to verify on each log-in, even for first-time log-in. Keep in mind sending the code directly at the first registration is bad for conversion. Our standard is therefore the second registration.

In detail, this means:

  1. If the customer logs in for the first time with their email address, this is stored as a cookie in the browser.
  2. If both the end device and the browser remain the same, neither the email address nor a code needs to be entered a second time.
  3. If the customer logs in for the first time with a new browser or device, a new code is sent.

Code email template​

The code email body can be customized by entering an HTML email template.