SP3: Manage customer relationships: Difference between revisions

From YaSM Service Management Wiki
No edit summary
No edit summary
Line 65: Line 65:


<p><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>
<p><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>
<p>&nbsp;</p>


==Sub-processes==
==Sub-processes==


<html><!-- define schema.org/CreativeWork -->YaSM's CRM process has the following sub-processes:</p>
<html><!-- define schema.org/CreativeWork -->YaSM's CRM process has the following sub-processes:</p>
<p>&#160;</p>


<!-- define schema.org/CreativeWork -->
<!-- define schema.org/CreativeWork -->
Line 79: Line 77:
<dd itemprop="description">Process objective: To identify potential new customers and to present the service provider's offerings to those potential new customers.</dd></dl>
<dd itemprop="description">Process objective: To identify potential new customers and to present the service provider's offerings to those potential new customers.</dd></dl>
</div>
</div>
<p><br /></p>
<div itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.2" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<div itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.2" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM CRM process SP3.2" />
<meta itemprop="alternateName" content="YaSM CRM process SP3.2" />
Line 85: Line 82:
<dd itemprop="description">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.</dd></dl>
<dd itemprop="description">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.</dd></dl>
</div>
</div>
<p><br /></p>
<div itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.3" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<div itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.3" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM CRM process SP3.3" />
<meta itemprop="alternateName" content="YaSM CRM process SP3.3" />
Line 91: Line 87:
<dd itemprop="description">Process objective: To record customer complaints, to assess if the complaints are justified and to determine the steps required to deal with the complaints.</dd></dl>
<dd itemprop="description">Process objective: To record customer complaints, to assess if the complaints are justified and to determine the steps required to deal with the complaints.</dd></dl>
</div>
</div>
<p><br /></p>
<div itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.4" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<div itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.4" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM CRM process SP3.4" />
<meta itemprop="alternateName" content="YaSM CRM process SP3.4" />
Line 97: Line 92:
<dd itemprop="description">Process objective: To continuously monitor the processing status of outstanding customer complaints and to take corrective action if required.</dd></dl>
<dd itemprop="description">Process objective: To continuously monitor the processing status of outstanding customer complaints and to take corrective action if required.</dd></dl>
</div>
</div>
<p><br /></p>
<div itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.5" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<div itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.5" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM CRM process SP3.5" />
<meta itemprop="alternateName" content="YaSM CRM process SP3.5" />
Line 103: Line 97:
<dd itemprop="description">Process objective: To communicate with customers on a regular basis in order to learn about their needs and plans for the future.</dd></dl>
<dd itemprop="description">Process objective: To communicate with customers on a regular basis in order to learn about their needs and plans for the future.</dd></dl>
</div>
</div>
<p><br /></p>
<div itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.6" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<div itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.6" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM CRM process SP3.6" />
<meta itemprop="alternateName" content="YaSM CRM process SP3.6" />
Line 109: Line 102:
<dd itemprop="description">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.</dd></dl>
<dd itemprop="description">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.</dd></dl>
</div><!-- end of schema.org/CreativeWork --><p></html>
</div><!-- end of schema.org/CreativeWork --><p></html>
<p>&nbsp;</p>


==Process outputs==
==Process outputs==


<html><div itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#Process_outputs" itemscope="itemscope" itemtype="https://schema.org/CreativeWork"><!-- define schema.org/CreativeWork -->
<html><!-- define schema.org/DefinedTermSet -->
<div itemid="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#process-inputs-outputs" itemscope="itemscope" itemtype="https://schema.org/DefinedTermSet">
<link itemprop="additionalType" href="http://www.productontology.org/id/Input/output" />
<meta itemprop="name" content="YaSM process SP3: documents and records" />
<meta itemprop="name" content="YaSM process SP3: documents and records" />
<meta itemprop="alternateName" content="Customer relationship management process outputs" />
<meta itemprop="alternateName" content="Customer relationship management process outputs" />
<meta itemprop="alternateName" content="Customer relationship management data objects" />
<meta itemprop="alternateName" content="Customer relationship management data objects" />
<p><span itemprop="description">This section lists the documents and records produced by 'customer relationship management'.</span> YaSM data objects <a href="#ydo" title="YaSM data object">[*]</a> are marked with an asterisk, while other objects are displayed in gray.</p>
<p><span itemprop="description">This section lists the documents and records produced by 'customer relationship management'.</span> YaSM data objects <a href="#ydo" title="YaSM data object">[*]</a> are marked with an asterisk, while other objects are displayed in gray.</p>
<p>&#160;</p>


