Create the parameter in Nimbus

In Nimbus, create a new parameter

• Name = CustomerSurveyValue
• Default Value = EMPTY

Create the workflow in Nimbus

In Nimbus, create a Workflow with a couple of branches. We want to collect the survey responses for each branch, at the end of the branch. We store them in the Parameter CustomerSurveyValue created above. After that we make an announcement an disconnect the call.

💡 In the example we ask a first question using the Input Customer workflow activity. 

• If the customer presses 1 for "Yes", then we collect the information using the Save to Parameter activity and route to the announcement. 
• For "No" we route to the second question, and so on.

The Save to Parameter @Workflow activity is important. We want to store a JSON value in the parameter. For each branch, we write the values accordingly to the customer choice into the parameter. 

The syntax is as follows:

[
{
 "question": "Are you satisfied with our service?",
 "response": "No"
},
{
 "question": "Do you want to receive a survey per email?",
 "response": "Yes"
},
 {
 "question": "A third question",
 "response": "A third answer"
}
]

Capture the responses

Next, build a Power Automate flow which will listen to the UpdatedParameter Trigger Event and write the answers to your CRM, survey system or simply into a list.

Description	Screenshot
Start with a When a task changes state and select Parameter Updated as the event
To make sure Power Automate only runs when the “CustomerSurveyValue” parameter has been update you can add a trigger condition under settings in the When a task changes state Trigger conditions = @equals(triggerBody()?['UpdatedParameterName'],'CustomerSurveyValue')
Then initialize a new array variable Name = CustomerSurveyValue Type = Array
Now, set the contents of the array variable  Name = CustomerSurveyValue Value = json(triggerOutputs()?['body/updatedParameterValue'])
Add an Apply to each element to the flow and iterate over the variable CustomerSurveyValue. Now you can work with the data. As a reminder, the variable CustomerSurveyValue holds the following data: [ { "question": "Are you satisfied with our service?", "response": "No" }, { "question": "Do you want to receive a survey per email?", "response": "Yes" } ] In our example we update a SharePoint list with the following values: Title = Nimbus Survey Question = items('Apply_to_each')['question'] Answer = items('Apply_to_each')['response'] callChainId = triggerOutputs()?['body/callChainId'] Number = triggerOutputs()?['body/microsoftCallerId'] DisplayName = triggerOutputs()?['body/customer/displayName'] The callChainId can be used like a correlation id to identify all answers that belong together.
PUSHING SURVEY RESPONSES TO DYNAMICS CUSTOMER VOICE At this point you could also add the responses to your Dynamics Customer Voice instance using the Microsoft Dataverse Connector. We recommend implementing the push in a second step, as it could be error prone. Step 1 (this flow): Save the Nimbus responses in a table of your choice (Azure Storage Tables, Microsoft Dataverse, SharePoint, etc.) Step 2: Read the data from the table and create the entries in Dynamics Customer Voice according to the internal data structure.

Test your flow

1. Now, call the Service and make some choices to the questions.
2. We've shared the SharePoint list in a channel "Survey" on the MS Teams team. 
   1. This way, we can also post survey actions as Adaptive Cards in that channel or … 
   2. … share other customer survey related content in one centralized place.