Conversation context variables are the bridge between information collected before a conversation and later Contact Center operations. Microsoft states that context variables enrich conversations with pre-conversation, channel, and custom context data. These variables can subsequently be consumed by routing rules and by representative productivity tools, including macros and scripts.

When a pre-chat survey asks the customer for information such as product, region, support category, or account type, the collected response can become conversation context. Unified routing can inspect that contextual value when determining the destination queue. After the CSR accepts the conversation, the same context remains associated with the interaction and can be referenced by a macro to populate records, launch actions, or insert contextual information.

A knowledge-article tag organizes knowledge content rather than conversation data. A static canned response has no dynamic relationship with a survey value. Queue priority influences work-item assignment order but does not preserve or expose customer-entered information.

The correct design is therefore to capture the survey response into a context variable and reuse that same contextual attribute throughout routing and representative productivity operations.

Study Guide reference: Implement channels - > Configure pre-chat surveys and context variables; configure productivity integration with macros.