<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="25367" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/25367?output=omeka-xml" accessDate="2026-06-19T04:12:11+00:00">
  <collection collectionId="7">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3139">
                <text>Faculty Publications</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="28">
    <name>Conference Paper</name>
    <description>Faculty Publications- Conference Papers</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="249172">
              <text>Sasikiran Angara, V.; Manu, K.S.; Kumar Chandar, S.; Iyer, Lakshmi Shankar</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="249173">
              <text>Intelligent Analytical Framework to Improve Customer Retention in the SaaS Industry</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="249174">
              <text>01-01-2026</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="249175">
              <text>Smart Innovation, Systems and Technologies;Volume;454 SIST;pp.121-135</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="249176">
              <text>&lt;a href="https://doi.org/10.1007/978-3-032-07837-7_10" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-3-032-07837-7_10&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105036714049?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105036714049?origin=resultslist&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="249177">
              <text>Sasikiran Angara V., School of Management, CHRIST (Deemed to be University), Karnataka, Bengaluru, India; Manu K.S., School of Business and Management, CHRIST (Deemed to be University), Karnataka, Bengaluru, India; Kumar Chandar S., School of Business and Management, CHRIST (Deemed to be University), Karnataka, Bengaluru, India; Iyer L.S., School of Business and Management, CHRIST (Deemed to be University), Karnataka, Bengaluru, India</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="249178">
              <text>In the software as a service (SaaS) sector, churn is a crucial indicator as it directly affects a businesss earnings, prospects for expansion, and viability over time. Because SaaS companies mostly rely on recurring income from subscriptions, high churn rates can be detrimental to their operations. Customer retention is crucial for SaaS companies as it is frequently more profitable and cost-effective than bringing on new customers. Retention expenses and efforts can be decreased by focusing on an appropriate set of customers. This study focuses on an intelligent analytical framework that uses machine learning and artificial intelligence techniques to find the ideal group of customers for a SaaS-based organization to retain. The previous papers concentrated on either classification or survival analysis to determine the probabilities of churn. A few studies used explainable AI models to improve the predictability of the model predictions. Not having a holistic prediction model and retention strategies provides the research gap for this study. The proposed methodology used feature selection models to identify the most significant drivers of churn, and the most popular predictive models, like logistic regression, random forest, support vector machine, and neural networks, are applied to the training set. The likelihood of churn is calculated by using classification models. The Kaplan-Meier estimate is used for survival analysis to determine the odds of survival based on the tenure of each account. Lastly, the prediction models interpretability is enhanced by using explainable AI models like SHapley Additive exPlanations (SHAP) and Local interpretable model-agnostic explanations (LIME). The neural networks model gave the best accuracy of 71% for the classification model, which provided the probability of churn and the likelihood of survival, has been predicted by Survival Analysis. Explainable AI models have identified the most important features that the model considers when arriving at the probability. This enabled the company to segment the data based on the probabilities of churn and survival, and the feature importance and respective retention strategies have been planned for each segment. By implementing the suggested analytical methodology, the business may determine which customers are most important to target with customer retention strategies.  The Author(s), under exclusive license to Springer Nature Switzerland AG 2026.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="249179">
              <text>Churn analysis; Explainable AI; Machine learning predictive models; SaaS; Survival analysis</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="249180">
              <text>Springer Science and Business Media Deutschland GmbH</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="249181">
              <text>ISSN: 21903018; ISBN: 978-303207836-0;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="249182">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="249183">
              <text>Conference paper</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="249184">
              <text>Restricted Access; Hardcopy may be available in the library</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="249185">
              <text>online</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
