Display custom context in Conversation summary
Omnichannel for Customer Service offers a suite of capabilities that extend the power of Dynamics 365 Customer Service Enterprise to enable organizations to instantly connect and engage with their customers across digital messaging channels. An additional license is required to access Omnichannel for Customer Service. For more information, see the Dynamics 365 Customer Service pricing overview and Dynamics 365 Customer Service pricing plan pages.
Important
Power Virtual Agents capabilities and features are now part of Microsoft Copilot Studio following significant investments in generative AI and enhanced integrations across Microsoft Copilot.
Some articles and screenshots might refer to Power Virtual Agents while we update documentation and training content.
The data type of the context variables is a JSON object with two properties—isDisplayable
and Value
. The JSON object has the following schema.
{
"type": "object",
"properties": {
"isDisplayable": {
" description": " Context variable should display in agent UI or not",
"type": "boolean"
},
"Value": {
" description": " Context variable value pass through bot , this can be string Boolean or number",
"type": "string or Boolean or Number"
}
},
"required": [ "isDisplayable", "Value" ]
}
The input value for isDisplayable
is Boolean (true or false). The input value for Value
can be Boolean, String, or Number.
To display the context variables in the Conversation Summary Control of conversations for Copilot Studio and Azure bots, use the isDisplayable
property in the body of setContextProvider method.
Here's an example:
{\"isDisplayable\":\"true\"," +"\"Value\":\"context variable value as string\"}
The isDisplayable
property, when set to true
, will display the context variables on the third tab of the Conversation Summary Control for a conversation. The Value
property of the JSON object includes the user response or any other information in string, Boolean, or number format.
See also
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for