Feedback that becomes Salesforce action
AutoSurvey lets Salesforce teams collect feedback as part of the process, not after it. Drop survey steps into Flow, personalize from CRM data, route on answers, and turn every scored response into Salesforce action — without sending feedback to a separate survey cloud.
Prefill and personalize from the CRM record.
Branch and validate on the answers as they come in.
Score the response, write it to records, trigger the next step.
A Case closes. Salesforce sends the survey. The customer gives it a two. Most tools would drop that score into a dashboard nobody opens until Friday. AutoSurvey stamps the score onto the response record the moment it's submitted — the Flow updates the Case, opens a recovery Task for the owner, escalates the severe complaints to the service manager, and the whole thing lands in dashboards your team already reads. No exported spreadsheet. No second survey cloud to reconcile.
Your process reaches the point where feedback matters — and the send action fires from your own record-triggered Flow.
Salesforce emails each contact a unique invitation link — the same engine behind Campaign and list sends.
The response lands as a Salesforce record with the primary score, metric type, and band stamped as fields — plus a negative-score flag.
Update the Case, open a recovery Task, route detractors to a manager — standard Salesforce automation on the scored record.
Native Salesforce reports on packaged report types — no export, no second tool. Build your own dashboard on top with one admin click to open the folder.
Salesforce sends the survey to the contact.
The response lands as a Salesforce record.
The team reads it in a native Salesforce report.
The acting step runs in a record-triggered Flow you configure — standard Salesforce automation on the scored response record, not a proprietary rules engine.
Wherever the audience lives, the send starts in Salesforce and the responses come home to it.
Pick the Campaign and send. Every member gets their own invitation link, and invitations and responses are attributed back to the Campaign Member.
Paste addresses. AutoSurvey matches existing Contacts and Leads, optionally creates Leads for the rest — with explicit admin confirmation — and sends. No Campaign required.
Run it on a public Experience Cloud page — CAPTCHA'd and rate-limited — share the link, or copy a QR code straight to the clipboard. Or keep it behind login for internal teams.
Drop the "Send AutoSurvey Invitation" action into any record-triggered Flow — Case closed, Opportunity won, onboarding complete — and the invitation goes out the moment the process gets there.
Sending safeguards & auditability
However it's launched, the response lands in Salesforce ready for scoring, Flow, and reporting.
Post-case CSAT that fires when the Case closes. Every response is scored on arrival — detractors get escalated to a manager, recovery Tasks land on the owner, and the Case updates from the score. Your service queue does the follow-up, not a separate feedback inbox.
Lead-qualification surveys that qualify during the survey and route high-intent responses straight to the right rep the moment they submit. Enrich the Lead from the answers and trigger SDR follow-up while the intent is fresh. Most survey tools make this a custom integration project; here the response is already a Salesforce record.
Campaign and event feedback attributed back to the Campaign Member, with standard Salesforce automation to segment respondents into the right nurture. Moving off a legacy tool? Import the survey structure and make it Salesforce-native.
GetFeedback, Typeform, Google Forms & SurveyMonkey import.
Start from a prompt, paste a question list, bring a spreadsheet or CSV/JSON, or import an existing survey. AutoSurvey turns rough inputs into a Salesforce-native survey — no dragging questions in one at a time. AI-assisted authoring is included; no Agentforce project, no separate Salesforce AI license to buy.
Tell AutoSurvey what you want to learn, or give it a page to read, and it drafts real questions with the right Salesforce field types. Tune tone and persona so it doesn't sound like a robot wrote it. Then you edit, because you know your customers.
Ground it in your business — paste a product or campaign URL and AutoSurvey grounds the questions in what's on the page.
Already drafting in ChatGPT, Claude or Gemini? Grab our authoring prompt →
Already have the questions written down? Paste the list, or bring a spreadsheet, CSV, or JSON, and AutoSurvey builds the whole survey at once. No blank canvas, no clicking questions in one at a time.
Questions already in a spreadsheet? Google Sheets, Excel, or CSV works as an entry point. Bring it in once, then run the survey natively in Salesforce.
Bring surveys over from GetFeedback, Typeform, and Google Forms by pasting the public link, or connect SurveyMonkey (API-assisted). The structure comes with you — you make it Salesforce-native from there.
Moving off GetFeedback? GetFeedback Direct retires December 31, 2026. Bring the survey structure with you, then make it native to Salesforce. See the GetFeedback guide
Step-by-step migration guides: all providers · GetFeedback · Typeform · SurveyMonkey · Google Forms
Salesforce-aware question and storage types
However the survey starts, it ends up native. Refine it, publish it, and drop it into the Salesforce Flow that sends it, routes on the answers, writes back to the record, and follows up.
Every response is stored in your org, reportable in Salesforce, available to Flow, and governed by your admins. When someone answers, the record already lives where your team works.
The shape most admins expect: one row per submission, each question its own field, plus Audience, Wave/Round, Started, Completed and Status. Because it's a normal object, native Salesforce Reports & Dashboards work on it out of the box — group by Audience, chart % Completed, no extra setup.
One row per answer (question key + value), so the schema never changes when your questions do. Ideal for tracking results across changing question sets and for feeding BI tools like Tableau or CRM Analytics — a tall answer table is exactly what they want for pivots, trends and cross-survey analysis.
Response data stays in your Salesforce org. AI authoring uses hosted Claude and only ever sees what you send it to draft a survey — a prompt or a page URL, never a response.
Per-suite insights in the app — completion, NPS, drop-off — before you build a single report.
Score trends and bands ship as native report types and reports — one admin click to share the folder in Setup Home, then build your own dashboard on top with standard Salesforce tools. No dashboard to buy or wait on.
Six export formats, from a flat submission list to a full analysis package for Tableau or CRM Analytics.
Flag junk responses out of analytics without deleting them, and grant a retake when someone deserves one.
AutoSurvey is a managed package that runs on the controls you already own. Your data, your permissions, your Flow.
Installs clean, runs on standard Salesforce metadata, and your admins govern it like anything else in the org.
Response data is stored as records in your Salesforce org. It doesn't get shipped to a vendor's survey cloud.
You compose the survey into your own Flow and control exactly what it reads, writes, and triggers. Scored responses are records — your Flows, permissions, and sharing rules decide what happens next.
Profiles, Permission Sets, Sharing, and Field-Level Security apply the way they do everywhere else in Salesforce.
Suppression and unsubscribe, org-level daily caps, and an append-only consent audit trail on every send channel.
The respondent experience is hardened against WCAG AA criteria — keyboard, screen reader, and contrast included.
Run behind login or on a public Experience Cloud page, with CAPTCHA and rate-limiting for guests.
Runs on-platform; a formal security-review path follows as we approach AppExchange listing.
AutoSurvey is pre-GA. Founding customers get direct implementation support and staged access to the process-native runtime as it hardens.
Some Salesforce survey tools are strong at native collection and mapping. AutoSurvey is built so the response itself is something your automation can act on. Here's the categorical split.
| Old model | AutoSurvey model |
|---|---|
| Survey lives outside the process | Survey becomes a step in the process — a screen inside your own Flow |
| External-tool automation may depend on a sync or mapping layer | Responses are already Salesforce records, with score fields your Flow can branch on the moment they're submitted |
| A separate dashboard is the work queue | Salesforce records and Tasks are the work queue |
| Proprietary survey automation to learn | Salesforce Flow orchestration your admins already govern |
| AI may need separate Salesforce AI licensing | AI-assisted authoring included, no Agentforce project |
"Old model" describes the common non-process-native pattern, not any one vendor. Comparisons are categorical.
Founding partners
AutoSurvey is in early access, ahead of our AppExchange listing. We're working directly with a small group of Salesforce teams, free while we do, and locking in founding pricing for anyone who stays. Three months free in your sandbox now, three more in production the day we list on the AppExchange. You get the full product and a direct line to the founder. We get honest feedback on a real survey.
Everything AutoSurvey does today, in your sandbox first and in production at launch. No card, no response cap.
Leaving GetFeedback or Delighted? We'll give you a hands-on migration plan before you commit. GetFeedback structure import is available today; other structures and historical data are assessed separately.
Two or three short calls. What you flag tends to ship. Founding pricing is locked in if you continue.
Limited to a handful of founding partners. Prefer not to book yet? Send a few details instead.
A couple of details and we'll figure out whether AutoSurvey fits where you need feedback to trigger action.
Erik reads these himself and usually replies within a day. Want to skip ahead? Grab a 30-minute slot.
Founding customers are shaping the process-native runtime right now — the send, capture, scoring, and reporting run today, and the orchestration hardens with the people using it.