Research question and scope

Published September 8, 2026.

This study asks how documented channel priority rules relate to wait time, duplicate contact, transfer, and completion. It covers eligible customer journeys in a defined operation and window. It does not rank channels universally or test whether one channel causes a better outcome.

Methodology

Create a pseudonymous journey identifier that links permitted contacts about the same issue. Record channel, receipt time, assigned priority, priority reason, queue entry, first meaningful response, transfers, promised checkpoints, disposition, and later contact. Preserve original contacts while analyzing the linked journey. Stratify by issue family and customer-risk rule. Audit a sample of automated links and priority overrides.

Measures and analysis

Report contact and journey counts, duplicate-channel share, response-time distributions, transfer rate, completion, and repeat contact during a fixed follow-up period. Compare channels only within similar issue and priority groups. Show missing links and unresolved journeys. A faster channel may reflect simpler work, different hours, or stricter eligibility rather than the channel itself.

Limitations and inference limits

Identity rules may fail to link contacts, while shared accounts can create false matches. Customers self-select channels, and operating hours differ. Completion fields may not reflect the customer's view. Findings apply to the sampled system and rules. They do not establish legal compliance, customer preference, or causal advantage.

Sources

  1. NIST Privacy Framework
  2. US Government Accountability Office, Assessing Data Reliability
  3. Federal Communications Commission Consumer Guides
  4. NIST Engineering Statistics Handbook