Home » How Variables improve user experience in AI Agents
How Variables improve user experience in AI Agents
AI Agents are now a part of our everyday reality. They can improve business processes, get work done, and save you a lot of time. One of the most important aspects of their design is how they communicate with the end user – this is what builds the user experience.
Think about an old IVR system where you had to go through an entire conversation just to find what you needed: “For English, press 1. For Polish, press 2. For orders, press 1. For product information, press 2.” And all you really wanted was to check your order status.
This illustrates how much the way an AI interacts with users can affect satisfaction.
Interaction types in Copilot Studio
In Copilot Studio, there are several ways to interact with the end user:
1. Topics with questions
Asking questions one by one.
2. Adaptive Cards
Using Adaptive Cards
3. AI and Prompt Actions
The newest method is using AI and Prompt Actions. With AI, you can extract all needed information directly from the user’s request, making the interaction feel more like a conversation with a human.
Extracting all information from the user’s request with AI.
Choosing the right method
- Sometimes, there’s no need to use AI Actions (which can affect usage costs).
- Other times, AI may be a better fit than Adaptive Cards.
- And sometimes, all you need is to ask two simple questions.
Efficient communication through Variables
Another important element of smooth communication with your AI Agent is avoiding repetitive questions.
Your Agent should remember what the user has already shared – and this is where variables come in.
Topic Variables
These are custom variables created and used within a single topic.
For example, if a user provides their information in one topic, the Agent won’t remember it once the conversation switches to another topic.
Global Variables
To store information across topics, use Global Variables. They can also receive values from external sources and maintain context throughout the conversation.
System Variables
Copilot Studio also includes built-in variables that store user information like first name, last name, and email address.
You don’t need to ask for these: they’re already stored in the System Variables.
Context Variables
When your Agent supports a Model-Driven App (for example, Dynamics 365), you can also use Context Variables.
These help the Agent understand what the user is referring to.
For instance, if a user is viewing an Account form and wants to see related orders, they can simply ask: “Show me all open orders for this account”, instead of typing the full name like “Show me all open orders for Account XYZ.”
The Agent knows what “this” refers to, because the context variable tells it that the user is currently on the Account form with ID:12344.
Why Variables matter
All these variable types work together to make your AI Agent more human-like and context-aware. Even small improvements in user experience can significantly impact satisfaction.
Combined with previous insights about forms of communication (covered in earlier blog posts), this creates a complete guide to building the perfect Virtual Assistant.
Summary: Variable types and Data types in Copilot Studio
Variable type
System Variables
Scope
Description
How it's created / used
Topic Variables
Global Variables
Environment Variables
Defined in Power Platform Admin Center.
Session Variables
Data type
String
Description
Boolean
Number
Numeric values.
DateTime
Record
Table
Choice
Blank
Benefits of using Variables
Variables make interactions personalized, efficient, and contextual. Here’s how they enhance your Copilot (for example, in Dynamics 365 Sales):
Benefit
Personalization
How Variables help
Example in Dynamics 365 Sales
Context awareness
Dynamic responses
Efficient data handling
contactEmail used for both follow-up email generation and CRM update.
Automation integration
Error reduction
Decision making
If customerSentiment = negative, Copilot escalates to support.
See the latest insights from Netwise
15 years at Netwise: a conversation with our Chief Delivery Officer
In this article, you’ll learn about Adrian Wieczorek’s journey from developer to Chief Delivery Officer and how Netwise has evolved over the past 15 years.
Read moreSimplifying AI Agent Integration with Model Context Protocol
In this article, you’ll learn how MCP connects Copilot Studio agents with external systems for faster deployment, lower costs, and greater autonomy.
Read moreHow Variables improve user experience in AI Agents
Learn how variables enhance AI Agent interactions and see how different variable and data types work in Copilot Studio.
Read more

