![](\"https://img.announcekit.app/c79bbb6a22e94b2bb280fa558a1d27d5?s=828b49ea8326113abbb2f87bea3c295f\")
You can now filter responses by hidden variables and contact attributes using the Responses API. This lets you fetch only the feedback you need, such as responses from a specific store, channel or customer segment, without pulling everything and filtering it yourself.
How it works
store_location=Downtown,Airportcontact_ to the attribute name.contact_plan=Pro,EnterpriseYou can combine these with existing filters like surveyId, startDate and limit.
Example
GET /responses?store_location=Downtown,Airport&contact_plan=Pro,EnterpriseThis returns responses from the Downtown or Airport stores, submitted by contacts on the Pro or Enterprise plan.
Use cases
View the Responses API documentation βΒ
", "url": "https://announcekit.app/zonka-feedback/product-updates/filter-api-responses-by-hidden-variables-and-contact-attributes-j8hnW", "title": "Filter API Responses by Hidden Variables and Contact Attributes", "summary": "You can now filter responses by hidden variables and contact attributes using the Responses API. This lets you fetch only the feedback you n...", "date_modified": "2026-10-01T06:48:10.000Z", "tags": [ "announcement", "improvement", "new" ] }, { "id": "448421", "content_html": "We're excited to roll out the Zonka Feedback MCP Server β a new way to work with your customer feedback right inside the AI tools your team already uses, like Claude and ChatGPT.
Until now, getting answers from your feedback meant opening dashboards, building reports, or exporting data. With the MCP server, you just ask β in plain language, from your AI assistant, using your live Zonka Feedback data.
Link Claude, ChatGPT, or any MCP-compatible tool to your account in a couple of clicks. Zonka Feedback is listed in the Claude connector directory, so there's nothing to wire up by hand.
Query your survey responses, NPS, CES, CSAT, and sentiment, online reviews and reputation, and your AI Feedback Intelligence themes β down to the verbatim quotes behind them β just by asking. No exports, no query language.
Every connection signs in with OAuth and runs with that user's own role and access. The connector is read-only β it reads and analyzes your feedback, and never changes your account.
π Track your metrics β \"What's our NPS this quarter, and how does it compare to last?\"
π§ Find what's driving sentiment β \"Which themes are behind our negative feedback right now?\"
β Watch your reputation β \"What's our average review rating this year, and how many did we reply to?\"
Available on all plans. An account admin turns it on under Settings β AI Governance β AI Features β Agents & MCP, after which everyone on the account can connect their own AI tool.
Learn more here
", "url": "https://announcekit.app/zonka-feedback/product-updates/introducing-the-zonka-feedback-mcp-server-32inLi", "title": "Introducing the Zonka Feedback MCP Server", "summary": "We're excited to roll out the Zonka Feedback MCP Server β a new way to work with your customer feedback right inside the AI tools your team ...", "date_modified": "2026-09-25T12:00:00.724Z", "tags": [ "new", "feature" ] }, { "id": "449042", "content_html": "Your CRM and helpdesk can now show more than what customers said. They can also show how customers felt and what they need. π―
You can now map Sentiment, Emotion, Intent, and Urgency to fields in Salesforce, HubSpot, Intercom, and every other integration that supports one-to-one field mapping.
How to set it up
From then on, each new response sends its AI-detected signals to the fields you mapped.
What your teams can do with it
Your teams can act on feedback signals in the tools they already use, without logging into Zonka Feedback.
", "url": "https://announcekit.app/zonka-feedback/product-updates/sync-ai-feedback-signals-to-salesforce-hubspot-intercom-more-lp4qs", "title": "Sync AI Feedback Signals to Salesforce, HubSpot, Intercom & More", "summary": "Your CRM and helpdesk can now show more than what customers said. They can also show how customers felt and what they need. π― You can now m...", "date_modified": "2026-09-24T06:59:34.000Z", "tags": [ "improvement" ] }, { "id": "449039", "content_html": "When Zonka sends a response to a connected tool β creating a ticket, posting a notification, or syncing the full response β it now carries every attribute on that response, not just the survey answers and a fixed set of contact fields.
Now included:
Attributes also travel across integrations, not just back where they came from. A Shopify post-purchase survey response now carries its order ID, order total, line items and shipping type into the Zendesk ticket it creates β so your team sees the order behind the feedback without leaving the helpdesk.
This works across ticket creation, notifications and full response sync, in every integration you've connected.
", "url": "https://announcekit.app/zonka-feedback/product-updates/all-response-attributes-now-sync-to-your-integrations-hZSRG", "title": "All response attributes now sync to your integrations", "summary": "When Zonka sends a response to a connected tool β creating a ticket, posting a notification, or syncing the full response β it now carries e...", "date_modified": "2026-09-22T06:46:14.000Z", "tags": [ "announcement", "improvement" ] }, { "id": "449041", "content_html": "Salesforce mappings used to force a choice up front: create a new record, or update an existing one. Pick wrong and you got duplicate Contacts, or updates that went nowhere.
Custom Mapping now has a fourth action: Create or update a record using an External ID.
Choose a Salesforce field you already use to identify customers β account number, CRM ID, subscription reference β and every response is checked against it. Match updates the record. No match creates one.
Get the identifier onto a response three ways:
?sf_External_Field_1__c=Get%20Started (sf_ prefix + the Salesforce API name)Set it up under Integrations β Salesforce β Add Mapping. Only fields marked as External ID in Salesforce appear β mark yours Unique too, or a value matching multiple records won't sync. Matching is exact, case and spacing included.
", "url": "https://announcekit.app/zonka-feedback/product-updates/create-or-update-salesforce-records-using-an-external-id-kgFUc", "title": "Create or update Salesforce records using an External ID", "summary": "Salesforce mappings used to force a choice up front: create a new record, or update an existing one. Pick wrong and you got duplicate Contac...", "date_modified": "2026-09-15T06:51:53.000Z", "tags": [ "announcement", "improvement", "new" ] }, { "id": "447261", "content_html": "Tested your Salesforce integration in a sandbox? Take it live without rebuilding anything from scratch.
What is Sandbox to Production migration?
From your survey's Integrations β Salesforce screen, select Switch to Production and authorise your production org. Your mappings, filters, email trigger configuration, and synced users all carry over as they were. Zonka then validates the configuration against your production org and shows you a summary of what transferred β and flags anything that needs attention.
Whether you're:
π‘ Key Use Cases
Zero-rebuild go-live Switch orgs with one authorisation step and keep everything intact. Example: A RevOps team spent two weeks mapping custom fields and configuring triggers in sandbox β they switch to production in minutes, nothing lost.
Automatic field validation Zonka checks every mapped field against your production org and surfaces mismatches immediately. Example: A field that existed in sandbox but wasn't deployed to production gets cleared automatically β the rest of the mapping keeps working without interruption.
Pause and recover missing objects If an entire object is missing in production, that mapping is paused rather than deleted. Example: A custom object wasn't deployed yet β once it's created in production, use Re-validate to bring the mapping back without reconfiguring it.
Available on all Salesforce Plans
", "url": "https://announcekit.app/zonka-feedback/product-updates/move-your-salesforce-integration-from-sandbox-to-production-xRuO4", "title": "Move your Salesforce integration from Sandbox to Production", "summary": "Tested your Salesforce integration in a sandbox? Take it live without rebuilding anything from scratch. What is Sandbox to Production migrat...", "date_modified": "2026-09-01T07:28:06.000Z", "tags": [] }, { "id": "447260", "content_html": "Slice your Response Inbox and survey reports using the Salesforce data already attached to your responses β no extra configuration needed.
What is Salesforce response filtering?
Any Salesforce merge field you've selected on a survey's automated email trigger is automatically available as a filter under + Add Filter β Salesforce Merge Fields. Conditions adapt to the field type, so you get the right operators for text, dates, numbers, and picklists β including the actual values held in Salesforce.
Whether you're:
π‘ Key Use Cases
Segment by account or ownership Filter responses to a specific account owner or team directly from your report. Example: A CX lead wants to see all detractor responses from accounts owned by the enterprise sales team β done in two clicks.
Track campaign or lifecycle cohorts Use date or ID fields from Salesforce to isolate responses tied to a specific onboarding batch or renewal cycle. Example: Filter by Onboarding Start Date to see feedback from customers in their first 30 days.
Build and share focused views Combine Salesforce filters with existing ones, save the result as a view, or share it via URL with your team. Example: An ops manager shares a pre-filtered report with the customer success team every Monday β no manual exports.
Worth knowing: filters are survey-specific and only show merge fields on that survey's own trigger. Responses collected outside Salesforce β via web link or SMS β will appear as Not Filled.
Available on all Salesforce Plans
", "url": "https://announcekit.app/zonka-feedback/product-updates/filter-your-responses-by-salesforce-data-wJ6hO", "title": "Filter your responses by Salesforce data", "summary": "Slice your Response Inbox and survey reports using the Salesforce data already attached to your responses β no extra configuration needed. W...", "date_modified": "2026-09-01T07:24:58.000Z", "tags": [] }, { "id": "447267", "content_html": "What does the Klaviyo integration do?
Every survey response can now automatically update a Klaviyo profile, add a respondent to a list, or trigger a flow β with no manual exports or data wrangling. The integration works both ways: pull Klaviyo contacts into Zonka to survey them, or push feedback back into Klaviyo to personalize your campaigns.
Whether you're:
π‘ Key Use Cases
Segment by feedback, not just behaviour Map survey scores to Klaviyo profile properties and build segments the instant feedback lands. Example: Detractors from your post-purchase NPS flow automatically enter a win-back sequence β no manual tagging needed.
Embed surveys inside Klaviyo emails Drop a question, button, or hyperlink into any campaign using ready-made HTML. Responses tie back to the Klaviyo profile, so you can act on them without switching tools. Example: A one-click CES question inside your onboarding email, with scores synced to the contact's profile.
Keep both platforms in sync Two-way sync pulls Klaviyo profiles into Zonka as contacts and keeps them current β automatically or on demand. Example: A new list segment in Klaviyo is available in Zonka for survey targeting within minutes, with no CSV in sight.
π View Integration Guide β
πΒ Find us on the Klaviyo Marketplace β
Available on Growth plan and above.
Export the responses behind any theme or sub-theme as a CSV β filtered, column-picked, and delivered to your inbox.
Click the export icon on the filter bar, next to a theme title, or on any sub-theme card. Select a date range, choose your columns, and you're done. Each row is one response Γ one sub-theme, so sentiment stays accurate even when a response is tagged under multiple sub-themes.
π‘ Key Use Cases
Theme-level exports for focused analysis Export exactly the responses tagged to a theme or sub-theme β nothing else. Example: A CX manager spots a spike in \"Billing Confusion\" and exports just those responses to share with the Finance team.
Accurate sentiment per tag Because each row is one response Γ one sub-theme, a response tagged under three sub-themes appears three times β each with its own sentiment intact. Example: A response mentioning both \"Onboarding\" and \"Support Speed\" shows up under each, so neither theme's sentiment gets diluted.
Flexible column selection Choose only the columns relevant to your audience before exporting. Example: A quarterly review export includes response text, NPS score, and account name β nothing else cluttering the sheet.
Worth knowing: the CSV is delivered by email and the download link is valid for 5 days.
Available on Growth and Enterprise plans with Intelligence Hub addon.
", "url": "https://announcekit.app/zonka-feedback/product-updates/intelligence-hub-export-responses-and-theme-data-directly-from-deep-dive-report-Cp4T6", "title": "Intelligence Hub : Export responses and theme data directly from Deep Dive Report", "summary": "Export the responses behind any theme or sub-theme as a CSV β filtered, column-picked, and delivered to your inbox. Click the export icon on...", "date_modified": "2026-08-31T07:31:42.000Z", "tags": [] }, { "id": "447269", "content_html": "You can now see exactly what your integrations are doing β every event, every status, in one place with Integration Logs. They are useful in the following ways.
π‘ Key Use Cases
Know when something goes wrong β before it becomes a problem Failed events surface immediately with enough context to act. Example: Three responses didn't sync to your CRM β the log shows exactly which ones, so you can follow up without waiting on support.
Confirm your setup is working After configuring a new integration, verify it's firing correctly without guessing. Example: A new Klaviyo integration was set up yesterday β the log confirms responses are syncing to the right profiles.
Answer audit questions yourself 30 days of history means you don't need to raise a ticket every time someone asks \"did this run?\". Example: Confirming whether a webhook fired for a specific account before a customer call.
Available on all plans
", "url": "https://announcekit.app/zonka-feedback/product-updates/no-more-guessing----see-exactly-what-your-integrations-are-doing-GWEY8", "title": "No more guessing β see exactly what your integrations are doing", "summary": "You can now see exactly what your integrations are doing β every event, every status, in one place with Integration Logs. They are useful in...", "date_modified": "2026-08-27T08:01:35.000Z", "tags": [] }, { "id": "445833", "content_html": "Great news β Zonka Feedback now supports Gupshup as a WhatsApp messaging provider, alongside Infobip!
Why this matters
If your team already uses Gupshup for WhatsApp Business messaging, you can now connect it directly to Zonka Feedback and start sending survey invites, feedback requests, and follow-ups β no extra tools needed.
What's new
How to get started
Don't have a Gupshup account yet, or want help connecting a different sender? Reach out to us at hello@zonkafeedback.com β we're happy to help.
", "url": "https://announcekit.app/zonka-feedback/product-updates/new-send-whatsapp-surveys-via-gupshup-2wsyHK", "title": "π£ New: Send WhatsApp Surveys via Gupshup", "summary": "Great news β Zonka Feedback now supports Gupshup as a WhatsApp messaging provider, alongside Infobip! Why this matters If your team already ...", "date_modified": "2026-08-12T06:14:33.017Z", "tags": [ "announcement" ] }, { "id": "445730", "content_html": "We're excited to roll out account-wide AI Governance β one place for admins to control every Zonka Feedback AI capability across your account.
Until now, AI features ran by default with no central switch. With this update, account owners decide which AI is available, to whom, and where β so your team only works with the capabilities you've approved.
What's New?
π‘οΈ Account-wide on/off control β Enable or disable AI per hub (Survey Hub, Reputation Hub, Intelligence Hub) for every user at once.
π§ Granular signal control β Choose exactly what AI extracts from each survey response and review: Sentiment, Intent, Emotion, and Urgency. Turn off what you don't want your team acting on.
π AI survey creation & translation toggles β Keep or remove AI-assisted survey building and AI translation independently of the rest.
Why It Matters
Use Cases
π’ Approval-gated rollout β A security-conscious team keeps specific extractions off until internal sign-off, then flips them on account-wide.
ποΈ Standardized access β An admin sets one consistent AI posture so every user across teams sees the same capabilities.
Who Is It For?
Timing matters as much as targeting. A survey that lands at 3 AM in a recipient's timezone is far less likely to get a response than one that lands during their morning coffee. With Smart Send, Zonka Feedback now delivers your surveys within a preferred time window based on each recipient's local timezone β automatically.
π Timezone-Aware Delivery Smart Send detects each recipient's local timezone and holds delivery until it falls within your chosen sending window β instead of firing every survey the moment a trigger or schedule kicks off.
π Three Delivery Windows to Choose From Pick the window that fits your audience:
All windows run Monday to Friday, so surveys never land on a recipient's weekend.
π Works Across Every ChannelΒ Smart Send applies uniformly across Email, SMS, WhatsApp, scheduled campaigns, and workflow-triggered sends β one setting, consistent behavior everywhere.
Sending at the wrong hour is one of the quietest reasons response rates underperform β recipients simply aren't in a position to engage. With Smart Send, you can:
Smart Send controlsΒ when within the dayΒ a survey is delivered based on recipient timezone. It does not change how Auto Pilot schedulesΒ recurringΒ cycles (every 3, 6, 12 months, etc.) or its Smart Distribution logic across a cycle β those continue to work exactly as before. The two features operate independently and can be used together.
Go to Settings β Survey Hub β Throttling & Smart Send and toggle on Smart Send, then choose your delivery window.
π Learn more about Smart Sending β Help Center
Plan Availability: Available on Growth, and Enterprise plans.
", "url": "https://announcekit.app/zonka-feedback/product-updates/introducing-smart-send----deliver-surveys-at-the-right-local-time-every-time-4sNnEY", "title": "Introducing Smart Send β Deliver Surveys at the Right Local Time, Every Time", "summary": "Timing matters as much as targeting. A survey that lands at 3 AM in a recipient's timezone is far less likely to get a response than one tha...", "date_modified": "2026-07-31T12:24:42.010Z", "tags": [ "announcement", "feature" ] }, { "id": "445733", "content_html": "We're excited to roll out Signals in the Intelligence Hub β a prioritized list of what's changing, who's at risk, and what's worth acting on right now.
Until now, Snapshot told you your scores, and Deep Dive let you explore themes β but you still had to work out what mattered most. Signals does that read for you: it turns your analyzed feedback into a ranked set of things to act on, each tied to real customer quotes.
What's New?
π Key Drivers β The sub-themes moving your experience most: what's trending, newly appearing, emerging fastest, and your strongest positives and negatives.
π¬ Feedback Queries β What customers are asking for and asking about. A spike in questions usually points to an onboarding or documentation gap.
β οΈ Churn Signals β Relationships at risk, complaints, and time-bound Recovery Opportunities β recent high-urgency negatives where the customer still looks winnable.
π Praises & Recommendations β What's working and worth protecting, ready for advocacy and testimonials.
How It Works
Every row is one sub-theme carrying that signal, with its volume, change against the previous equal period, and a sentiment bar. Expand any row to read the customer quotes behind it β for intent signals, you see the exact sentence, not the whole response. Colour follows sentiment, and for churn, complaints, and negative drivers, a rise shows red, so the things getting worse stand out immediately.
Act Without Leaving the Page
Every row has an action bar: create a ticket, post to Slack or Microsoft Teams, or send an email β each pre-filled with the sub-theme, sentiment, volume, change, and quote. Filters are global and carry over from Snapshot and Deep Dive, and CSV export respects your active filters and sort.
Why It Matters
Who Is It For?
Getting Started
Signals lives under Intelligence Hub β your project β Signals tab. It needs Intelligence Hub enabled and a completed analysis run for a project
Available on all Enterprise Plans with Intelligence enabled
", "url": "https://announcekit.app/zonka-feedback/product-updates/introducing-signals-turn-analyzed-feedback-into-what-to-act-on-today-GV0FW", "title": "Introducing Signals: Turn Analyzed Feedback Into What to Act On Today", "summary": "We're excited to roll out Signals in the Intelligence Hub β a prioritized list of what's changing, who's at risk, and what's worth acting on...", "date_modified": "2026-07-31T10:24:34.000Z", "tags": [ "new", "feature" ] }, { "id": "444777", "content_html": "We're excited to introduce the Survey Links API β generate unique, tracked survey links programmatically and send them through whatever channel you already use.
Until now, sending a tracked survey meant sending it from Zonka. If you wanted to trigger a survey from your own app, your own CRM sequence, or a push notification, you gave up the attribution that makes the response useful. With this update, your system creates the link and keeps every bit of context attached to it.
Call the API with a survey and a contact, and you get back a unique URL to distribute however you like β email, SMS, WhatsApp, push, in-app, or anywhere else. The link resolves against your survey's default URL, using your white-label survey domain when you have one configured.
Pass contact details, contact attributes, hidden and survey variables, and CRM variables when you create the link. When the respondent submits, all of it binds to the response automatically β no prefill parameters to construct, no follow-up call to enrich. You can attribute the response to a specific location and agent at the same time.
Each link is consumed on the first submitted response, so one link means one respondent. You can set your own expiry per link as well.
Five endpoints, under Settings β Developers β API for your auth token:
POST /survey-links β create a tracked linkGET /survey-links β list your active linksGET /survey-links/{linkId} β fetch one linkPATCH /survey-links/{linkId} β update an unused linkDELETE /survey-links/{linkId} β remove a linkA response submitted through an API-generated link is recorded with the channel External β visible in your Response Inbox filters, reports, exports, and webhook payloads, with the same attribution you'd get from a Zonka-sent Email or SMS link. Nothing about your existing reporting changes.
Generate your auth token under Settings β Developers β API, then explore the endpoints in our Postman collection.
Building an integration? Write to us at hello@zonkafeedback.com and we'll walk through it with you.
π Survey Links API β Documentation
Available on Growth and Enterprise plans.
Slack Digest Reports now let you choose the data window each digest covers. Pick a fixed calendar period when the digest feeds a reporting cycle, or a rolling window when you're watching a trend.
Rolling periods refresh with every delivery. Calendar periods always cover the last complete cycle.
Go to Surveys β Integrations β Slack β Settings, turn on Send recurring Digest Reports to Slack, choose your Frequency, then select a Reporting period. Save.
Available on all Growth and Enterprise Plans
", "url": "https://announcekit.app/zonka-feedback/product-updates/set-the-reporting-period-for-your-slack-digest-reports-PYNAQ", "title": "Set the Reporting Period for Your Slack Digest Reports", "summary": "Slack Digest Reports now let you choose the data window each digest covers. Pick a fixed calendar period when the digest feeds a reporting c...", "date_modified": "2026-07-22T11:36:32.000Z", "tags": [ "new" ] }, { "id": "444460", "content_html": "Webhooks in Zonka Feedback have been rebuilt with a new payload, and AI insights delivered inline. Your systems can now act on feedback the moment it arrives β without a follow-up API call to enrich it.
Sentiment, urgency, intent, and emotion now ship with every response delivery. Route an angry, high-urgency response straight to a senior agent in your helpdesk, or open a Salesforce case only when intent signals churn risk β all from the webhook body, no enrichment step required.
eventType and eventId, so you can identify the trigger and de-duplicate on your end.contactAttributes and responseAttributes now use a fixed variableId + value structure instead of dynamic keys β no more schema that shifts per survey.surveyResponse array.Under Settings β Developers β Webhooks, you'll now see four events:
response.added β completed response, new payloadpartial.response.added β partial response, new payloadEvery webhook created before this update keeps receiving the legacy payload exactly as before. We strongly recommend that you migrate to the new format ASAP, as the legacy formats will be deprecated in near future.
Go to Settings β Developers β Webhooks β Add Webhook and select the new response.added event.
Migrating an existing integration? Write to hello@zonkafeedback.com and we'll walk through the payload mapping with you.
π Using Webhooks β Help Center
Available on Professional, Growth and Enterprise plans.
", "url": "https://announcekit.app/zonka-feedback/product-updates/introducing-webhooks-2.0-OQp4A", "title": "Introducing Webhooks 2.0", "summary": "Webhooks in Zonka Feedback have been rebuilt with a new payload, and AI insights delivered inline. Your systems can now act on feedback the ...", "date_modified": "2026-07-22T11:23:54.000Z", "tags": [ "announcement", "new" ] }, { "id": "444457", "content_html": "Some feedback isn't for the whole workspace. Exec-level CX reports, account escalations, at-risk NPS alerts β until now, routing those to Slack meant putting them in a channel anyone could join.
With this update, you can send everything from Zonka Feedback to private Slack channels, so sensitive feedback reaches only the people who should see it.
Invite the Zonka Feedback app to your private channel β type /invite @Zonka Feedback in the channel and hit Enter. That channel then appears in your channel picker across every Slack integration setting, marked with a lock icon.
π¨ Account escalations β Route detractor responses from named enterprise accounts to a private CSM channel instead of a general alerts feed.
π Leadership digests β Send the weekly NPS and sentiment digest to a private exec channel.
π¬ Internal team reviews β Keep agent-level or store-level feedback inside the manager channel that acts on it.
Available on all plans with the Slack integration enabled.
", "url": "https://announcekit.app/zonka-feedback/product-updates/private-slack-channels-are-now-supported-for-notifications-digests-and-surveys-LrdvO", "title": "Private Slack Channels Are Now Supported for notifications, digests and surveys", "summary": "Some feedback isn't for the whole workspace. Exec-level CX reports, account escalations, at-risk NPS alerts β until now, routing those to Sl...", "date_modified": "2026-07-22T10:45:00.000Z", "tags": [] }, { "id": "444456", "content_html": "We're excited to roll out a new native action in the Zonka Feedback HubSpot integration: Send Two-Way SMS Survey From Zonka.
Add Send Two-Way SMS Survey From Zonka to any HubSpot Workflow. When the workflow fires β a ticket closes, a deal is won, onboarding wraps β the enrolled contact gets a conversational SMS survey and answers question by question in the same thread.
Use Additional Attributes (JSON) to prefill the response with the context you already hold in HubSpot: language to send in the contact's own language, locationId to attribute feedback to a specific store or branch, ratedUser to tie it to the agent who handled the ticket, plus any custom variable you track.
Responses flow into Zonka Feedback with all tracked attributes attached β so they segment, filter, and roll up into your dashboards without any manual mapping.
π Multi-location retail β Close a support ticket in HubSpot, auto-text a CSAT survey stamped with the store'slocationId, and compare branch performance without asking the customer where they shopped.
π¬ Support quality tracking β Pass ratedUser on every ticket-closed workflow to build per-agent CSAT automatically.
π Post-onboarding check-in β Fire a short two-way survey when a deal-won or onboarding-complete workflow triggers, while the experience is still fresh.
Install the Zonka Feedback app from the HubSpot Marketplace, add the Send Two-Way SMS Survey From Zonka action to your workflow, map the contact's Mobile Number, pick your survey, and turn it on.
HubSpot Workflows also support Send Email Survey, Send SMS Survey, and Send a Survey from Webhook actions.
Two-Way SMS Surveys must be enabled on your Zonka Feedback plan before this action will send. Reach out to your account manager or write to hello@zonkafeedback.com to switch it on.
Multilingual email support now extends to surveys sent through Salesforce. Until now, multilingual surveys were limited to other distribution channels. With this update, the surveys your team triggers from Salesforce workflows go out in each customer's own language.
In your Salesforce Data settings, a new Field that determines the recipient language dropdown lets you map any Salesforce language field β Preferred Language, Locale, Language β to your survey. Once mapped, each contact receives the survey in their own language automatically.
The dropdown defaults to No Mapping. Existing triggers keep running exactly as they do today until you choose a field β nothing changes underneath your live workflows.
When a contact's language field is empty or doesn't match an enabled language, the survey's default template is used, so every recipient still gets a complete send.
π¬ Global support follow-up β Fire a CSAT survey from Salesforce on case closure, localized via the mapped language field.
π Multi-region NPS β Run one NPS program across regions with each contact receiving the email in their preferred language.
Available on all Salesforce Plans