Customer Related Database Management System
Customer Related Database Management System
Customer Related Database Management System
The customer related database gives a business an insight on the customer behaviour. It is
the foundation on which the CRM software strategies work. For any business using the
CRM, the customer-related database is highly important to impart the customer-based
strategies and tactics.
The database supports all the forms of CRM Strategic, Operational, Analytical, and
Collaborative.
Customers personal information containing fields for name, address, contact details,
contact preferences, age, marital status, birthdate, anniversary, professional and
social status, etc.
Channel managers can record business-owned retail outlets, online retail information.
Product managers may record product preference, price band, product categories
explored, etc.
Based on the respective purposes, there are two types of databases
Operational and Analytical. The operational data resides in Online Transaction
Processing (OLTP) database and analytical data resides in Online Analytical Processing
(OLAP) database.
The primary data is collected by conventional means such as conducting surveys, holding a
skill competition, inviting the customers to subscribe for the newsletter or to register their
purchase, etc.
The location of CRM users. Especially in case of global use of CRM, the multilingual
users from different time zones can access the CRM for operational and analytical
purposes.
Data Attributes
The CRM data must have the following attributes
It must be sharable because many people need to access it from various geographical
locations.
It should be most accurate. Inaccurate data wastes the marketing efforts of the
business, predicts wrong opportunities and serves the customers with insufficient and
inaccurate service. Data should be reviewed timely to ensure removal of inaccuracy
taken place while acquiring and entering the data.
It should be up-to-date means it should store and show the latest information.
It should be secured. Businesses need to keep their data safe from loss and theft and
unethical snooping as many businesses can subscribe to the same CRM software
through the same portal.
Collaborative CRM implementations generally use the operational and analytical data as
described below, so that partners in distribution channels can align their efforts to serve end-
customers. Customer-related database is necessary for both operational and analytical CRM
purposes. Operational CRM uses customer-related database to help in the everyday running
of the business.
i. a telecoms customer service representative (CSR) needs to access a customer record when
she receives a telephone query
ii. a hotel receptionist needs access to a guests history so that she can reserve the preferred
type of room smoking or non-smoking, standard or deluxe
iii. a salesperson needs to check a customers payment history to find out whether the account
has reached the maximum credit limit.
iii. Analytical CRM uses customer-related database to support the marketing, sales and
service decisions that aim to enhance the value created for and from customers.
A direct marketer who is planning an e-mail campaign might want to know open and click-
through rates, and click-to-open rates (CTOR) for previous e-campaigns, broken down by
target market, offer and execution. She would also want to know e-mail addresses, e-mail
preferences (html or plain text), and preferred salutation (first name ?Mr? Ms?).
Operational and analytical needs like these help define the contents of customer-related
databases. Senior managers reviewing your companys strategic CRM decisions will require
a completely different set of information. They may want to know the following.
Contact data:
Who is the main contact (name) and who else (other names) is involved in buying decisions?
What are their roles? Who are the decision-makers, buyers, influencers, initiators and
gatekeepers? What are the customers invoice addresses, delivery addresses, phone numbers,
fax numbers, e- mail addresses, street addresses and postal addresses?
Contact history:
Who has communicated with the customer, when, about what, in which medium and with
what outcome?
Transactional history:
What has the customer bought and when? What has been offered to the customer, but not
been purchased?
Current pipeline:
What opportunities are currently in the sales pipeline? What is the value of each opportunity?
What is the probability of closing? Is there a10 per cent, 20 per cent 90 per cent chance of
making a sale? Some CRM applications enable sales people to allocate red, amber or green
signals to opportunities according to the probability of success.
Opportunities:
Whereas transactional history looks backwards, opportunity looks forwards. This is
where opportunities that have not yet been opened or discussed are recorded.
Products:
What products does the customer have? When were these products purchased, and when are
they due for renewal? Have there been any service issues related to these products in the
past?
2. census data
3. modelled data.
1. Hierarchical
2. Network
3. Relational.
Relational databases:
Relational databases are now the standard architecture for CRM applications Relational
databases store data in two dimensional tables comprised of rows and columns. Relational
databases have one or more fields that provide a unique form of identification for each
record. This is called the primary key. For sales databases, each customer is generally
assigned a unique number which appears in the first column
We use the appropriately because the level of accuracy depends upon the function of the
database. Operational CRM applications generally need more accurate and contemporary
data than analytical applications. You may have personally experienced the results of poor
quality data. Perhaps you have received a mailed invitation to become a do nor to a charity, to
which you already donate direct from your salary.
This could have happened when a prospecting list that has been bought by the charity was not
been checked against current donor lists. Perhaps you have been addressed as Mrs. although
you prefer Ms. This is caused because the company has either not obtained or not acted or
checked your communication preferences. One of the biggest issues with customer data is not
so much incorrect data as missing data. Many organizations find it difficult to obtain even
basic customer data, such as e-mail addresses and preferences.
The main steps in ensuring that the database is populated with appropriately accurate
data are as follows:
1. Source the data
It does not take long for databases to degrade. Companies can maintain data integrity in a
number of ways.
1. Ensure that data from all new transactions, campaigns and communications is inserted into
the database immediately. You will need to develop rules and ensure that they are applied.
3. Audit a subset of the files every year. Measure the amount of degradation. Identify the
source of degradation: is it a particular data source or field?
4. Purge customers who have been inactive for a certain period of time. For frequently bought
products, the dormant time period might be six months or less. For products with a longer
repeat purchase cycle, the period will be longer. It is not always clear what a suitable
dormancy period is. Some credit-card users, for example, may have different cards in
different currencies. Inactivity for a year only indicates that the owner has not travelled to a
country in the previous year. The owner may make several trips in the coming year.
5. Drip-feed the database. Every time there is a customer contact there is an opportunity to
add new or verify existing data.
6. Get customers to update their own records. When Amazon customers buy online, they
need to confirm or update invoice and delivery details. Remove customers records when
they request this.