Setup Customer
Customer Registration Configuration
This article covers all settings related to customer registration and profile update.
To configure customer registration, follow these steps.
- On the InTouch home page, navigate to Profile > Organization Settings > Miscellaneous > Registration Configuration.
- Configure the required fields based on the description provided in the following table.
OPTION | DESCRIPTION |
|---|---|
CONF_REGISTRATION_PRIMARY_KEY | Choose the primary identifier of the customer. This is the unique identifier of the customer required for registration. |
CONF_ALLOW_REGISTRATION_FROM_ANY_IDENTIFIERS | Select this to allow the registration of customers using any of the identifiers. |
CONF_USERS_IS_EMAIL_REQUIRED | Check this if email id is a mandatory parameter to register a customer. |
CONF_USERS_IS_EMAIL_UNIQUE | Check this to make the email ID a unique identifier. If any registered email ID is registered the accounts will be merged automatically. |
CONF_USERS_USE_EXTERNAL_ID | Check this to capture the external ID of customers while registering. |
CONF_USERS_IS_EXTERNAL_ID_REQUIRED | Check this to make the external ID mandatory to register a customer. Not applicable if the external ID is the primary identifier. |
CONF_USERS_IS_MOBILE_REQUIRED | Check this to make the mobile number mandatory to register a customer. Not applicable if mobile is the primary identifier. |
CONF_ALLOW_MOBILE_UPDATE | Check this to allow updating registered mobile numbers of customers. |
CONF_ALLOW_EMAIL_UPDATE | Check this to allow updating registered email IDs of customers. |
CONF_LOYALTY_ALLOW_EXTERNAL_ID_UPDATE | Check this to allow updating registered external IDs of customers. |
CONF_PRIMARY_IDENTIFIER_STRICT_CHECK | Check this to verify if the primary identifier is already registered in a different account. |
CONF_SKIP_SECONDARY_ID_ON_PRIMARY_MISMATCH | Check this to skip account merging if only secondary identifiers match but primary identifiers are different. |
USE_CRM_REGISTRATION_INFO_FROM_BASE_STORE | NA |
CONF_GIFT_CARD_ENABLED | Check this to enable gift card |
CONF_ORG_CURRENCY_CODE | Set the ISO currency code of the org. |
CONF_ORG_CURRENCY_SYMBOL | Set the currency symbol of the org as per the currency code. |
CONF_MIN_REGISTRATION_DATE | Set the minimum date and time from which the registration is valid. Registration fails if the registration date and time is prior to the value set herein ( especially through API or Data Import). |
SERVER_VALIDATION_PIN_SMS | Configure the verification SMS that will be sent to customers to validate the registered mobile numbers. Use the tag {{pin}} to insert the verification PIN in the message. |
SERVER_VALIDATION_PIN_EMAIL | Configure the verification email that will be sent to customers to validate the registered email ID. Use the tag {{pin}} to insert the verification PIN in the message. |
CONF_LOYALTY_REGISTER_CUSTOMER_GENDER | Choose the custom field for gender from the drop-down. |
CONF_LOYALTY_REGISTER_CUSTOMER_AGE | Choose the custom field for age from the drop-down. |
CONF_CLIENT_V2_API_ENABLED | Check this if sources other than InStore are supported for the org. |
CONF_GEN_CARD_NUMBER_AS_EXTERNAL_ID_ENABLED | Check this to enable generating external IDs automatically from the Capillary end. |
SOURCE_ACCOUNTS_EXTERNALID_ENABLED | Check this to enable support for external ID capture. |
CONF_CARD_NUMBER_GENERATION_ENABLED | Check this to enable generating card numbers automatically from the Capillary end. |
CONF_CARD_NUMBER_SUFFIX | Specify the suffix you want to have for the external card (supports alphanumeric value). |
CONF_CARD_NUMBER_PREFIX | Specify the prefix for the external card (supports alphanumeric value). For example, BRAND20. |
CONF_CARD_NUMBER_LENGTH | Specify the length of the external card. You can have up to 50 characters. |
CONF_CARD_NUMBER_OFFSET | Specify the card sequence numbers that you want to ignore from the top. For example, if you set 10, the first 10 cards will be considered invalid. |
Check this to enable primary identifier checks when registering or updating customers. | |
CONF_IDENTIFIERS_SYNC_ENABLED | Check this to synchronize identifiers such as mobile numbers, email addresses, and external IDs between Instore profiles and V2 profiles (external profiles such as WebEngage) within the system.
|
-CONF_CLIENT_DEFAULT_COUNTRYCODE_PASSED | Check this to auto select country code to the mobile number entered on the registration screen. The validation sequence will be as follows. |
External ID configuration
You can use the below configurations to enable the generation of a customised external ID for the customers. Once this configuration is enabled, the external ID in the customer add API payload will be replaced with the generated external ID.
Attention
There is no UI to enable this configuration. You need to raise a JIRA ticket (sample ticket) to the sustenance team to enable these configurations. Turn around time is five days.
Configuration & Description | Value |
|---|---|
CONF_CARD_NUMBER_GENERATION_ENABLED (Mandatory) Enables external ID number generation. | 0 - Disable |
SOURCE_ACCOUNTS_EXTERNALID_ENABLED (Mandatory) | ["INSTORE:"] - Instore ["web_engage:1234"]["web_engage:1234"] - ["INSTORE:", "web_engage:1234"]["INSTORE:", "web_engage:1234"] - Both Instore and webengage where 1234 is account id. |
CONF_CARD_CHECKSUM_DIGIT_ALGO (Mandatory) | LUHN_ALGO, MOD7_ALGO, AUTO_INC |
CONF_CARD_NUMBER_LENGTH (Mandatory) | Integers ranging from 1-50. |
CONF_CARD_NUMBER_OFFSET (Optional) | Any integer value |
CONF_CARD_NUMBER_PREFIX (Optional) | Any integer value but prefix + suffix + system-generated number should not be more than 50. |
CONF_CARD_NUMBER_SUFFIX (Optional) | Any integer value but prefix + suffix + system-generated number should not be more than 50. |
CONF_VALUES_TO_INCLUDE_FOR_CHECKSUM_DIGIT (Optional) | PREFIX - Prefix is considered |
Customer ingestion restriction configuration
There is no UI to enable this configuration. You need to raise a JIRA ticket (sample ticket) to the sustenance team to enable these configurations. Turn around time is five days.
CONF_RESTRICT_ORPHAN_V2_PROFILE - This configuration prevents the ingestion of a WebEngage profile into the Capillary platform for a specific customer if they do not already have an existing Instore profile.
Managing customer lifecycle with customer status
A customer status defines the relationship between a brand and a customer. For example, a customer who interacts often with the brand can be defined as an active customer. Further, these statuses can be used to run the loyalty program and assign coupons, reward points etc accordingly. For example, more offers can be offered to a customer to make an inactive customer to active customer..
Activating customer status
To activate customer status for your organisation, navigate to Organisation settings> Miscellaneous> Customer Status configuration and select the Enable customer status check box.
On enabling the customer status, the existing fraud status will be replaced by the customer status function.
Types of customer statuses
The various customer statuses available in the Capillary platform that you can configure are:
- Active
- Suspended
- Deleted
- Fraud suspected
- Fraud confirmed
- Internal
- Pending deletion
Creating a custom label
You can click the Create new label option in the customer label and enter a new label name to assign a custom name for the status. You can add multiple labels if required. The first status label that you create is set as the default status value.
Active customer status
The active status can be used to indicate that the customer is active.
NOTES:
- There are no restrictions for customers with Active status.
- All customers are marked Active by default.
Suspended, Fraud suspected, Fraud confirmed, and Internal customer status
You can restrict the following operations for the users with Suspended, Fraud suspected, Fraud confirmed or Internal status.
Restriction | Description |
|---|---|
Block coupons redemption | Restrict from redeeming coupons. |
Block issual of loyalty promotions | Restrict from receiving points. |
Block identifier change and account merge | Restrict from account merging and identifier change requests. |
Block issual of badges | This is a future development feature. |
Block issual of coupons | Restrict from providing coupons. |
Block enrollment into loyalty promotions | This is a future development feature. |
Block points allocation | Restrict from providing points. When this restriction is added on any label, then the points allocation from any points-related action (like transaction point allocation, allocation points, target point allocation, issue to the referrer, issue to referee, goodwill points, import profile) will be blocked for the customer. |
Block points redemption | Restrict from redeeming points. |
Block tier upgrade | Restrict from tier upgrade. |
Block transaction | Restrict future transactions. |
Mark transaction outlier | Mark the transactions made by the selected label(s) as outliers. |
To restrict access, select the individual status labels or all the created status labels from the desired restriction drop-down. Click Select, and then click Update.
Deleted customer status
The deleted status allows you to block every action for customers with this status. To configure restriction, from the Block everything drop-down, select the individual custom labels or select all labels created for Deleted. Click Select and then click Update.
Pending deletion customer status
This status is used to indicate the status of customers for whom a deletion request is raised. For Pending Deletion, whenever a PII deletion request is triggered, a label Deletion_pending is automatically created and assigned to the customer, regardless of any other label that may have been created and set as default.
Updated 2 days ago