Survey Question Response
A Survey Question Response in Salesforce, called SurveyQuestionResponse in the API, is a standard object that records one respondent's answer to one question on a survey.
Definition
A Survey Question Response in Salesforce, called SurveyQuestionResponse in the API, is a standard object that records one respondent's answer to one question on a survey. It is the row-level fact behind every Salesforce Surveys analysis. When a person finishes a five-question survey, the platform writes one SurveyResponse record (the whole submission) and five SurveyQuestionResponse records (one answer each).
Each record links up to its parent SurveyResponse, to the SurveyQuestion it answers, and back to the Survey and Survey Version. The answer itself lands in a field that depends on the question type. A choice picks up a ChoiceId, free text fills a text field, a rating or NPS score fills a numeric field, and a date question fills a date field. Because the answer can sit in different places, reading this object well means knowing the question type first.
How question type decides where the answer lives
One submission, many answer rows
Salesforce Surveys splits a single submission into two layers. The SurveyResponse object holds the completion record: who responded, the status, the location, and when it finished. The SurveyQuestionResponse object holds the answers, one record per answered question. The two are joined by a lookup from each answer back to its parent response. This split is what makes the data useful for reporting. You can count completions at the response layer and study answer distributions at the question layer without mixing the two. A survey with three sections and twelve questions produces one response record and up to twelve answer records per participant. Skipped questions simply do not generate an answer row, which is why skip counts matter when you read the numbers. The same split also keeps the model honest across versions. Each answer points at the Survey Version it was captured under, so a question reworded in version three does not silently blend with version two. When you aggregate by version, you compare like with like. That is the foundation every CSAT, NPS, and feedback dashboard sits on.
The answer field changes with the question type
The trickiest part of this object is that the answer does not always live in the same field. A single-select or multi-select question stores a ChoiceId that points at the chosen SurveyQuestionChoice. A free-text or long-text question stores the words the respondent typed. A rating, score, slider, or NPS question stores a numeric value. A date or time question stores a date value. So a raw query against SurveyQuestionResponse returns rows of mixed shape. One row carries a choice reference and an empty text field, the next carries text and an empty number, the next carries a number. Code that reads these records has to branch on the question type before it can pull the right field. That is why ad-hoc SOQL against this object feels awkward. Most teams avoid the problem by reporting through standard Salesforce Reports or CRM Analytics, both of which understand the structure and present the right value per question. The lesson for builders is simple. Always read the SurveyQuestion type first, then reach for the matching answer field.
Linking answers back to the record that triggered the survey
The Survey Subject is the bridge between feedback and the rest of your CRM. A SurveySubject record ties a survey response to another object, such as a Case, an Account, a Contact, or an Opportunity. Because every answer rolls up to a response, and the response carries the subject, each individual answer is effectively tied to the record that prompted the survey. This is where the real value shows up. With the subject in place you can ask questions that join feedback to operational data. Average CSAT for Cases closed by each support queue. NPS grouped by the customer success manager who owns the Account. Response rate by Account tier. None of that needs a custom integration, because the link is built into the standard model. Set the subject when you send the invitation, usually through Flow, the invitation API, or a survey embedded on a record page. If the subject is missing, the answers still save, but they float free of any CRM context and you lose the join. Treat the subject as part of the design, not an afterthought, whenever cross-object reporting is a goal.
Reading the data without raw SOQL
You rarely need to query this object by hand. The Survey Builder includes an Analyze tab that shows response data per question and lets you export it for outside tools. For score questions like NPS, rating, score, and slider, the report shows each participant score and the aggregate average. For choice questions it shows the share of participants who picked each option. For ranking questions it shows ranked weights, and for date questions it shows selected dates with counts. Beyond the builder, custom report types open the same data inside the standard report engine. The Survey Question Score report type covers every question type except short text and long text, and each row carries the invitation, the question, response counts, and skip counts. Text answers are handled separately because counts and averages do not apply to free prose. For larger programs, Customer Lifecycle Analytics dashboards ship prebuilt views on top of this data, including a dashboard built around natural language processing. The point across all three paths is the same. Let the tooling resolve the per-type answer field so you do not have to.
Anonymous responses change what you can analyze
Salesforce Surveys lets you collect responses anonymously, and that choice ripples down to the answer records. When a survey runs in anonymous mode, the answers save without identifying the respondent and usually without a Survey Subject link. That protects people giving sensitive feedback, which is exactly what you want for employee engagement or an exit interview. The trade is real. Without the subject and the respondent identity, the cross-object joins described above stop working. You can still see the distribution of answers per question, but you cannot tie a low CSAT score back to a specific Case or a particular account. So anonymous mode and deep operational analysis pull in opposite directions. The fix is to decide the mode by use case before you launch, not after. Customer satisfaction and product feedback usually benefit from named responses, because the analytical depth is the point. Confidential internal surveys usually need anonymity, and you accept the lighter analysis in exchange. Switching mode after launch does not retroactively add identity to data already collected, so this is a design decision worth getting right the first time.
Volume, text answers, and where the limits bite
Answer records pile up fast. A program sending thousands of invitations a month, each with several questions, generates tens of thousands of SurveyQuestionResponse records in short order. That volume is fine for the platform, but it shapes how you analyze. Free-text answers in particular do not scale to manual reading much past a few hundred per quarter before a human reviewer falls behind. This is why Salesforce Feedback Management adds sentiment and natural language processing on top of raw answers. NLP services can pull entities, key phrases, and sentiment out of text answers so you spot themes without reading every comment. Setting up sentiment insights involves connecting an external NLP service, after which the text-based answers feed into dashboards. Entitlement also matters at scale. Feedback Management Starter includes a fixed pool of responses, while Growth lifts that cap and adds lifecycle tracking. Plan capacity against your expected response volume, because the count is at the response layer and each response can spawn many answer records. Knowing where the limits sit keeps a fast-growing feedback program from stalling on either headroom or human review time.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Survey Question Response.
Hands-on resources to go deeper on Survey Question Response.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Discussion
Loading discussion…