Was the import successful? Product Survey Question
Quickly validate your import feature's reliability and catch technical issues before they compound into user frustration and data migration problems.
Question type
Yes/No binary choice
Primary metric
CSAT (Customer Satisfaction Score)
Answer scale variations
| Style | Options |
|---|---|
| Typical choice | No Yes |
| Success-focused | Failed Successful |
| Outcome-based | Import failed Import succeeded |
| Direct status | Unsuccessful Successful |
Follow-Up Questions
Understanding what happens after an import attempt is crucial for improving your data migration tools. These follow-up questions help you diagnose failure patterns and identify friction points in the import process.
This gives you structured data on common failure modes, making it easier to prioritize which import issues to fix first based on frequency.
Open-ended context reveals edge cases and specific scenarios that your structured questions might miss, especially useful for debugging complex data transformation issues.
Knowing which file formats cause the most problems helps you focus compatibility improvements where they'll have the biggest impact on success rates.
When to Use This Question
SaaS Products: Show this immediately after the first data import completes, via an in-app modal that appears before users navigate away from the import results screen, because catching problems while users are still in the import context dramatically increases the chance they'll provide actionable details about what went wrong.
E-commerce: Trigger this within 2 minutes of completing a bulk product upload or inventory sync, using a slide-in notification in the admin dashboard that doesn't block their workflow, because merchants need to verify their catalog data loaded correctly before customers start browsing, and timing it this tightly lets them fix issues before going live.
Mobile Apps: Display this on the confirmation screen right after users finish importing contacts, photos, or other personal data, as a native bottom sheet that feels like a natural part of the flow, because users are most invested in verifying success at this exact moment and will remember specific details if something failed.
Web Apps: Present this within 30 seconds of completing a file upload or integration sync, through an embedded banner at the top of the import results page, because users are still looking at what just happened and can immediately confirm whether the expected data appeared correctly or report discrepancies they're actively seeing.
Digital Products: Show this 5-10 seconds after users finish importing their existing content, settings, or configurations during onboarding, via a dismissible toast notification that doesn't interrupt their exploration, because this timing validates their migration experience while they're still evaluating whether your product handles their data properly, which directly impacts early retention decisions.
Related Questions
- Did you find what you were looking for using the search?
- Was this article helpful?
- Did this feature work as expected?
- Was the checkout process easy?
- Did you accomplish what you came here to do?
- Was this information useful?
- Did this solve your problem?
- Was this page helpful?
- Was the setup process clear?
- Did this answer your question?
- Was this tutorial easy to follow?
- Did this feature meet your expectations?
- Did you get what you needed?
- Was this documentation clear?
- Did this workflow make sense?
- Did this tool do what you expected?
- Did we meet your expectations?
- Did our product meet your expectations?
- Did our service meet your expectations?
- Was your issue resolved to your satisfaction?
- Did we resolve your issue on first contact?
- Was the support agent polite and respectful?