Mind the Style: Impact of Communication Style on Human-Chatbot Interaction

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2602.17850v2 Announce Type: replace-cross Abstract: Conversational agents increasingly mediate everyday digital interactions, yet the effects of their communication style on user experience and task success remain insufficiently understood. Addressing this gap, we report a between-subject user study in which participants interacted with one of two versions of a chatbot called NAVI, which assisted them in an interactive map-based 2D navigation task. The two chatbot versions were designed to differ primarily in communication style: one used a friendly and supportive tone, while the other used a direct and task-focused tone. We also included a control condition where participants did not interact with a chatbot but received the step-by-step navigation instructions. The friendly chatbot significantly increased users' communication satisfaction and was associated with higher task success than the direct chatbot. However, participants in the control condition achieved the highest task success overall, suggesting that chatbot interaction may introduce overhead in tasks that can be completed effectively using straightforward instructions. We did not find significant evidence that gender moderated the effects of communication style, although exploratory gender-stratified analyses suggested patterns that warrant further investigation. Finally, we found limited evidence of global linguistic accommodation, with only selective feature-level alignment. These findings suggest that chatbot communication style influences users' perceptions of conversational agents and may improve …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2602.17850
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.