Running a feedback program comes down to three jobs. You ask the right people the right questions. You work out what their answers are telling you. Then you make sure someone does something about it.
Since our September update, we’ve shipped changes to all three. Some save you setup time. Some put the number you already report straight onto the page. Some carry your results out of SurveyRock and into the places where your team already works.
Here’s what’s new, grouped by the job it helps with, and which plan each one needs. Everything below is live now.
Ask: start from what you already have
Turn an existing questionnaire into a survey. If your questions already sit in a Word file, a PDF or an email, you don’t have to retype them. Paste the text, or upload a .docx, .pdf or .txt file, and SurveyRock drafts a survey from those questions and answer choices for you to review and edit before you save. Drafts now come with suggested pages, required questions and help text, and that goes for surveys you describe in a prompt too. Logic, piping, quotas, scoring and images aren’t carried over, and rating questions start with default scales, so check those before you publish. Available on Solo and up, and each draft uses AI credits. How converting works
Bring your past responses with you. Moving to a new tool usually means leaving your history behind. Now you can import past responses from a CSV or Excel file into a survey you’ve built in SurveyRock: map each column to a question, preview the result, then import. For multiple choice, ranking and matrix questions, which a file often spreads across several columns (one per choice, per ranked item or per matrix row), you can map them all to the one question and SurveyRock combines them. Imported responses don’t count toward your plan’s monthly response limit. Import works on every plan, for editors and above. Import answers across several columns
Offer one survey in several languages. A survey can now carry more than one language. Translate it in the editor next to the original, in a file for your translator, or from AI drafts, which use AI credits only when someone accepts them. Respondents pick their language from a menu, and each response records the language it was answered in, so you can filter results by language. Answers to choice questions combine across languages into one report. Available on Growth and up. Offer a survey in more than one language
Send surveys under your own name. Survey links, shared reports and file uploads can now live on your own domain. You add two DNS records where you manage your domain, and SurveyRock checks them and sets up the security certificate. Invitations, reminders and thank-you emails can also go out from your own verified email domain, or through your own mail server, without our “Powered by SurveyRock” footer. Both are on Growth and up, and neither is available during a free trial. Send from your own server or domain
Build and read surveys by asking Claude. Add SurveyRock to claude.ai as a custom connector, or to Claude Code, and you can build a survey, publish it, share the link and read the results by asking in plain words. It works on every plan, including Free. Claude works only in the one workspace you pick, and it can’t delete surveys or touch billing, team members or workspace settings. Build a survey by asking Claude
Understand: read the number you report, and slice it by what you know
CSAT, CES and Top 2 box on every rating question. If you report CSAT or CES, you no longer need a spreadsheet to work it out. Each rating question now shows a percentage beside its average. A scale that ends in “Very satisfied” reports CSAT, one that ends in “Very easy” reports CES, and anything else reports Top 2 box, the share of people who picked one of the two highest points. The range it counts is printed next to the figure, and you can choose the measure yourself in the question’s Results settings, which is also how to set it for a scale labelled in a language other than English. With enough responses you also get a weekly or monthly trend. The figure and trend are on every plan; the question’s data table and CSV download, and dashboard filters, need Team. What CSAT measures
Filter and compare by what you already know about a respondent. You often know things the survey never asked: the company on someone’s contact record, or a department you passed in through the survey link. These respondent attributes now show on each respondent’s page and in CSV and Excel exports. You can filter responses by them, and use them as a row or column in a crosstab, so “how did Acme’s users answer?” doesn’t need a question of its own. Contact fields marked sensitive stay hidden from anyone who isn’t allowed to see them. Contact fields are on Solo and up, and values passed in through the survey link are on Growth and up. Filtering by them needs Team; crosstabs need Growth. Respondent attributes
Key drivers: see what to fix first. Key drivers, which we covered in September, now plots each question on two scales: how closely it moves with your score, and how well it scores itself. The questions that matter most and score lowest land in one corner, and that’s the place to start. You can filter the analysis like any other report and export it to CSV or Excel. It still shows which answers move together with your score, not what causes the score to change. Available on Growth and up; the weighted view needs Pro, where response weighting lives. Key drivers
MaxDiff: find out what matters most when everything seems to. Ask people to rate fifteen features or benefits and most of them come back “important,” which tells you little. A MaxDiff question shows a few items at a time and asks which one matters most and which least. SurveyRock turns those picks into a ranking of 6 to 30 items, showing each item’s share of the vote with a margin of error. The scores describe the group, not each person, and they appear once at least 30 people have answered. Available on Growth and up. MaxDiff questions
Act: make sure someone follows through
Give an action a target, and break it into sub-actions. When an action tracks a score, such as a rating or NPS question you picked or the result it was raised from, you can now give it a target. Once enough new responses come in, the action shows how far the score has moved toward it. Bigger pieces of work can be split into sub-actions, one level deep, each with its own due date and, on plans with more than one seat, its own owner. Both work on every plan, including Free, which allows three open actions at a time. The morning email of actions that are due now arrives at 08:00 in the owner’s own time zone, and it can be switched off in notification preferences. Actions
Actions from alerts and workflows, and a post in Slack. When the Feedback Intelligence dashboard flags an unusual jump in an open-text theme, you can raise an action straight from the alert (Growth and up). A workflow can now raise an action on its own, as one of its steps (Team and up). And managers can have every new assignment posted to a shared Slack channel, naming who now owns it. That needs Slack connected to your workspace, which comes with workflows on Team and up. What connects to SurveyRock
Freshdesk tickets from workflows and actions. If your support team works in Freshdesk, a workflow can now create or update a ticket, or add a note to one, when a response comes in, and an action can open a linked ticket in one click. Freshdesk emails the customer to say their ticket was received unless a Freshdesk admin turns that email off, so check the setting before you switch the workflow on. Available on Pro and up. Connect Freshdesk
Webhooks: tell your own systems when a survey is completed. If you run your own systems, such as a data warehouse, a CRM sync or an internal dashboard, SurveyRock can now tell them as soon as a respondent completes a survey. Add a webhook in Workspace Settings or through the API, and we send a signed request to your endpoint, retrying for nearly four days if it’s down. If your system can’t accept incoming requests, it can read the same events from an event feed instead. Each event carries IDs and the completion time, not the answers, so your system fetches the answers through the API. Available on Team and up. Webhooks and events
Workflow webhooks that keep trying. A workflow’s webhook step can now send in the background. It hands the request to the same delivery queue as webhooks and keeps retrying for nearly four days, instead of failing the step when your endpoint is down for a moment. Requests can be signed, each one carries an Idempotency-Key so your endpoint can ignore repeats, and run history shows where each delivery stands, with a Send again button. Workflows are on Team and up, and replaying a step with its original input is on Growth and up. Webhook steps in workflows
Where to go from here
If a feature above needs a plan you’re not on yet, pricing shows what each plan includes. And for the running record of what changes in SurveyRock, see our changelog.