Abstract
Despite increasing interest in warmth and competence as fundamental dimensions in consumers’ evaluation of service providers, prior research remains ambiguous about which dimension is more important. The current study develops a nomological framework that clarifies this ambiguity and explains whether, when, and why warmth or competence takes precedence for different outcomes in customer-service provider relationships. Combined evidence from field and laboratory studies support the notion of an asymmetric dominance, which suggests that warmth is dominant in driving outcomes that capture relational aspects (e.g., customer-company identification), whereas competence is dominant in driving outcomes that capture transactional aspects of the customer-service provider relationship (e.g., share of wallet). The findings provide first insights into the underlying mechanisms that drive this asymmetric dominance by demonstrating that relational and capability concerns mediate this process. Moreover, the current investigation identifies novel moderators that offer managers help in identifying service contexts (people vs. object care) and customer segments (differing in process and outcome service goals) for which investing in warmth or competence is more promising. Overall, displaying competence is particular effective in driving customer attraction and current operating performance, whereas displaying warmth is better suited to establish strong emotional bonds and drive customer retention.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.