<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="12687" 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/12687?output=omeka-xml" accessDate="2026-04-09T05:07:43+00:00">
  <collection collectionId="5">
    <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="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</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="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="74590">
              <text>Optimising lead qualification through machine learning: A customer data-driven approach</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="74591">
              <text>cold leads; decision tree; hot leads; logistic regression; machine learning; supervised ML algorithms</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="74592">
              <text>Lead generation is the process of turning an outside person or business into a customer of the business. Traditionally, marketing personnel must conduct significant follow-ups in order to convert even one potential consumer. Converting bad client leads can cause businesses to burn through cash reserves. As a result of this, it is now necessary to develop an automated system that can correctly anticipate whether or not a lead should be explored (converted to a customer or not). In this study, an attempt is made to evaluate historical data for leads produced by other businesses in order to train and validate a machine learning (ML)/deep learning (DL) model and test it against real-world characteristics to categorise them as hot leads (convert to customers) or cold leads (failed leads). This can be achieved by employing ML algorithms, low codeno code libraries, such as PyCaret in Python, and can be used to make predictions regarding probable lead creation, propensity to convert generated leads and optimal actions on the leads by communications teams. Supervised ML algorithms such as logistic regression, decision trees, random forests and other models using a Python library were built to score leads for identifying potential conversions. With good and broad lead-scoring models in place, businesses can optimise their CTI actions on the basis of lead prioritisation and let go of non-prospect leads at the right time to cut costs and enable efficiency. The result of this study reveals that 52 per cent of the sample of 74,779 leads are cold leads and 48 per cent are hot leads that are sales qualified. The leads are qualified using the lead score matrix. This method can aid digital businesses to remove unqualified leads and manage leads better, and therefore improve the quality of the leads sent to clients. This, in turn, will improve conversion rates for individual customers. These increased conversion rates will enhance the business strategy of digital marketing firms.  Henry Stewart Publications.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="74593">
              <text>Helen J.V.L.; Moorthy V.; Sai C.; Joji B.</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="74594">
              <text>Applied Marketing Analytics, Vol-10, No. 3, pp. 255-270.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="74595">
              <text>Henry Stewart Publications</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="74596">
              <text>2024-01-01</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="74597">
              <text>&lt;a href="https://doi.org/10.69554/ETXF7251" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.69554/ETXF7251&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85213383861&amp;amp;doi=10.69554%2FETXF7251&amp;amp;partnerID=40&amp;amp;md5=049aa95eff0da5dc89531c56444bf6cb" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85213383861&amp;amp;doi=10.69554%2fETXF7251&amp;amp;partnerID=40&amp;amp;md5=049aa95eff0da5dc89531c56444bf6cb&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="74598">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="74599">
              <text>ISSN: 20547544</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="74600">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="74601">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="74602">
              <text>Article</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="74603">
              <text>Helen J.V.L., School of Business and Management, Christ University, Kengeri Campus, Mysore Road, Karnataka, Bangalore, 560074, India; Moorthy V., School of Business and Management, Christ University, Kengeri Campus, Mysore Road, Karnataka, Bangalore, 560074, India; Sai C., Enterprise Solution Architect, Airtel Business, India; Joji B., School of Business and Management, Christ University, Kengeri Campus, Mysore Road, Karnataka, Bangalore, 560074, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
