MétaCan
Menu
Back to cohort
Record W2901803330 · doi:10.1111/1911-3846.12641

The Effect of Humanizing <scp>Robo‐Advisors</scp> on Investor Judgments*

2020· article· en· W2901803330 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueContemporary Accounting Research · 2020
Typearticle
Languageen
FieldComputer Science
TopicAI in Service Interactions
Canadian institutionsnot available
Fundersnot available
KeywordsTask (project management)Investment (military)Key (lock)Computer scienceFinanceMarketingPsychologyBusinessEconomicsManagementPolitical scienceComputer securityLaw

Abstract

fetched live from OpenAlex

ABSTRACT We examine the effect of humanizing (naming) robo‐advisors on investor judgments, which has taken on increased importance as robo‐advisors have become increasingly common and there is currently little SEC regulation governing key aspects of their use. In our first experiment, we predict and find that investors are more likely to rely on the investment recommendation of an unnamed robo‐advisor, whereas they are more likely to rely on the investment recommendation of a named human advisor. Theory suggests one reason that naming a robo‐advisor may have drawbacks pertains to the complexity of the task the robo‐advisor performs. We explore the importance of task complexity in our second experiment. We predict and find that investors are less likely to rely on a named robo‐advisor when the advisor is perceived to be performing a relatively complex task, consistent with our first experiment, and more likely to rely on a named robo‐advisor when the advisor is perceived to be performing a relatively simple task, consistent with prior research on human‐computer interactions. Our findings contribute to the literature examining how technology influences the acquisition and use of financial information and the general literature on human‐computer interactions. Our study also addresses a call by the SEC to learn more about robo‐advisors. Lastly, our study has practical implications for wealth management firms by demonstrating the potentially negative effects of making robo‐advisors more humanlike in an attempt to engage and attract users.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.004
metaresearch head score (Gemma)0.004
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.115
Threshold uncertainty score0.768

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.004
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.000
Scholarly communication0.0010.001
Open science0.0030.001
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.099
GPT teacher head0.355
Teacher spread0.256 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it