Mapping Wizu responses to Salesforce fields

Learn how to update Salesforce fields with question response data

Updated over a week ago

Now your accounts are connected you can start to explore the incredible range of options that both Wizu and Salesforce offer. If this is the first time you are using Wizu, we would suggest creating a demo survey initially to experiment with the integration options. Add a couple of questions such as first name and last name from the text questions drop down list. Save your updated survey and then go to Workflows.

This is where you will create and edit all Salesforce mappings.

Choose your Salesforce integration environment from the drop down and then click the + Salesforce Action button to get started.

Your first option is to choose either the ‘Create’ or ‘Update’ action. These are pretty self-explanatory – click create to create a new record and update to, yes you guessed it, update a record.

Next you need to select your Object. The drop down will display all available objects in Salesforce. If you create any custom objects then these will also appear in this drop down.

Once you choose an object, such as ‘Lead’ you will then be shown the required fields that you need to map for this object. Wizu will automatically look for any matches between your conversation questions and the Salesforce field and set this mapping for you. Which is nice isn’t it? Then any other required fields can be mapped manually. You cannot delete a mandatory field mapping but you are able to edit this.

In the top right of this section you will see an ‘Auto Map’ button. This will add every available field in this object and automatically map any matches. The rest can be mapped manually or deleted if not required.

You can also click the + Mapping button at the bottom of this section in order to manually map a source and field.

Manual Mapping

There are a number of different ways to map your survey responses and other data to Salesforce. You can map responses to an existing Salesforce record or create a new record. Once you have set up your survey mappings, every new response received will utilize these rules and the data will be saved in the relevant Salesforce fields. When you have selected your ‘Action’ and ‘Object’ you will then be shown the required fields for this object. You will need to set the ‘Type’ and ‘Source’ to match the Salesforce field. There are 4 different types available which we will run through below.

1. Question mapping – Here you will map a specific question response to the field in Salesforce. The ‘Source’ field will show the available answer options for you to select from. For example, if you have added an organization and last name text question to your conversation these can simply be mapped to the relevant field in Salesforce.

Each field within Salesforce has a defined data type such as Number, PickList, TextArea etc. Each of these fields will be expecting data of a certain type, so you can’t put a long string of text in a field that is expecting a number. Below is a guide to the supported survey response mappings.

2. Merge Field Parameters – This allows you to select a field that you have sent through to the survey via your invitation URL merge tags. This can be useful for linking a response back to a Salesforce record by including a unique reference such as the contactid.

Notice how the URL at the bottom of the screenshot is updated to show the merge tag. If I add an additional merge field you can see how you can start building your URL templates in order to pass this information through to Wizu and the connect individual responses back.

3. Conversation property – The conversation property field allows you to pass through information about the conversation/survey to a Salesforce field of your choice. This will allow you to create custom workflows or reports based around the conversation properties.

4. Fixed Text – The final ‘Type’ available is ‘Fixed Text’. This allows you to hard code a specific value across all responses. Again you will need to ensure you are mapping to a field with the correct data type.


Did this answer your question?