All case studies
05 · SaaS · reporting & automation
Alchemer: survey reporting and campaign workflows
Enterprise customers filter large response sets down to the answers they need, and survey answers drive scheduled email and SMS follow-ups.
- Client
- Alchemer (via Go Interactive)
- Role
- Senior software engineer
- Period
- Apr 2024 – Oct 2025
Problem
Alchemer is an enterprise survey and feedback platform on a legacy Zend PHP back end and a Vue.js front end.
Its customers needed to analyze big response sets by specific questions and answers, and to follow up with respondents by email and SMS on a schedule, depending on how they answered.
How it works
- 01Build the workflowIn the visual builder, users drag and drop email and SMS steps and set when and how often each one runs.
- 02Collect responsesSurvey answers arrive at scale and are searchable in Elasticsearch.
- 03Branch on answersThe next workflow step depends on the survey response.
- 04Send email or SMSSMS goes out through the Twilio delivery flow; email through the email campaign system.
- 05ReportFilters by question and answer type slice the responses, with charts and graphs on the result.
What I built
- Built Elasticsearch reporting with filters by question and answer type across large response sets.
- Added report building with charts and graphs on the filtered data.
- Took over the dynamic email and SMS workflow builder (drag-and-drop steps, a scheduled time and frequency for each step, next steps that branch on survey responses): shipped new features, fixed long-standing bugs and wrote its first documentation.
- Delivered workflow automation that applies custom campaign settings to surveys from the visual builder.
- Built the SMS campaign delivery flow on Twilio, improved SMS campaigns and shipped email campaign features.
- Shipped survey theme selection and other features across the Zend back end and Vue.js front end.
Key decisions
- A search index for reporting
- Responses are searchable in Elasticsearch, so reports filter large response sets by any question and answer.
- Understand it, then fix it
- The workflow builder had no documentation and long-standing bugs, so the first step was mapping how it works end to end; the fixes and the new features followed, and the docs stayed for the team.
Result
Over 1.5 years, shipped reporting, a stable and documented workflow builder and SMS campaign improvements on a platform used by enterprise customers.
media note
Screenshots of this client system aren’t published here, so this case study uses words and a diagram.