<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="13466" 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/13466?output=omeka-xml" accessDate="2026-05-04T13:53:54+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="85441">
              <text>Does robotic service quality determine robotic restaurant diners engagement behaviors? Role of customer engagement andattachment to the restaurant</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="85442">
              <text>Attachment and customer engagement behaviors; Customer engagement; Robotic restaurant; Service quality</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="85443">
              <text>Purpose: Robotic restaurants are very novel, and service robots in these restaurants are identified as offering unique advantages in terms of efficiency, tireless service and potentially lower operational costs. However, studying customer engagement with the robots can reveal aspects of robotic service that resonate with diners. Understanding how diners interact with robots can help create a more engaging and enjoyable atmosphere, bringing more business to restaurants. Building on the stimulus-organism-response (SOR) theory and place attachment theory, the purpose of this paper is to study the impact of the robotic service quality (RSQ) on the customer attachment to the robotic restaurant with the mediating role of the different dimensions of the customer engagement, like the Absorptive Attention, Enthusiastic Participation and Social Connection. Subsequently, the impact of the customer attachment to the robotic restaurant on different dimensions of customer engagement behaviors like augmenting, co-developing, influencing and mobilizing behaviors was also studied. Design/methodology/approach: The cross-sectional data from 786 robotic restaurant diners in India who answered the self-administered structured questionnaires is utilized for this descriptive study. The study employed a purposive sampling strategy. The SMART-PLS 4.0 program was used to run structural equation modeling and analyze the data. Findings: The results indicate that customer engagement dimensions like Absorptive Attention, Enthusiastic Participation and Social Connection differentially mediate the relationship between RSQ and customer attachment with the robotic restaurant. Customer attachment to the restaurant and the robotic services subsequently positively impact customer engagement behaviors. Research limitations/implications: The study relied upon cross-sectional data from the Indian population above 18years to test the proposed model. Further studies could test the model across different populations to generalize the study results. Originality/value: This study addresses the need to investigate robotic restaurant diners engagement behaviors. By testing place attachment theory and the SOR framework, this study is the first to show that RSQ will impact the customer attachment with the robotic restaurant and that different dimensions of customer engagement mediate the relationship. It also validates the previous research findings that customer engagement is not a single global construct, and different sub-dimensions are to be explored. This study is also the first to show customer attachment to the robotic restaurant will impact customer engagement behaviors differently.  2024, Emerald Publishing Limited.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="85444">
              <text>Veera Raghavan D.R.</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="85445">
              <text>TQM Journal</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="85446">
              <text>Emerald Publishing</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="85447">
              <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="85448">
              <text>&lt;a href="https://doi.org/10.1108/TQM-04-2024-0157" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1108/TQM-04-2024-0157&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85206371543&amp;amp;doi=10.1108%2FTQM-04-2024-0157&amp;amp;partnerID=40&amp;amp;md5=f3033a12bd4b49788b118a9bafd97abe" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85206371543&amp;amp;doi=10.1108%2fTQM-04-2024-0157&amp;amp;partnerID=40&amp;amp;md5=f3033a12bd4b49788b118a9bafd97abe&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="85449">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="85450">
              <text>ISSN: 17542731</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="85451">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="85452">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="85453">
              <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="85454">
              <text>Veera Raghavan D.R., School of Business and Management, CHRIST (Deemed to be University), Bangalore, India, Amrita School of Business, Amrita Vishwa Vidyapeetham, Coimbatore, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