<dl id="Complaint-record"><dt>Complaint record</dt>
<dl>
<dd>A record containing the details of a customer complaint, including the actions taken to resolve the complaint. <a href="#ydo" title="YaSM data object">[*]</a></dd></dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="Complaint-record">Complaint record</dt>
<dl id="Complaint-status-information" style="color:#636363"><dt>Complaint status information</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A record containing the details of a customer complaint, including the actions taken to resolve the complaint. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<dd>A message containing the present status of a complaint, typically sent to a customer who earlier made a complaint.</dd></dl>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="Complaint-status-information">Complaint status information</dt>
<dl id="Customer-meeting-minutes"><dt>Customer meeting minutes</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A message containing the present status of a complaint, typically sent to a customer who earlier made a complaint.</dd></div>
<dd>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. <a href="#ydo" title="YaSM data object">[*]</a></dd></dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="Customer-meeting-minutes">Customer meeting minutes</dt>
<dl id="Customer-portfolio"><dt>Customer portfolio</dt>
<dd itemprop="description" style="margin-bottom: 1em;">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. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<dd>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. <a href="#ydo" title="YaSM data object">[*]</a></dd></dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="Customer-portfolio">Customer portfolio</dt>
<dl id="Customer-service-agreement"><dt>Customer service agreement</dt>
<dd itemprop="description" style="margin-bottom: 1em;">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. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<dd>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. <a href="#ydo" title="YaSM data object">[*]</a></dd></dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="Customer-service-agreement">Customer service agreement</dt>
<dl id="Customer-survey-evaluation"><dt>Customer survey evaluation</dt>
<dd itemprop="description" style="margin-bottom: 1em;">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. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<dd>The evaluation of a customer satisfaction survey, presenting the results and findings from the survey in a condensed way. <a href="#ydo" title="YaSM data object">[*]</a></dd></dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="Customer-survey-evaluation">Customer survey evaluation</dt>
<dl id="Customer-survey-questionnaire"><dt>Customer survey questionnaire</dt>
<dd itemprop="description" style="margin-bottom: 1em;">The evaluation of a customer satisfaction survey, presenting the results and findings from the survey in a condensed way. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<dd>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'. <a href="#ydo" title="YaSM data object">[*]</a></dd></dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="Customer-survey-questionnaire">Customer survey questionnaire</dt>
<dl id="General-customer-agreement" style="color:#636363"><dt>General customer agreement</dt>
<dd itemprop="description" style="margin-bottom: 1em;">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'. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<dd>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.</dd></dl>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="General-customer-agreement">General customer agreement</dt>
<dl><dt>Service definition</dt>
<dd itemprop="description" style="margin-bottom: 1em;">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.</dd></div>
<dd>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></dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name">Service definition</dt>
<dl style="color:#636363"><dt>Suggested process modification</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>A suggestion for modifying one or several service management processes. Suggestions for process modifications or improvements may originate from anywhere within the organization.</dd></dl>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name">Suggested process modification</dt>
<dl style="color:#636363"><dt>Suggested service modification</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A suggestion for modifying one or several service management processes. Suggestions for process modifications or improvements may originate from anywhere within the organization.</dd></div>
<dd>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.</dd></dl>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
</div><!-- end of schema.org/CreativeWork --><p>
<dt itemprop="name">Suggested service modification</dt>
<dd itemprop="description" style="margin-bottom: 1em;">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.</dd></div>
</dl>
</div><!-- end of schema.org/DefinedTermSet --><p>


<p>&nbsp;</p>
<p>&nbsp;</p>
Line 160: Line 155:
</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="Example: YaSM checklists and document templates">example</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><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="Example: YaSM checklists and document templates">example</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>
<p>&nbsp;</p>


==Process metrics==
==Process metrics==
Line 168: Line 161:


