The intent is what the customer wants; entities are the specifics the request carries. In "cancel order 4817 and refund it to my original card", the intent is cancel my order. The entities are the order number and the refund destination. Intent and entity together turn a message into something a system can act on: one names the goal, the other supplies the details.
Resolution needs both, because they do different jobs. Intent selects the procedure: cancel-order triggers a different resolution path than change-address or where-is-my-order. Entities fill that procedure's parameters: which order, which address, what date, what amount. Entity extraction is the step that pulls those specifics out of natural language, reading "next Tuesday" as a date and "my work address" as a location, so the procedure runs on real values instead of guesses. In conversational AI, entities are the bridge between free text and structured action.
Systems that have one without the other fail in predictable ways. Detect intent vs entity extraction alone, and the system knows what to do but does it to the wrong thing: the right cancellation procedure aimed at the wrong order, the right refund for the wrong amount. Extract entities without intent, and the system holds perfect data with no idea what to do: it has the order number, the date, and the amount, and still cannot choose an action. The first failure damages customers; the second just describes them.
Intent vs entity at a glance
| Dimension | Intent | Entity |
|---|---|---|
| Question it answers | what does the customer want? | what specifics does the request carry? |
| Example | cancel my order | order 4817, next Tuesday, the work address, the amount |
| What it drives | which procedure runs | the parameters the procedure runs with |
Aide, the agentic AI platform for customer experience, is built on this pairing. Every inbound conversation is classified by intent against the Customer Intent Map, and the entities it carries are read against live systems before anything runs: the order number is checked against the real order, the address against the account on file, the amount against the actual invoice. The procedure that executes is the one the intent selected, filled with verified values rather than extracted guesses.
Frequently asked questions
- What is entity extraction in customer service AI?
- Entity extraction is identifying the specific values inside a customer message: order numbers, dates, addresses, amounts, product names. It converts free text into structured parameters a resolution procedure can use, and it works best when those values are verified against live systems rather than taken at face value.
- Can a message have one intent and many entities?
- Yes, and most real requests do. "Change my delivery to next Tuesday at my work address" carries one intent, change delivery, with two entities, a date and a location. A message can also carry more than one intent, each with its own entities, which is why classification runs before extraction.