Difference between revisions of "Kevoe-Feldman-Robinson2012"
AndreiKorbut (talk | contribs) m |
AndreiKorbut (talk | contribs) |
||
Line 10: | Line 10: | ||
|Number=2 | |Number=2 | ||
|Pages=217–241 | |Pages=217–241 | ||
− | |URL= | + | |URL=https://journals.sagepub.com/doi/abs/10.1177/1461445612439958 |
|DOI=10.1177/1461445612439958 | |DOI=10.1177/1461445612439958 | ||
|Abstract=This article describes an adjacency-pair organized course of action in the institutional context of customers calling an electronics repair facility to request the status of equipment they have previously sent in for repair. Relative to the majority of adjacency-pair sequences described in previous research, this course of action is rare in that it is essentially (vs contingently) composed of three (vs two) turns, including status solicitation, status response, and acceptance/rejection of status response. After defending this finding, we situate and discuss its significance relative to prior research – in both ordinary and institutional contexts – on adjacency-pair sequence organization, including implications for sequence-based relevance rules, such as preference organization. Finally, we outline a possible general explanation for why some initiating actions set in motion essentially three-turn (vs two-turn) courses of action, and offer a candidate example in ordinary conversation. | |Abstract=This article describes an adjacency-pair organized course of action in the institutional context of customers calling an electronics repair facility to request the status of equipment they have previously sent in for repair. Relative to the majority of adjacency-pair sequences described in previous research, this course of action is rare in that it is essentially (vs contingently) composed of three (vs two) turns, including status solicitation, status response, and acceptance/rejection of status response. After defending this finding, we situate and discuss its significance relative to prior research – in both ordinary and institutional contexts – on adjacency-pair sequence organization, including implications for sequence-based relevance rules, such as preference organization. Finally, we outline a possible general explanation for why some initiating actions set in motion essentially three-turn (vs two-turn) courses of action, and offer a candidate example in ordinary conversation. | ||
}} | }} |
Latest revision as of 09:18, 30 November 2019
Kevoe-Feldman-Robinson2012 | |
---|---|
BibType | ARTICLE |
Key | Kevoe-Feldman-Robinson2012 |
Author(s) | Heidi Kevoe-Feldman, Jeffrey D. Robinson |
Title | Exploring essentially three-turn courses of action: An institutional case study with implications for ordinary talk |
Editor(s) | |
Tag(s) | EMCA, Institutional interaction, Turn Organization, Service Encounter |
Publisher | |
Year | 2012 |
Language | |
City | |
Month | |
Journal | Discourse Studies |
Volume | 14 |
Number | 2 |
Pages | 217–241 |
URL | Link |
DOI | 10.1177/1461445612439958 |
ISBN | |
Organization | |
Institution | |
School | |
Type | |
Edition | |
Series | |
Howpublished | |
Book title | |
Chapter |
Abstract
This article describes an adjacency-pair organized course of action in the institutional context of customers calling an electronics repair facility to request the status of equipment they have previously sent in for repair. Relative to the majority of adjacency-pair sequences described in previous research, this course of action is rare in that it is essentially (vs contingently) composed of three (vs two) turns, including status solicitation, status response, and acceptance/rejection of status response. After defending this finding, we situate and discuss its significance relative to prior research – in both ordinary and institutional contexts – on adjacency-pair sequence organization, including implications for sequence-based relevance rules, such as preference organization. Finally, we outline a possible general explanation for why some initiating actions set in motion essentially three-turn (vs two-turn) courses of action, and offer a candidate example in ordinary conversation.
Notes