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:

• Moving a fully configured integration to production after UAT
• Preserving complex field mappings you don't want to redo manually
• Carrying over email trigger settings and synced user configurations
• Checking what transferred before anyone goes live

💡 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

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:

• Filtering by account owner to review responses by rep
• Segmenting by a date field to track a specific campaign window
• Narrowing down by picklist value like region or plan tier
• Combining a Salesforce field with an NPS segment and a date range

💡 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

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:

• Syncing NPS, CSAT, or CES scores to Klaviyo profiles for real-time segmentation
• Adding respondents to lists like NPS Promoters or detractors-to-win-back on submit
• Embedding a survey question directly into a Klaviyo email campaign
• Triggering survey sends automatically from a Klaviyo flow
• Keeping contacts in sync across both platforms without manual imports

💡 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.

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

• New provider option: Choose "Gupshup" from the Provider dropdown under Settings → Survey Hub → WhatsApp Surveys.
• Simple setup: Just add your Gupshup API Key, App Name, App ID, and WhatsApp Sender number to get connected.
• Same great workflow: Once connected, sending surveys works exactly as before — configure your WhatsApp template, map placeholders, preview the message live, add recipients (manually, via contact segments, or CSV import), and send.
• Full visibility: Track every message with WhatsApp Survey Logs, so you always know what's been sent, delivered, and responded to.

How to get started

1. Go to Settings → Survey Hub → WhatsApp Surveys → WhatsApp Setup
2. Select Gupshup from the Provider dropdown
3. Enter your API Key, App Name, App ID, and Sender number, then hit Update
4. Head to Distribute → SMS & WhatsApp to configure your template and send your first survey

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.

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

• Policy alignment: Match your AI usage to your organization's internal AI-use policy and data-handling rules.
• Consistency: Everyone in the account works from the same approved set of AI capabilities — no ad hoc variation.
• Simple control: One screen, clear toggles. No tickets, no config files, no waiting on support.

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?

• Admins / account owners: one control surface for all AI.
• Security & governance leads: a clear view of what AI is enabled.

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.

What's New?

🌍 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:

• Morning (8:00 AM – 12:00 PM) — for a focused, start-of-day nudge
• Business Hours (8:00 AM – 5:00 PM) — the standard workday window
• Extended Day (8:00 AM – 8:00 PM) — widest reach across the day

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.

Why This Matters

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:

• Improve response rates by reaching people when they're actually available
• Avoid survey fatigue from odd-hour delivery
• Maintain a consistent, professional send cadence across global audiences
• Set it once and let delivery timing take care of itself

A Note on Auto Pilot

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.

Getting Started

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.

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

• From data to decision: Stop interpreting dashboards — open Signals and see what to do today.
• Catch risk early: Churn and Recovery Opportunities surface at-risk relationships while they're still recoverable.
• Route in one click: Insights become tickets, messages, and emails without copy-paste.

Who Is It For?

• CX & operations leads: a daily prioritized worklist instead of a report to decode.
• Support & CS teams: recovery opportunities and complaints, ready to action.
• Product & marketing: feature requests and advocacy, surfaced automatically.

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

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.

What's New?

🔗 Tracked Links, Generated On Demand

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.

🎯 Full Context Travels With the Link

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.

👤 Single-Use and Time-Bound

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.

Working With Links

Five endpoints, under Settings → Developers → API for your auth token:

• POST /survey-links — create a tracked link
• GET /survey-links — list your active links
• GET /survey-links/{linkId} — fetch one link
• PATCH /survey-links/{linkId} — update an unused link
• DELETE /survey-links/{linkId} — remove a link

✅ Responses Land Exactly Where You Expect

A 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.

🚀 Getting Started

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

Plan Availability

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.

📊 Your Options by Frequency

• Daily: Yesterday, Last 7 days, or Last 30 days
• Weekly: Calendar week (Monday–Sunday, last complete week) or Last 7 days
• Monthly: Calendar month (1st to last day, last complete month) or Last 30 days

Rolling periods refresh with every delivery. Calendar periods always cover the last complete cycle.

Why It Matters

• Calendar periods match how you report: a Monday digest covering the complete prior week lines up with your weekly review, and a monthly digest with the closed calendar month matches your business reporting.
• Rolling periods show movement, not snapshots: a daily digest set to Last 30 days gives your team a fresh 30-day view of NPS, CES, CSAT, and AI sentiment signals every morning — enough of a window to see a trend, updated often enough to catch it early.

How to Set It Up

Go to Surveys → Integrations → Slack → Settings, turn on Send recurring Digest Reports to Slack, choose your Frequency, then select a Reporting period. Save.

Plan Availability

Available on all Growth and Enterprise Plans