Zonka Feedback's native Salesforce integration gives you a bidirectional, real-time connection between your CRM and your customer feedback program. You can push survey response data into Salesforce objects and pull Salesforce events to automatically trigger surveys — all without writing a single line of code.
This guide covers everything from initial authentication to advanced outbound message triggers, managed package setup, and workflow automation.
With Salesforce and Zonka Feedback, you can:
Sync survey responses to any Salesforce object (Contact, Lead, Opportunity, Case, Account, and more)
Create or update Salesforce records automatically when a response is received
Trigger Email and SMS surveys from Salesforce events (new contact, case closed, deal won, etc.)
Set up Salesforce Outbound Messages via Flow to fire surveys at the perfect moment
Capture NPS, CSAT, and CES scores against the Contact object via Managed Mapping
Run AI sentiment analysis and sync sentiment values back to Salesforce
Add location and tag data to responses and see them in Salesforce
Use Salesforce Sandbox for safe testing before going live
In this article, you will learn
Plan & Account Requirements
Requirement | Details |
Salesforce Account | Any paid Salesforce plan (including Essentials, Professional, Enterprise, Unlimited) |
Zonka Feedback — Custom Mapping | Any Zonka Feedback plan |
Zonka Feedback — Managed Mapping | Growth plan or above |
Salesforce Sandbox Testing | Available on all plans — connect Sandbox account instead of Production |
Outbound Messages / Flow | Requires Salesforce Workflow Rules or Flow (Enterprise edition or above recommended) |
Salesforce AppExchange Package | Required only for Managed Mapping; free to install |
⚠️ Salesforce Workflow Rules Deprecation Notice Salesforce has deprecated Workflow Rules in favor of Flow Builder. If your org runs on newer Salesforce editions, you should use Record-Triggered Flows to fire Outbound Messages. This guide covers both approaches. |
Part 1 — Connecting Your Salesforce Account
All integration types (Custom Mapping, Managed Mapping, and Outbound Triggers) begin with the same Salesforce authentication step. You only need to authenticate once per Salesforce org.
Step-by-Step: Connect Salesforce to Zonka Feedback
Log in to Zonka Feedback and go to Surveys from the left sidebar.
Select the survey you want to integrate. Open the Integrations tab from the top navigation.
Locate Salesforce in the integrations list and click Connect.
On the Salesforce Integration Detail Page, choose your mapping type: Custom Mapping or Managed Mapping. (You can change this later.)
You will be redirected to the Salesforce OAuth authorization page. Enter your Salesforce credentials.
First-time login: Salesforce will send a one-time OTP to the Salesforce account owner's email. Enter this OTP to complete authentication.
Once authenticated, you are redirected back to Zonka Feedback with your Salesforce account connected.
💡 Tip: Connecting a Sandbox Account
To test your integration safely before going live, you can connect your Salesforce Sandbox account instead of your Production org.
On the Salesforce Integration Detail Page, click 'Connect Salesforce Account' and choose Sandbox from the options. The Sandbox integration works identically to the Production integration and lets you validate all mappings and triggers before flipping to live.
Switching from Sandbox to Production
Once you've finished testing in a Sandbox org, you can move the whole configuration to Production without setting it up again — mappings, mapping conditions, email trigger configuration and synced users all carry across. The switch applies to one survey at a time.
⚠️ The switch cannot be undone. If you authorise the wrong org, the only fix is to remove the integration and start over. Check the org name and ID on the confirmation screen before continuing.
Before you switch: you must be an Account Owner or Admin, have your Production Salesforce credentials to hand, and — if you use Managed Mapping — have the Zonka Feedback package installed in the Production org. Ideally the objects, fields and Salesforce users you used in Sandbox should also exist in Production; anything missing is flagged afterwards.
Steps
Open the survey and go to Integrations → Salesforce.
Click Switch to Production, then Continue to Salesforce.
Sign in to your Production org and approve access.
Check the org name, ID and username shown, then confirm. Click Cancel here if it's the wrong org — nothing has changed yet.
If you cancel or close the browser before the final confirmation, your survey stays on Sandbox.
What happens next
We check every object, field and user your configuration refers to against your Production org, then show a summary.
In Production | Result |
Everything matches | Mapping stays active and syncs as before |
Field missing, type changed, or inaccessible to your Salesforce user | That field is set to No Mapping; the rest of the mapping keeps working |
Picklist value missing | That value is set to No Mapping; other values unaffected |
Target object missing, or the Managed Mapping package isn't installed | Mapping set to Inactive and can't be edited until resolved |
Every field unresolved, or a Salesforce-required field unmapped | Mapping set to Inactive |
Record Types and Salesforce users | Matched by name and email rather than ID and relinked automatically; if no match, set to No Mapping and the team member is kept but unlinked |
⚠️ Inactive mappings don't sync responses. Matching responses are dropped, not held. We email the Account Owner and Admins the first time this happens and send a daily summary if it continues, so resolve them promptly.
Fixing inactive mappings
Create the missing object, field or picklist value in Production (or install the package), return to Integrations → Salesforce, and click Re-validate. The mapping becomes editable and you can remap and save. Fields showing No Mapping work the same way.
📌 Your Sandbox test data. Responses collected during Sandbox testing stay in your Inbox and reports, but their links to Sandbox Salesforce records are cleared, since those record IDs don't exist in Production. Responses received after the switch sync as normal.
Part 2 — Custom Mapping
Custom Mapping lets you manually connect any Zonka Feedback survey field to any field on any Salesforce object. When a response comes in, Zonka Feedback will create or update the mapped record in real time.
What is Custom Mapping?
Custom Mapping is the most flexible option. Use it when you want to:
Push survey responses to Leads, Contacts, Accounts, Opportunities, Cases, or any custom Salesforce object
Create new Salesforce records from survey data
Update existing records conditionally (e.g., only when a score is below a threshold)
Create Activity records on an existing Salesforce object
How to Add a Custom Mapping
After connecting your Salesforce account (see Part 1), follow these steps:
On the Salesforce Integration Detail Page, ensure Custom Mapping is selected.
Click the Add Mapping button. A slide-in form will appear.
Fill in the mapping form using the fields described in the table below.
Map your Zonka Feedback survey fields to the corresponding Salesforce object fields in the 'What do you want to Map' section.
Click Save. Your mapping is now active.
Custom Mapping Form Fields
Field | Description |
Mapping Name | A label to identify this mapping (e.g., 'New Contact from NPS Survey'). Use a descriptive name if you have multiple mappings. |
Salesforce Object Type | The Salesforce object you want to write data to. Dropdown lists all standard and custom objects in your org (Contact, Lead, Opportunity, Case, Account, etc.). |
Select an Action | The action to perform on the chosen object: Create a new record, Update an existing record, or Create an Activity on an existing record. |
Select a Mapping Condition | Controls when this mapping fires. Choose 'Every Time' to trigger on all responses, or 'Only When' to add one or more conditions (e.g., NPS score < 7, specific answer selected). |
What do you want to Map | Field-by-field mapping between Zonka Feedback survey fields/response attributes and Salesforce object fields. Select 'No Mapping' to skip any field. |
Mapping Conditions in Detail
Every Time: The mapping fires for every survey response received, with no filtering.
Only When: The mapping fires only when the specified conditions are met. You can set conditions based on:
A specific survey question's answer (e.g., NPS score equals 9 or 10)
Response metadata (e.g., location, survey channel)
Logical operators: Match ALL conditions or match ANY condition
📌 Required Fields Note
Certain Salesforce objects require mandatory fields to create a new record (e.g., Last Name for a Contact, Company for a Lead). Zonka Feedback will display a note listing these required fields when you select an object type. You must map all required fields before the Save option becomes available.
Part 3 — Managed Mapping
Managed Mapping uses the Zonka Feedback Salesforce Package (available on the Salesforce AppExchange) to automatically map survey and response fields for the Salesforce Contact object. It is purpose-built for syncing CX Metrics (NPS, CSAT, CES) and AI sentiment analysis values directly to your Contacts.
Managed Mapping Requirements
|
Step 1 — Install the Zonka Feedback Salesforce Package
In Zonka Feedback, select your survey and go to Integrations > Salesforce > Connect.
On the Salesforce Integration Detail Page, select Managed Mapping.
Authenticate with Salesforce using your credentials (OTP may be required for first-time login).
You will be redirected to the Salesforce Package Installation page.
Select the type of user access for the package (Install for Admins Only, Install for All Users, or Install for Specific Profiles).
Click Install Package. Installation may take a few minutes.
Once complete, a success screen confirms the installation. Click Proceed to return to Zonka Feedback.
Step 2 — Configure the Salesforce Contact Page Layout
After installing the package, you need to add the Zonka Feedback Responses related list to the Salesforce Contact object layout so you can view survey responses directly inside a Contact record.
In Salesforce, click the Settings gear icon (top right) and select Setup.
In the Setup navigation, click Object Manager.
From the list of objects, select Contact.
In the left panel of the Contact Object Manager, click Page Layouts.
Select Contact Layout (or the layout assigned to your users).
In the page layout editor's left panel, click Related Lists.
Drag and drop the Responses related list into the layout's Related Lists section.
Click Save on the page layout.
Salesforce Contact records will now show a Responses related list where all Zonka Feedback survey responses for that contact are displayed.
Step 3 — Configure Auto-Sync Settings
In Zonka Feedback, you can control how responses are matched and synced to Salesforce Contacts. Choose the sync method that best fits your data setup:
Sync Method | How it Works |
Sync by Salesforce Contact ID | Zonka Feedback matches the Contact ID passed in the survey link parameters against your connected Salesforce org and syncs the response to the matching Contact. |
Sync by Contact Email Address | Zonka Feedback looks up the respondent's email address in Salesforce and syncs the response to the matching Contact record. |
Create New Contact if Email Not Found | If no matching email address exists in Salesforce, Zonka Feedback automatically creates a new Contact record and syncs the response to it. |
Part 4 — Triggering Surveys via Salesforce Outbound Messages
This is the most powerful part of the Salesforce integration. Rather than manually sending surveys, you can configure Salesforce to fire an outbound message when a specific event occurs — and Zonka Feedback will automatically send an Email or SMS survey to the relevant contact.
Common trigger scenarios include:
A support case is closed → Send a CSAT survey
An opportunity is marked as Won → Send an NPS survey
A new Contact is created → Send an onboarding feedback survey
A Contact's Status field changes → Send a targeted survey
A custom field is updated → Fire any survey you choose
How Outbound Message Triggering Works
The flow is:
Salesforce Event (e.g., Case Closed) → Salesforce Flow or Workflow Rule fires → Outbound Message sent to Zonka Feedback Webhook URL → Zonka Feedback sends Email/SMS Survey to the Contact |
Step-by-Step: Set Up an Outbound Message Trigger
Step 1 | Generate the Webhook URL in Zonka Feedback In Zonka Feedback, go to the survey you want to trigger. Open the Integrations tab and go to the Salesforce section. Look for the Outbound Message / Webhook URL option. Copy the unique Endpoint URL generated for this survey. You will paste this into Salesforce in Step 3. |
Step 2 | Create an Outbound Message in Salesforce In Salesforce Setup, search for 'Outbound Messages' in the Quick Find box and open it. Click New Outbound Message. Name: Give the message a descriptive name (e.g., 'Case Closed — CSAT Survey'). Object: Select the Salesforce object that will trigger this message (e.g., Case). Endpoint URL: Paste the Zonka Feedback Webhook URL you copied in Step 1. User to Send As: Select a Salesforce user with sufficient API access. Fields to Send: Select all Contact/Lead fields you want to pass to Zonka Feedback (at minimum, include Email, First Name, Last Name, and any merge fields you want to personalize the survey with). Click Save. |
Step 3 | Create a Flow (or Workflow Rule) in Salesforce to Fire the Outbound Message Option A — Using Flow Builder (Recommended for modern Salesforce orgs): • In Salesforce Setup, search for Flows and click New Flow. • Select Record-Triggered Flow. • Configure the Object and Trigger: choose the object (e.g., Case) and the trigger condition (e.g., Record is Updated, Status = Closed). • Add an Action step: search for and select Outbound Message. • Choose the Outbound Message you created in Step 2. • Save and Activate the Flow. (Important: the Flow must be activated for the trigger to fire.)
Option B — Using Workflow Rules (Legacy; check Salesforce deprecation status for your org): • In Salesforce Setup, navigate to Process Automation > Workflow Rules. • Click New Rule and select your object. • Set the evaluation criteria and conditions (e.g., Status changes to Closed). • Under Workflow Actions, click Add Workflow Action > New Outbound Message. • Configure the Outbound Message to use the Zonka Feedback Endpoint URL. • Save and Activate the Workflow Rule. |
Step 4 | Test the Outbound Message Trigger In Salesforce, manually trigger the event (e.g., close a test Case record). Check Salesforce Setup > Outbound Message Monitor to confirm the message was sent. In Zonka Feedback, check Response Inbox to verify the survey was sent to the contact. Confirm the contact receives the survey email or SMS. |
Step 5 | Activate and Monitor Once testing is confirmed, ensure your Flow or Workflow Rule is Activated. Monitor outbound message delivery from Salesforce Setup > Outbound Message Monitor. Monitor survey sends and responses from Zonka Feedback's Response Inbox and Reports. |
⚠️ Important: Flow Must Be Activated
A Salesforce Flow will NOT fire outbound messages until it is in an Activated state. After saving the Flow, always click 'Activate' from the Flow detail page. If your surveys aren't being triggered, verify this first.
Supported Salesforce Objects for Outbound Message Triggers
You can configure outbound message triggers on any Salesforce object that supports Flows or Workflow Rules. Common objects include:
Salesforce Object | Example Trigger Scenario |
Case | Case is Closed → Send CSAT survey |
Opportunity | Stage changes to Closed Won → Send NPS survey |
Contact | New Contact created → Send onboarding survey |
Lead | Lead Status changes to Qualified → Send interest survey |
Account | Account renewal date approaches → Send relationship survey |
Custom Object | Any custom record event → Send contextual survey |
Part 5 — Filtering Responses by Salesforce Merge Fields
Once your surveys are triggered from Salesforce, every response carries the Salesforce data that came with it. You can now filter your responses by that data — directly in the Response Inbox and in your survey reports — without exporting anything.
This lets you answer questions like:
Which detractors belong to a specific account owner?
What did contacts created in the last quarter say about us?
How does CSAT compare across the values of a Salesforce picklist field, such as Region or Plan Type?
How Merge Field Filters Work
The filters come from the Salesforce Merge fields you already selected when configuring your automated email trigger (Configure Email → Salesforce Data → Salesforce Merge fields). There is no separate setup step — if a field is selected on the trigger, it is available as a filter.
The flow is:
Merge field selected on the email trigger → Value travels with the Outbound Message → Value stored on the response → Field appears under + Add Filter in Inbox and Reports |
Filters are specific to each survey. A survey's Inbox and reports show only the merge fields configured on that survey's own trigger.
Step-by-Step: Filter Responses by a Merge Field
Go to Response Inbox from the left sidebar, or open any survey report.
Select the survey whose Salesforce trigger is configured. (Merge field filters are not available in the all-surveys view.)
Click + Add Filter in the filter bar.
Scroll to the Salesforce Merge Fields section of the dropdown. Your configured merge fields are listed here by their Salesforce field label.
Select the field you want to filter by.
Choose a condition and enter a value. The available conditions depend on the field's Salesforce data type — see the table below.
Click Done. The filter is applied immediately and appears as a chip in the filter bar.
To edit a filter, click its chip in the filter bar. To remove it, click the X on the chip.
💡 Tip: Combine filters
Salesforce merge field filters work alongside every other filter in the Inbox. Combine Owner ID contains [ID] with NPS: Detractors and a date range to narrow down to exactly the responses you need in a few clicks.
Available Filter Conditions by Field Type
Salesforce Field Type | Available Conditions |
Text, Text Area, Email, Phone, URL, ID, Lookup / Reference | Filled, Not Filled, Contains, Does Not Contain, Starts With, Ends With |
Date and Date/Time | Before, After, On, Next X Days, Between |
Number, Currency, Percent | Equal to, Less than, More than, Between |
Picklist and Multi-Select Picklist | Choose from the values held in Salesforce for that field, plus Filled and Not Filled |
Checkbox | Is True, Is False, Not Filled |
Notes on conditions
Contains, Starts With and Ends With are not case-sensitive.
Between includes both the values you enter. A date range of 1 June to 30 June includes responses on both of those days.
Filled returns responses that have a value for the field. Not Filled returns responses where the field is empty or was never received.
Picklist values are pulled from Salesforce, so you select from a list rather than typing. If a value is later removed in Salesforce, it stays available so you can still filter your historical responses.
Saving and Sharing a Filtered View
Once you have a filter combination you use regularly, save it so you don't have to rebuild it:
Save the filter set as a view to return to it later.
Copy the page URL to share the exact filtered view with a colleague. They will see the same filters applied, provided they have access to the survey.
If a merge field is later removed from the trigger, any saved view using it will show that condition as disabled with an explanation. The rest of the view continues to work.
Things to Know
Behaviour | What it means |
Filters are per survey | Each survey shows only the merge fields configured on its own trigger. They are not available in the all-surveys Inbox view. |
Only Salesforce-triggered responses carry values | If the same survey also collects responses through a web link, email campaign, SMS or CSV import, those responses have no merge field values and will appear under Not Filled. |
Values are captured at the time of sending | The value stored on a response is the one that came from Salesforce when the survey was triggered. Changing the field in Salesforce afterwards does not change the stored value, so your historical reporting stays accurate. |
Only configured fields are filterable | Fields you have not selected in the trigger's Salesforce Merge fields list will not appear. Add the field to the trigger and it will show up in the filter list. |
Responses collected before a field was added | These have no value for that field and will appear under Not Filled. Adding a merge field does not backfill earlier responses. |
📌 Adding a new field to filter by
Open the survey's automated email trigger, go to Configure Email → Salesforce Data → Salesforce Merge fields, add the field, and save. It will appear in the filter list right away, and responses received from that point onward will carry its value.
Part 6 — Survey Send Triggers from Salesforce Events
Beyond Outbound Messages, there are several other ways Salesforce events can automatically send surveys through Zonka Feedback.
Option 1: Native Zonka Feedback — Salesforce Trigger Settings
When setting up a custom mapping, you can define Mapping Conditions that act as filters on when the mapping executes. While this primarily controls data sync, it pairs with your distribution settings to determine when surveys are sent.
Option 2: Outbound Message via Flow (Covered in Part 4)
This is the recommended method for complex event-based triggering. Use Salesforce Flow to define the exact event and pass the contact's details to Zonka Feedback via the Outbound Message Webhook.
Option 3: Zapier / Integrately (For Teams Without Salesforce Flow Access)
If your Salesforce edition doesn't support Flows or you need to connect non-standard events, you can use Zapier or Integrately to bridge Salesforce and Zonka Feedback:
Trigger: New Outbound Message in Salesforce (Zapier native trigger)
Trigger: Record Created or Updated in Salesforce (any object)
Action: Send Email Survey via Zonka Feedback
Action: Send SMS Survey via Zonka Feedback
These automations require a Zapier or Integrately account but allow finer control without Salesforce Flow setup.
Part 7 — Syncing Locations and Tags to Salesforce
Adding Location Data to Responses and Syncing to Salesforce
If your surveys are location-based (e.g., branch, store, clinic), you can attach a location to each response and have that location data sync into Salesforce automatically.
Step 1: Create a Location in Zonka Feedback
Navigate to Manage > Locations from the left sidebar.
Click Add a Location.
Fill in Location Name, External ID, and Address.
Optionally, assign Location Labels to the location for grouping.
Click Add to save the location.
Step 2: Assign the Location to Your Survey
Navigate to Manage > Surveys.
Select the survey you want to assign a location to.
Click the location dropdown (visible at the top of the survey settings) and select Assign Locations.
In the location popup, choose the locations you want to assign.
Click Apply and save.
When a respondent opens the survey, they will be presented with a location selection popup before starting. The selected location is saved with the response and automatically synced to Salesforce.
Step 3: View Location Data in Salesforce
In Salesforce, open the Response Detail Page for any synced response. You will see two location fields: Location ID and Location Name, both populated from the respondent's selection
Adding and Removing Tags and Syncing to Salesforce
Response Tags allow you to categorize and label individual survey responses. Tags are automatically synced to Salesforce and visible on the Response Detail Page.
Adding a Tag to a Response
Go to Response Inbox from the left sidebar.
Click Assign Tags on the response you want to tag.
Search existing tags or type to create a new tag. Click Apply.
The tag is added immediately and synced to Salesforce under the 'Tags' field on the Response Detail Page.
Removing a Tag from a Response
In Response Inbox, hover over the response.
Hover over the tag you want to remove and click the X next to it.
The tag is removed instantly and the change is reflected in Salesforce.
Part 8 — CX Metrics and AI Sentiment Sync
With Managed Mapping (Growth plan required), Zonka Feedback automatically captures and syncs CX Metrics and AI-generated sentiment scores to the Salesforce Contact object. This gives your sales and service teams live customer health data directly in the CRM.
Data Field | Description |
NPS Score | Net Promoter Score from the most recent NPS survey response |
CSAT Score | Customer Satisfaction Score from the most recent CSAT response |
CES Score | Customer Effort Score from the most recent CES response |
Sentiment Value | AI-generated sentiment (Positive, Neutral, Negative) derived from open-text responses |
Last Response Date | Timestamp of the most recent survey response |
Response Count | Total number of survey responses from this contact |
These fields appear on the Salesforce Contact record (visible via the Managed Package) and in the Responses related list added during the Managed Mapping setup.
Part 9 — Troubleshooting & FAQs
Issue | Resolution |
Authentication fails or OTP not received | Ensure you are using the Salesforce account owner's email. Check spam/junk folders. Contact Salesforce support if OTP is not being delivered. |
Surveys not being triggered from Salesforce | Verify that the Flow or Workflow Rule is Activated. Check Salesforce Outbound Message Monitor for delivery failures. Confirm the Endpoint URL in the Outbound Message matches the Zonka Feedback Webhook URL exactly. |
Responses not syncing to Salesforce Contact (Managed Mapping) | Confirm that the Zonka Feedback Salesforce Package is installed in the correct org (Production vs. Sandbox). Verify the Responses related list was added to the Contact Layout. |
Required fields error when creating a Salesforce record | Check the mandatory fields note displayed in the Custom Mapping form when you select an object type. All required fields must be mapped before saving. |
Salesforce records being created but not updated | Review your Mapping Condition. For update actions, the selected action must be 'Update' (not 'Create'). Ensure a matching field (e.g., email or Contact ID) is included in the mapping for record lookup. |
Tags not appearing in Salesforce | Tags sync to the 'Tags' field on the Salesforce Response Detail Page (not the Contact). Ensure you are checking the Zonka Feedback Response Detail Page in Salesforce, not the Contact record directly. |
Outbound Message firing but survey not sent | Check that the contact's email address is included in the fields sent by the Outbound Message. Verify the Zonka Feedback Webhook URL is correctly pasted (no extra spaces or characters). |
Sandbox integration not working like Production | Sandbox and Production are separate Salesforce orgs. You must install the Zonka Feedback package separately in Sandbox and re-authenticate. All mappings configured in Sandbox are independent of Production. |
Salesforce Merge Fields section is missing from + Add Filter | This section only appears on surveys with a connected Salesforce email trigger that has at least one merge field selected. It is also not available in the all-surveys Inbox view — select a specific survey first. |
A Salesforce field I need isn't in the filter list | Only fields selected in the trigger's Salesforce Merge fields list are filterable. Open the survey's email trigger, go to Configure Email → Salesforce Data → Salesforce Merge fields, add the field and save. |
A merge field filter returns fewer responses than expected | Merge field values only exist on responses triggered from Salesforce. Responses collected on the same survey through a web link, email campaign, SMS or CSV import will appear under Not Filled. Responses received before the field was added to the trigger also have no value. |
Switch to Production button isn't visible | It shows only on Sandbox-connected surveys, and only to Account Owners and Admins. |
Mapping shows as Inactive after switching | The target object doesn't exist in Production, or the package isn't installed for Managed Mapping. Fix in Salesforce, then click Re-validate. |
Fields show No Mapping after switching | The field is missing in Production, has a different type, or your authorising user can't access it. Correct it in Salesforce, click Re-validate, then remap. |
Responses stopped syncing after switching | Check for Inactive mappings — they drop responses rather than queueing them. |
Quick Reference: Integration Types at a Glance
Integration Type | Best For |
Custom Mapping | Syncing survey responses to any Salesforce object with full field-level control |
Managed Mapping | Auto-syncing NPS/CSAT/CES scores and sentiment to the Salesforce Contact object |
Outbound Message (Flow) | Triggering surveys automatically from Salesforce events like case close or deal won |
Sandbox Testing | Validating the integration end-to-end before going live in Production |
Merge Field Filters | Filtering and reporting on your feedback using Salesforce data such as record owner, created date or picklist values |
Location Sync | Tagging responses with physical locations and surfacing them in Salesforce |
Tag Sync | Categorizing responses in Zonka Feedback and mirroring categories in Salesforce |
Zapier / Integrately | Connecting Salesforce events to Zonka Feedback surveys without Flow or code |