Contact rate is the share of orders in a period that generate at least one inbound customer-service contact across the brand’s support channels.
Pick orders or shipments and label it — same period can produce two different contact rates depending on the denominator.
The inverse — orders per contact — is the same number recast for capacity planning, the form a support-ops lead uses when staffing against ticket load (“one contact per N orders”).
The numerator has to cover the actual channel surface. Inbound contacts arrive over email, chat, phone, SMS, and social DMs; a brand counting only what one ticketing system ingests underreports whenever Instagram DMs, in-app chat, or a separate phone queue live in another tool. The number moves as much with how contacts are counted as with what customers do.
The denominator choice — orders versus shipments — is the other definitional fork. Orders matches commercial reporting and is the figure leadership already cites, which makes it the default for cross-functional reads. Shipments better isolates fulfillment-driven contacts (WISMO, damages, late deliveries) because a single order with three shipments generates three chances for a shipping-triggered contact. Pick one, label it on the dashboard, and don’t mix the two across teams — the same period can produce two different “contact rates” depending on which denominator the analyst pulled.
Gross and net are the next layer. Gross counts every inbound ticket; net deduplicates by order or customer, so one frustrated customer emailing three times about one delayed order counts once. Net is the truer signal of unique customer demand; gross is what the staffing model reads, because each touch consumes an agent’s time. Brands that report only gross tend to overstate “issue volume” — the numerator counts touches while the denominator counts orders.
Contact-reason mix shapes interpretation. For most DTC brands the largest single reason is WISMO (“where is my order”), followed by returns and exchanges, sizing and fit, and pre-purchase product questions. Category shifts the mix — apparel skews toward sizing, electronics toward pre-purchase product questions — so cross-brand benchmarks read as ranges, not as targets.
The reason WISMO dominates is also what makes contact rate useful beyond the CX dashboard: it moves with fulfillment health before the slower metrics do. A 3PL slipping on ship-by SLAs lifts WISMO volume within a day or two of the missed promise; the same slip shows up in return rate and refunds days or weeks later, once customers actually receive late or damaged product. That lead-time is the mechanism that ties contact rate to cost-of-CX: lower fulfillment SLA → more WISMO → higher contact rate → more support hours per order. Contact rate sits next to CSAT on most CX dashboards but reads a different axis — contact rate is the volume and cost lens, CSAT the quality lens — and the two move independently often enough that a brand can drive contact rate down while CSAT slides if the resolution path got worse.