68/100

Moderate evidence

GainPublished recordScienceGood Space

How Chatbot Advice Shapes Travel Intention: Comparing Social-Oriented and Task-Oriented Responses to Social Media-Induced Travel Anxiety

Truvace record
TRV-2026-3006raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
e65ed30348d2…check it

As social media becomes embedded in travel decision-making, idealized portrayals, information overload, and difficulty assessing content authenticity can trigger travel anxiety. Although chatbots are widely used in travel planning, prior research has focused mainly on adoption and functional performance, leaving it unclear whether their communication style can address users’ emotional responses. Drawing on cognitive appraisal theory, we compared social-oriented and task-oriented chatbot responses across three ex…

The gain

In three experiments where participants imagined browsing travel content on social media, those who read a social-oriented chatbot response reported higher travel intention than those who read a task-oriented one, and in Study 2 also reported lower travel anxiety.

What this doesn’t fix

Participants only imagined browsing travel content on social media rather than making real travel decisions, so the results reflect hypothetical scenarios.

Sources

1 on file
  1. Behavioral Sciencesdoi:10.3390/bs16112164
    Peer-reviewed2026-11-14

Cite this record

v1

Truvace Impact Record TRV-2026-3006, v1: “How Chatbot Advice Shapes Travel Intention: Comparing Social-Oriented and Task-Oriented Responses to Social Media-Induced Travel Anxiety.” Truvace, 2026-11-18. /record/TRV-2026-3006 (accessed on the day you copy it). sha256 e65ed30348d23b7f…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1e65ed30348d2…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-3006 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.