Short answer
A contact driver is the underlying reason a customer reaches out, the root cause behind a support interaction rather than the channel or symptom. It is the why behind the volume: a confusing checkout step, a delayed shipment, an unclear billing line.Support teams use contact drivers to understand and reduce their workload. If 30 percent of tickets trace to one driver, the fix may live outside support entirely, in the product, the policy, or the shipping partner. Naming drivers turns a flood of individual tickets into a small set of addressable causes. A contact driver is closely related to intent: intent is what the customer wants in a given message, while a contact driver is the recurring root cause that generates many such intents.
At Aide, the AI platform for customer service, contact drivers surface directly from the auto-discovered Customer Intent Map. Because intents are clustered from real conversations into a three-level taxonomy, the dominant drivers become visible without manual tagging, and Intent Coverage Rate shows which ones are resolved by verified automation versus still landing on the team.
Automation takes on a driver only once its intents are tested and verified; a high-volume driver is never auto-answered on a guess. Drivers stay legible after automation too, which is what lets people push fixes upstream instead of absorbing the same root cause forever.