SP3: Manage customer relationships: Difference between revisions
No edit summary |
No edit summary |
||
(2 intermediate revisions by the same user not shown) | |||
Line 22: | Line 22: | ||
==Process description== | ==Process description== | ||
<html><span id="md-itempage-description" itemprop="description">The customer relationship management process in YaSM (<a href="https://yasm.com/wiki/en/img/yasm-process/Manage-customer-relationships-yasm-sp3.jpg" title="YaSM customer relationship management (SP3)">fig. 1</a>) is about finding new customers for the service provider's offerings and establishing a mutually beneficial relationship with existing customers. This is achieved in particular by obtaining regular feedback from customers through customer meetings and surveys, and by dealing with customer requirements (and complaints) in a professional way.</span></p> | <html><span id="md-itempage-description" itemprop="description">The <b><span style="color:#465674;">customer relationship management process</span></b> in YaSM (<a href="https://yasm.com/wiki/en/img/yasm-process/Manage-customer-relationships-yasm-sp3.jpg" title="YaSM customer relationship management (SP3)">fig. 1</a>) is about finding new customers for the service provider's offerings and establishing a mutually beneficial relationship with existing customers. This is achieved in particular by obtaining regular feedback from customers through customer meetings and surveys, and by dealing with customer requirements (and complaints) in a professional way.</span></p> | ||
<p> </p> | |||
< | |||
<div itemid="https://yasm.com/wiki/en/img/yasm-process/Manage-customer-relationships-yasm-sp3.jpg" itemscope itemtype="https://schema.org/ImageObject"> | <div itemid="https://yasm.com/wiki/en/img/yasm-process/Manage-customer-relationships-yasm-sp3.jpg" itemscope itemtype="https://schema.org/ImageObject"> | ||
<meta itemprop="width" content="1200" /> | <meta itemprop="width" content="1200" /> | ||
<meta itemprop="height" content="900" /> | <meta itemprop="height" content="900" /> | ||
Line 36: | Line 35: | ||
<meta itemprop="dateCreated" content="2014-05-02" /> | <meta itemprop="dateCreated" content="2014-05-02" /> | ||
<meta itemprop="datePublished" content="2014-05-08" /> | <meta itemprop="datePublished" content="2014-05-08" /> | ||
<meta itemprop="dateModified" content=" | <meta itemprop="dateModified" content="2024-05-20" /> | ||
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | <span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | ||
<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-process/16x9/Manage-customer-relationships-yasm-sp3.jpg" /> | <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-process/16x9/Manage-customer-relationships-yasm-sp3.jpg" /> | ||
Line 43: | Line 42: | ||
<meta itemprop="dateCreated" content="2020-06-13" /> | <meta itemprop="dateCreated" content="2020-06-13" /> | ||
<meta itemprop="datePublished" content="2020-06-15" /> | <meta itemprop="datePublished" content="2020-06-15" /> | ||
<meta itemprop="dateModified" content="2024-05-20" /> | |||
</span> | |||
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | |||
<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-process/800px/Manage-customer-relationships-yasm-sp3.jpg" /> | |||
<meta itemprop="width" content="800" /> | |||
<meta itemprop="height" content="600" /> | |||
<meta itemprop="dateCreated" content="2024-05-23" /> | |||
<meta itemprop="datePublished" content="2024-05-30" /> | |||
</span> | |||
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | |||
<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-process/480px/Manage-customer-relationships-yasm-sp3.jpg" /> | |||
<meta itemprop="width" content="480" /> | |||
<meta itemprop="height" content="360" /> | |||
<meta itemprop="dateCreated" content="2024-05-23" /> | |||
<meta itemprop="datePublished" content="2024-05-30" /> | |||
</span> | </span> | ||
< | <figure class="mw-halign-left" typeof="mw:File/Thumb"><a itemprop="contentUrl" href="https://yasm.com/wiki/en/img/yasm-process/Manage-customer-relationships-yasm-sp3.jpg" title="Manage customer relationships. - YaSM customer relationship management process SP3"> | ||
< | <img srcset="https://yasm.com/wiki/en/img/yasm-process/480px/Manage-customer-relationships-yasm-sp3.jpg 480w, https://yasm.com/wiki/en/img/yasm-process/800px/Manage-customer-relationships-yasm-sp3.jpg 800w, https://yasm.com/wiki/en/img/yasm-process/Manage-customer-relationships-yasm-sp3.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-process/Manage-customer-relationships-yasm-sp3.jpg" fetchpriority="high" decoding="async" width="800" height="600" class="mw-file-element" alt="Fig. 1: Manage customer relationships. - YaSM customer relationship management process (CRM-Prozess) SP3. - Related with: Practice of ITIL 4 relationship management." /></a><figcaption><span style="font-variant:small-caps;"><b>Fig. 1: 'Manage customer relationships'</b><br /><a href="https://yasm.com/wiki/en/img/yasm-process/Manage-customer-relationships-yasm-sp3.jpg" title="YaSM customer relationship management SP3">YaSM customer relationship management (CRM) process SP3</a>.</span></figcaption></figure></div></html> | ||
<br style="clear:both;"/> | |||
The information gained is an important input for other service management processes, such as | |||
* The strategic process which decides about the introduction of new services or significant enhancements to existing ones</li> | |||
* The service improvement process which is tasked with identifying weaknesses and improvement potentials in the current services. | |||
CRM also takes care of negotiating and signing formal contracts (customer service agreements) between the customer and the service provider. | |||
<p> </p> | <p> </p> | ||
< | <html><i><u>Compatibility</u>: The YaSM CRM process is <a href="/wiki/en/index.php/YaSM_and_ISO_20000#ISO_20000_requirements_and_related_service_management_processes" title="YaSM and ISO 20000">aligned with ISO 20000</a>, the international standard for service management (see ISO/IEC 20000-1:2018, sections <a href="/wiki/en/index.php/YaSM_and_ISO_20000#Service-portfolio" title="ISO 20000 section 8.2: Service portfolio">8.2</a> and <a href="/wiki/en/index.php/YaSM_and_ISO_20000#Relationship-and-agreement" title="ISO 20000 section 8.3: Relationship and agreement">8.3</a>), and it <a href="/wiki/en/index.php/YaSM_and_ITIL#ITIL-4-Relationship-management" title="ITIL 4 practices and YaSM processes: ITIL 4 relationship management">corresponds to the practice of 'ITIL 4 relationship management'</a>.</i></html> | ||
==Sub-processes== | ==Sub-processes== | ||
Line 131: | Line 147: | ||
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm"> | <div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm"> | ||
<dt itemprop="name">Service definition</dt> | <dt itemprop="name">Service definition</dt> | ||
<dd itemprop="description" style="margin-bottom: 1em;">A service definition specifies the service properties, in particular the offered functionality and the guaranteed service levels. Service definitions also describe how the organization's resources are used in order to provide the service. A service can be provided using one or several other (internal or external) supporting services. <a href="#ydo" title="YaSM data object">[*]</a></dd></div> | <dd itemprop="description" style="margin-bottom: 1em;">A service definition specifies the service properties, in particular the offered functionality and the guaranteed service levels. Service definitions also describe how the organization's resources are used in order to provide the service. A service can be provided using one or several other (internal or external) supporting services. See also: <a href="https://yasm.com/wiki/en/index.php/Service_Definition_-_Template" title="Service definition document template">Checklist / document template 'Service definition'</a>. <a href="#ydo" title="YaSM data object">[*]</a></dd></div> | ||
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm"> | <div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm"> | ||
<dt itemprop="name">Suggested process modification</dt> | <dt itemprop="name">Suggested process modification</dt> | ||
Line 143: | Line 159: | ||
<p> </p> | <p> </p> | ||
<hr /> | <hr /> | ||
<p><i><u>Notes</u> | <p><i><u>Notes:</u></i> | ||
</p><p><span id="ydo"><strong>[*]</strong> <i>"YaSM data objects"</i> are those documents or records for which the YaSM model provides detailed recommendations: Every YaSM object has an associated checklist (see <a href="https://yasm.com/wiki/en/index.php/Service_Management_Checklists" title=" | </p><p><span id="ydo"><strong>[*]</strong> <i>"YaSM data objects"</i> are those documents or records for which the YaSM model provides detailed recommendations: Every YaSM object has an associated checklist (see <a href="https://yasm.com/wiki/en/index.php/Service_Definition_-_Template" title="Service Definition document template">document template 'Service definition'</a> and <a href="https://yasm.com/wiki/en/index.php/Service_Management_Checklists#yasm-template-example" title="Examples: YaSM checklists and document templates">more examples</a>) describing its typical contents, and an associated lifecycle diagram depicting how the status of the object changes as it is created, updated, read and archived by various YaSM processes (see <a href="https://yasm.com/wiki/en/img/yasm-project/Yasm-object-lifecycle-diagram.jpg" title="Example: YaSM object lifecycle diagram (.JPG)">example</a>).</span> | ||
</p><p><i>"Other objects"</i> are mostly informal data or information where YaSM has less strong views about their contents. There are no associated lifecycle diagrams or checklists.</html> | </p><p><i>"Other objects"</i> are mostly informal data or information where YaSM has less strong views about their contents. There are no associated lifecycle diagrams or checklists.</html> | ||
Line 155: | Line 171: | ||
==Roles and responsibilities== | ==Roles and responsibilities== | ||
<span id="responsible">Process owner: The ''customer relationship manager'' is responsible for maintaining a positive relationship with customers. This role identifies customer needs and makes this information available to the service provider organization, so that the service provider is able to offer an appropriate range of services.</span> | |||
<p> </p> | <p> </p> | ||
{| class="wikitable" style="background: white | {| class="wikitable" style="background: white; font-size: 95%" | ||
|+ | |+style="background:#465674; color:#ffffff; font-size: 110%"|Responsibility matrix: 'SP3: Manage customer relationships' | ||
|- style="vertical-align:top" | |- style="vertical-align:top" | ||
! colspan="2"| YaSM role / sub-process | ! colspan="2"| YaSM role / sub-process | ||
Line 203: | Line 217: | ||
<html><div itemid="https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-customer-relationship-management-process.jpg" itemscope itemtype="https://schema.org/ImageObject"> | <html><div itemid="https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-customer-relationship-management-process.jpg" itemscope itemtype="https://schema.org/ImageObject"> | ||
<meta itemprop="caption" content="Process objective: YaSM customer relationship management, CRM - Manage customer relationships (SP3)." /> | <meta itemprop="caption" content="Process objective: YaSM customer relationship management, CRM - Manage customer relationships (SP3)." /> | ||
<meta itemprop="width" content="1200" /> | <meta itemprop="width" content="1200" /> | ||
<meta itemprop="height" content="627" /> | <meta itemprop="height" content="627" /> | ||
<meta itemprop="dateCreated" content="2021-09-21" /> | <meta itemprop="dateCreated" content="2021-09-21" /> | ||
<meta itemprop="datePublished" content="2021-09-22" /></ | <meta itemprop="datePublished" content="2021-09-22" /> | ||
< | <span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | ||
< | <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-process/goal-definition/400px/yasm-customer-relationship-management-process.jpg" /> | ||
<meta itemprop="width" content="400" /> | |||
<meta itemprop="height" content="209" /> | |||
<meta itemprop="dateCreated" content="2023-12-12" /> | |||
<meta itemprop="datePublished" content="2023-12-29" /> | |||
</span> | |||
<meta itemprop="keywords" content="CRM process: Objectives" /> | |||
<figure class="mw-halign-left" typeof="mw:File/Thumb"><a itemprop="contentUrl" href="https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-customer-relationship-management-process.jpg" title="Customer relationship management (CRM): process objective"><img srcset="https://yasm.com/wiki/en/img/yasm-process/goal-definition/400px/yasm-customer-relationship-management-process.jpg 400w, https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-customer-relationship-management-process.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-customer-relationship-management-process.jpg" decoding="async" width="400" height="209" class="mw-file-element" alt="The customer relationships management process in YaSM aims to maintain a positive relationship with the customers. In particular, the CRM process identifies potential new customers and ensures that regular feedback is obtained from existing customers through customer meetings and surveys." /></a><figcaption><span style="font-variant:small-caps;">Customer relationship management process: Objectives</span></figcaption></figure></div> | |||
<p>By:  Stefan Kempter <a href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>  and  Andrea Kempter <a href="https://www.linkedin.com/in/andreakempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Andrea Kempter | Profile on LinkedIn" alt="Contributor: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps.<br style="clear:both;"/ | <p>Is based on: The CRM process from the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map">YaSM Process Map</a>.</p> | ||
<p>By:  Stefan Kempter <a href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>  and  Andrea Kempter <a href="https://www.linkedin.com/in/andreakempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Andrea Kempter | Profile on LinkedIn" alt="Contributor: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps.<br style="clear:both;"/><p> | |||
<p> </p> | <p> </p> | ||
Line 258: | Line 278: | ||
<meta itemprop="name" content="SP3: Manage customer relationships" /> | <meta itemprop="name" content="SP3: Manage customer relationships" /> | ||
<meta itemprop="alternateName" content="YaSM CRM process" /> | <meta itemprop="alternateName" content="YaSM CRM process" /> | ||
<meta itemprop="alternateName" content="CRM process" /> | |||
<meta itemprop="alternateName" content="Customer relationship management process" /> | |||
<link itemprop="url" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships" /> | <link itemprop="url" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships" /> | ||
<link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.1"> | <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.1"> |
Latest revision as of 16:51, 11 October 2024
Process name: Manage customer relationships - Part of: Supporting processes
Previous process: Maintain the service portfolio
Next process: Manage configuration information
Process description
The customer relationship management process in YaSM (fig. 1) is about finding new customers for the service provider's offerings and establishing a mutually beneficial relationship with existing customers. This is achieved in particular by obtaining regular feedback from customers through customer meetings and surveys, and by dealing with customer requirements (and complaints) in a professional way.
The information gained is an important input for other service management processes, such as
- The strategic process which decides about the introduction of new services or significant enhancements to existing ones
- The service improvement process which is tasked with identifying weaknesses and improvement potentials in the current services.
CRM also takes care of negotiating and signing formal contracts (customer service agreements) between the customer and the service provider.
Compatibility: The YaSM CRM process is aligned with ISO 20000, the international standard for service management (see ISO/IEC 20000-1:2018, sections 8.2 and 8.3), and it corresponds to the practice of 'ITIL 4 relationship management'.
Sub-processes
YaSM's CRM process has the following sub-processes:
- SP3.1: Find new customers
- Process objective: To identify potential new customers and to present the service provider's offerings to those potential new customers.
- SP3.2: Sign or terminate customer service agreements
- Process objective: To sign customer service agreements with customers who wish to use the service provider's services. This process is also responsible for terminating customer service agreements which are no longer needed.
- SP3.3: Handle customer complaints
- Process objective: To record customer complaints, to assess if the complaints are justified and to determine the steps required to deal with the complaints.
- SP3.4: Monitor customer complaints
- Process objective: To continuously monitor the processing status of outstanding customer complaints and to take corrective action if required.
- SP3.5: Hold customer meetings
- Process objective: To communicate with customers on a regular basis in order to learn about their needs and plans for the future.
- SP3.6: Perform customer satisfaction surveys
- Process objective: To plan, carry out and evaluate regular customer satisfaction surveys. The principal aim of this process is to learn about areas where customer expectations are not being met before customers are lost to alternative service providers.
Process outputs
This section lists the documents and records produced by 'customer relationship management'. YaSM data objects [*] are marked with an asterisk, while other objects are displayed in gray.
- Complaint record
- A record containing the details of a customer complaint, including the actions taken to resolve the complaint. [*]
- Complaint status information
- A message containing the present status of a complaint, typically sent to a customer who earlier made a complaint.
- Customer meeting minutes
- The customer meeting minutes record the details and findings from a meeting of the service provider with one of its customers. This report is an important input for developing the service strategy and defining service improvement initiatives. [*]
- Customer portfolio
- The customer portfolio is used to record all information related to customers. The customer portfolio is the customer relationship manager’s view of the customers who receive services from the service provider. [*]
- Customer service agreement
- An agreement between a service provider and a customer for the provision of a service as specified in the service definition. A signed customer service agreement represents a commitment by the service provider to deliver a service in line with the agreed quality, at a specified cost. A single agreement may cover multiple services. [*]
- Customer survey evaluation
- The evaluation of a customer satisfaction survey, presenting the results and findings from the survey in a condensed way. [*]
- Customer survey questionnaire
- A customer survey is typically based on questionnaires, aimed at getting insight into overall customer satisfaction and customers' views on specific (aspects of) services. In many cases, answers are given using a scale, for example '1: Very dissatisfied', … , '10: Very satisfied'. [*]
- General customer agreement
- A higher-level agreement with a customer. General customer agreements are at times put in place with particular customers, covering issues regardless of the services being used. If such agreements exist, they are routinely attached to customer service agreements.
- Service definition
- A service definition specifies the service properties, in particular the offered functionality and the guaranteed service levels. Service definitions also describe how the organization's resources are used in order to provide the service. A service can be provided using one or several other (internal or external) supporting services. See also: Checklist / document template 'Service definition'. [*]
- Suggested process modification
- A suggestion for modifying one or several service management processes. Suggestions for process modifications or improvements may originate from anywhere within the organization.
- Suggested service modification
- A suggestion for modifying a service, for example to improve service quality or economics. Suggestions may originate from anywhere within or outside of the service provider organization.
Notes:
[*] "YaSM data objects" are those documents or records for which the YaSM model provides detailed recommendations: Every YaSM object has an associated checklist (see document template 'Service definition' and more examples) describing its typical contents, and an associated lifecycle diagram depicting how the status of the object changes as it is created, updated, read and archived by various YaSM processes (see example).
"Other objects" are mostly informal data or information where YaSM has less strong views about their contents. There are no associated lifecycle diagrams or checklists.
Process metrics
Process metrics are used, for example, to assess if the service management processes are running according to expectations.
For suggestions of suitable metrics, please refer to the list of metrics for the YaSM CRM process.
Roles and responsibilities
Process owner: The customer relationship manager is responsible for maintaining a positive relationship with customers. This role identifies customer needs and makes this information available to the service provider organization, so that the service provider is able to offer an appropriate range of services.
YaSM role / sub-process | Customer | Customer relationship manager | |
---|---|---|---|
SP3.1 | Find new customers | - | AR |
SP3.2 | Sign or terminate customer service agreements | R | AR |
SP3.3 | Handle customer complaints | - | AR |
SP3.4 | Monitor customer complaints | - | AR |
SP3.5 | Hold customer meetings | R | AR |
SP3.6 | Perform customer satisfaction surveys | R | AR |
Notes
Is based on: The CRM process from the YaSM Process Map.
By: Stefan Kempter and Andrea Kempter , IT Process Maps.
Process description › Sub-processes › Process outputs › Metrics › Roles