A sub-intent is a child intent in a hierarchical intent taxonomy: the specific version of a broader customer request. The parent intent names the category, like order changes. The sub-intent names the exact goal inside it, like cancel order or change shipping address.
The distinction matters because automation lives or dies at this level of granularity. "Billing" is not one thing a system can safely act on. A duplicate charge, a plan downgrade, and an invoice copy request need three different resolution paths and three definitions of done. Flat topic lists that treat billing as a single intent force one generic workflow onto all of them. Specificity, not breadth, is what makes an intent automatable. The pattern holds in any queue: shipment exception splits into carrier delay and failed delivery, payment issue into dispute and payment status.
Granularity also makes measurement honest. Topic-level reporting says billing volume is up. Sub-intent reporting says duplicate charge contacts doubled after the last release. One is a mood, the other is a fixable cause.
Intent vs sub-intent at a glance
| Dimension | Intent | Sub-intent |
|---|---|---|
| Granularity | the category of request | the exact goal inside it |
| Example | order changes | cancel order, change shipping address |
| What automation attaches to | only when one path fits every child | the usual level: one clear resolution path |
| Risk when wrong | one generic workflow, confidently wrong | a misread triggers the wrong resolution path |
Aide, the agentic AI platform for customer experience, auto-discovers a three-level Customer Intent Map from real conversations, so the hierarchy reflects what customers actually ask, not what a team guessed in a workshop. Automation is deployed at the level where the resolution path is unambiguous: sometimes the parent intent, usually the sub-intent.
Verification happens at the same granularity. Each sub-intent is approved on its own terms, its resolution path confirmed against past conversations before it goes live, and automation is recorded at the sub-intent level, so the team's picture of customer demand keeps its full resolution instead of blurring into topic-level summaries.
Frequently asked questions
- What is a sub-intent in intent classification?
- The more specific label a message resolves to beneath its broad category. A classifier that stops at the parent, like *shipping*, can only route. One that reaches the sub-intent, like *change delivery address*, can trigger the exact resolution.
- What is the difference between an intent and a sub-intent?
- Position in the hierarchy. An intent can sit at any level of the taxonomy. A sub-intent is always the child of a broader intent: the specific goal inside the category.
- Is a sub-intent the same as multi-intent detection?
- No. A sub-intent is depth: one request described more precisely. Multi-intent detection is breadth: one message that contains two or more separate requests.