G2

Verified User in Supermarkets

Small-Business (50 or fewer emp.)

11/2/2026

"Clean, On-Brand Surveys Made Easy with Smart Branching and Permissions"

4/5

What do you like best about Block Survey?

What I like best about Block Survey is how it lets us build clean, branded surveys and feedback forms that fit smoothly into our customer outreach and internal team check-ins, without forcing us to learn complicated form-building logic. I’m Leno Beer, Business Systems Coordinator at Cascade Community Retail LLC. We’re a Washington-based retail operation with a team of 11–50, and my daily responsibilities include testing new business software, rolling out user training, troubleshooting integrations, and supporting store leadership, frontline staff, purchasing and admin teams. We use forms for a wide range of needs: gathering customer feedback after visits, collecting input from staff on in-store workflows, and capturing simple interest submissions for our special order programs. Before Block Survey, we relied on basic form tools that looked generic, had limited layout options, and made it hard to branch questions based on how someone responded. It was tough to tailor the experience for different respondent groups, and our reports were always very basic.

What stands out for our operation is its flexible visual builder and conditional branching. A couple months back, I built a multi-path survey for customer feedback. If a shopper said they used our special order service, the form would jump to questions about ordering timelines and product selection; if they only shopped in-store, it skipped those sections and asked about checkout and shelf availability instead. I was able to match the form styling to our brand colors and add our logo, so it felt consistent with the rest of our customer communications. We got much more focused feedback, and respondents told us the survey felt shorter and less repetitive. It helped us separate general store feedback from feedback specific to our special order process, so leadership could prioritize adjustments more easily.

I also value the straightforward reporting and permission controls. I can filter responses by date and question category, then export organized results to share with our management team. I can give view-only access to survey summaries to store supervisors, while keeping the form setup and branching rules locked so our configured workflows don’t get accidentally changed.

It won’t replace our retail ERP or inventory platform, so it can’t manage stock counts or purchase orders out of the box. Even with that limitation, Block Survey has become a reliable piece of our tech setup. It makes building smart, on-brand forms for customers and internal staff far less of a headache, cuts down on repetitive survey questions that annoy people, and keeps me from wasting time rigging up janky form workarounds that fall apart easily. Review collected by and hosted on G2.com.

What do you dislike about Block Survey?

One of the most frustrating limitations we hit regularly with Block Survey is the rigid handling of file upload fields, which creates friction whenever we collect supporting notes or images alongside form submissions. We use the platform for customer feedback surveys, internal staff workflow questionnaires, and intake forms for our special order program. There are plenty of scenarios where respondents need to attach photos, such as noting damaged items or sharing reference images for custom requests. The upload component has tight file size caps, and it only accepts a narrow list of file types. Even standard common image formats sometimes fail to upload without a clear error message explaining why. On one occasion, a customer tried submitting a photo reference for a special order, and the upload silently failed. We never received the attachment, and our team followed up with incorrect assumptions about their request, which dragged out resolution time. There is no setting to adjust these restrictions on our end, and we also cannot add custom instructions that appear directly next to the upload box to set clear expectations for respondents.

The analytics dashboard also leaves a lot to be desired for our operational review cycle. We run surveys continuously across different form types, and we need to compare trends week over week and month over month. While basic response counts and individual answers are easy to pull up, the platform does not support custom calculated metrics. We cannot create a rolling satisfaction score or automatically track how many feedback submissions mention specific topics. The tagging system is manual only; there is no option to auto-tag responses based on keywords in open-text answers. That means every time we wrap up a survey period, I have to go through every open-ended response one by one to apply tags. If we skip this step, leadership only gets a raw list of comments with no way to tell which concerns are recurring patterns and which are one-off isolated remarks. This manual tagging work piles up quickly when we run multiple active surveys at once. Review collected by and hosted on G2.com.

What problems is Block Survey solving and how is that benefiting you?

Before we started using Block Survey, managing our feedback and intake forms was a disjointed process. We relied on a mix of free form tools and shared spreadsheets to capture customer comments, gather team input, and collect details for special order requests. Those older tools had very limited layout customization, and branching logic was either missing or clunky to set up. We were forced to send long, one-size-fits-all forms to everyone, whether the respondent was a regular in-store shopper or a customer placing a special order. That created survey fatigue, led to rushed and low-quality responses, and made it hard to separate relevant feedback from unrelated comments. Sorting through all the answers afterward took hours of manual work just to pull out actionable insights for our managers and purchasing team.

Block Survey solves those pain points by giving us a visual, intuitive builder to create branded formswith robust conditional branching. A few months back, we built a combined feedback and special order intake form. We set the logic so the form adapts based on how someone answers the opening question. If a visitor indicated they were submitting a special order request, the form would surface fields for product preferences, desired pickup date and additional notes. If they were only leaving general feedback about their shopping experience, those order-related sections would hide automatically and direct them to questions about checkout, shelf availability and overall service. The form matches our brand styling, so it feels cohesive with our other customer communications. Respondents mentioned the form felt streamlined and not bloated with irrelevant questions, which helped boost our completion rate. We can now capture targeted feedback without asking every person the same long list of questions.

We also get a lot of value from its built-in reporting suite and granular permission controls. After each survey closes, I can filter responses by submission date and form path, then export organized datasets to share summaries with our leadership. I can grant store supervisors view-only access to results, while keeping the core form structure and branching rules locked down. This prevents accidental edits that could break our carefully configured workflows.

It’s not without drawbacks. File upload limits are restrictive, keyword auto-tagging is unavailable, and webhook payloads can be inconsistent when pushing data to our CRM. I still need to manually tag open-ended responses and double-check any data we sync over to other systems. Even so, Block Survey has streamlined how we collect feedback and intake information. It cuts down on repetitive manual sorting, improves response quality, and frees me up to focus on higher priority system maintenance and integration work across our software stack. Review collected by and hosted on G2.com.