Can Customers Detect Script Usage in Service Encounters?
Bibliographic record
Abstract
Service scripts are predetermined guides for employees to follow when delivering service to customers. Some services require employees to strictly follow a script, whereas others use scripts more flexibly, if at all. Extant research regarding service scripts in the domain of service operations has mainly addressed the topic from more of a process view as a control mechanism for the encounter but minimal research has examined customer perceptions of scripted service. The authors examine a pivotal first question, which is if customers can detect different approaches to script use. To answer the question, the authors conducted a video experiment of face-to-face service encounters in the hospitality industry. The results indicate that customers can detect degrees of script use across both standardized and customized encounter types. This work serves as initial empirical evidence that customers are indeed capable of detecting subtleties in scripting approaches in different service situations and supports that script level is an important service design construct for research. Furthermore, the authors highlight the use of a video experiment as an innovative methodology for assessing customer perceptions of intangible aspects to services in a realistic setting. One implication of this study is that managers need to assess the impact that different script levels have on customer perceptions of various service performance measures. Managers should also consider the effect script detection has on customer perceptions of the service experience and service brand to assure their script approach aligns with the organization’s service strategy.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.040 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.004 | 0.004 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".