For suggestions of [[Service Management Metrics|suitable metrics]], please refer to the [[Service_Management_Metrics#Metrics_for_the_CRM_process|list of metrics for the YaSM CRM process]].
For suggestions of [[Service Management Metrics|suitable metrics]], please refer to the [[Service_Management_Metrics#Metrics_for_the_CRM_process|list of metrics for the YaSM CRM process]].
<p>&nbsp;</p>


==Roles and responsibilities==
==Roles and responsibilities==
Line 222: Line 213:
<html><div itemid="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-customer-relationship-management-process.jpg" itemscope itemtype="https://schema.org/ImageObject">
<html><div itemid="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-customer-relationship-management-process.jpg" itemscope itemtype="https://schema.org/ImageObject">
<a href="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-customer-relationship-management-process.jpg" title="Customer relationship management (CRM): process definition" itemprop="contentUrl">
<a href="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-customer-relationship-management-process.jpg" title="Customer relationship management (CRM): process definition" itemprop="contentUrl">
<img style="display: block; float: left; margin-right: 20px" src="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-customer-relationship-management-process.jpg" width="320" height="160" title="Customer relationship management (CRM): process definition" alt="What is customer relationship management? Definition of the CRM process SP3 from the YaSM framework." />
<img style="display: block; float: left; margin-left: 10px; margin-right: 20px" src="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-customer-relationship-management-process.jpg" width="320" height="160" title="Customer relationship management (CRM): process definition" alt="What is customer relationship management? Definition of the CRM process SP3 from the YaSM framework." />
<meta itemprop="caption" content="Manage customer relationships | YaSM CRM | Process definition SP3" />
<meta itemprop="caption" content="Manage customer relationships | YaSM CRM | Process definition SP3" />
<meta itemprop="width" content="1050" />
<meta itemprop="width" content="1050" />
<meta itemprop="height" content="525" /></a></div>
<meta itemprop="height" content="525" /></a></div>
<div style="margin-left: 30%; color:#636363">
<div style="margin-left: 5%; color:#636363">
<p style="margin-top: 0;">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 style="margin-top: 0; word-wrap:normal;">Is&nbsp;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:&#160;&#160;Stefan Kempter&#160;<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>&#160;&#160;and&#160;&#160;Andrea Kempter&#160;<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;"/></div><p>
<p>By:&#160;&#160;Stefan Kempter&#160;<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>&#160;&#160;and&#160;&#160;Andrea Kempter&#160;<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;"/></div><p>
Line 234: Line 225:


<p><small>
<p><small>
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList">
<span itemprop="breadcrumb" itemscope itemtype="https://schema.org/BreadcrumbList">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#Process_description">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#Process_description">
<span itemprop="name">Process description</span></a>
<span itemprop="name">Process description</span></a>
<meta itemprop="position" content="1" /></span> ›
<meta itemprop="position" content="1" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#Sub-processes">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#Sub-processes">
<span itemprop="name">Sub-processes</span></a>
<span itemprop="name">Sub-processes</span></a>
<meta itemprop="position" content="2" /></span> ›
<meta itemprop="position" content="2" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#Process_outputs">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#Process_outputs">
<span itemprop="name">Process outputs</span></a>
<span itemprop="name">Process outputs</span></a>
<meta itemprop="position" content="3" /></span> ›
<meta itemprop="position" content="3" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#Process_metrics">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#Process_metrics">
<span itemprop="name">Metrics</span></a>
<span itemprop="name">Metrics</span></a>
<meta itemprop="position" content="3" /></span> ›
<meta itemprop="position" content="3" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#Roles_and_responsibilities">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#Roles_and_responsibilities">
<span itemprop="name">Roles</span></a>
<span itemprop="name">Roles</span></a>
Line 281: Line 272:
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.5">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.5">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.6">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#SP3.6">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#Process_outputs">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP3:_Manage_customer_relationships#process-inputs-outputs">
  <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process/Manage-customer-relationships-yasm-sp3.jpg" />
  <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process/Manage-customer-relationships-yasm-sp3.jpg" />
  <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-customer-relationship-management-process.jpg" />
  <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-customer-relationship-management-process.jpg" />
Line 298: Line 289:
[[Category:YaSM process]]
[[Category:YaSM process]]
<!-- --- -->
<!-- --- -->

Revision as of 16:04, 1 February 2021

share this page on LinkedInshare this page on Twittershare this page
auf Deutsch


 

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.

Fig. 1: Manage customer relationships. - YaSM customer relationship management process (CRM-Prozess) SP3. - Related with: Practice of ITIL 4 relationship management.
Fig. 1: 'Manage customer relationships':
YaSM customer relationship management (CRM) process SP3.


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. [*]
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 example) 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: Customer relationship manager

  • 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.

 

Responsibility matrix: "SP3: Manage customer relationships"
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 Author: Stefan Kempter, IT Process Maps GbR  and  Andrea Kempter Contributor: Andrea Kempter, IT Process Maps GbR, IT Process Maps.

 

Process description  › Sub-processes  › Process outputs  › Metrics  › Roles