Customer Feedback Collection System

Purpose

This recipe builds a complete customer feedback collection system: NPS, CSAT, and CES surveys configured with trigger-based distribution, an analysis pipeline that turns raw scores into prioritized action items, and a closed-loop workflow that follows up with every respondent. The output is a configured survey platform, automated alert rules, an analysis dashboard, and documented close-the-loop processes. [src1]

Prerequisites

• Customer contact list — email addresses for at least 100 customers, segmented by tenure, plan tier, or lifecycle stage
• Customer journey map — key touchpoints identified (onboarding, support, feature release, renewal)
• Communication channel access — ability to send emails, embed in-app widgets, or configure post-interaction triggers
• CRM or customer database — system of record for customer data (HubSpot, Salesforce, spreadsheet)
• Team owner assigned — one person responsible for reviewing feedback weekly and routing action items

Constraints

• Survey fatigue: keep transactional surveys (CSAT, CES) to 1-2 questions plus one open-text field. Completion rates drop 15-20% per additional question. [src2]
• NPS response rates average 4.5-12% via email. Achieve statistical significance by surveying at least 250 customers per NPS cycle. In-app surveys can reach 20-40% response rates. [src2]
• GDPR/CCPA compliance: include opt-out mechanism in all survey communications, store responses with retention policies, and do not share individual feedback externally without consent.
• Follow up with detractors (NPS 0-6) and low scorers (CSAT 1-2) within 24-48 hours. [src3]
• Do not send NPS and CSAT surveys in the same interaction. Use NPS for relationship health (quarterly) and CSAT for transactional quality (post-event). [src5]

Tool Selection Decision

Which path?
├── Non-technical AND budget = free
│   └── PATH A: No-Code Free — Google Forms + Sheets + manual follow-up
├── Non-technical AND budget > $0
│   └── PATH B: No-Code Paid — Typeform + Zapier + Sheets/Notion
├── Semi-technical or developer AND budget = free
│   └── PATH C: Code + Free — Google Forms + Sheets + Apps Script automation
└── Already using HubSpot/Zendesk AND budget > $50/mo
    └── PATH D: CRM-Integrated — HubSpot Service Hub or Zendesk surveys

Execution Flow

Step 1: Choose Survey Types and Map to Touchpoints

Duration: 30-60 minutes · Tool: Spreadsheet or document

Define which metric to use at each customer touchpoint. NPS measures relationship loyalty (quarterly). CSAT measures transaction satisfaction (post-event). CES measures effort to complete a task (post-support/self-service). Map each touchpoint to exactly one survey type. [src4]

Verify: Every key touchpoint has exactly one survey type assigned. No touchpoint triggers more than one survey within 7 days. · If failed: If uncertain, default to CSAT for transactional moments and NPS for periodic relationship health checks.

Step 2: Configure Survey Tool and Create Surveys

Duration: 1-2 hours · Tool: Typeform (Path B), Google Forms (Path A/C), or HubSpot (Path D)

Create one survey per type: NPS (0-10 scale + conditional open text), CSAT (1-5 scale + optional text), CES (1-7 scale + optional text). Add conditional logic to branch follow-up questions by score range. Connect responses to a spreadsheet or CRM. [src5]

Verify: Each survey loads correctly, conditional logic works (test with scores 3, 7, and 10 for NPS), and responses appear in connected spreadsheet or dashboard. · If failed: If conditional logic does not work in Google Forms, create separate forms per score range. Typeform and HubSpot handle branching natively.

Step 3: Set Up Survey Triggers and Distribution

Duration: 1-2 hours · Tool: Zapier (Path B), Apps Script (Path C), or HubSpot Workflows (Path D)

Configure automated triggers: CES 1 hour after support ticket closes, CSAT 24 hours after onboarding milestone, NPS on quarterly schedule. Enforce a 30-day cooldown per customer to prevent survey fatigue. Throttle batch sends to 50 emails per batch. [src1]

Verify: Send a test trigger for each automation. Confirm survey arrives within configured delay and responses route correctly. · If failed: If Zapier free tier runs out of tasks, batch NPS sends manually and automate only detractor alert routing.

Step 4: Build the Analysis Pipeline

Duration: 1-2 hours · Tool: Google Sheets (Path A/B/C) or HubSpot Reports (Path D)

Create a dashboard with tabs for: raw responses, NPS trend tracker (quarterly NPS score + response rate), CSAT by touchpoint (bar chart), CES by interaction type, open-text theme tags, and prioritized action items sorted by severity times frequency. [src3]

Verify: Dashboard populates correctly with test data. NPS formula returns a number between -100 and 100. CSAT percentages are between 0% and 100%. · If failed: Simplify to manual NPS calculation. Add complexity once the basic flow works.

Step 5: Create Action Workflows and Escalation Rules

Duration: 30-60 minutes · Tool: Zapier + Slack/Email (Path B), or HubSpot Workflows (Path D)

Define score-based routing: NPS 0-6 triggers immediate Slack alert + CRM task (4-24h follow-up SLA). NPS 7-8 logs for passive nurture. NPS 9-10 triggers thank-you + review request. CSAT 1-2 alerts support lead. CES 1-3 aggregated weekly for product team review. [src6]

Verify: Send test responses at each score level. Confirm alerts fire to correct channels and the correct owner is notified. · If failed: Start with a single rule (NPS 0-6 sends Slack message) and add additional rules weekly.

Step 6: Close the Loop with Customers

Duration: Ongoing (15-30 minutes per week) · Tool: Email + CRM

Follow up with every respondent: detractors get personal outreach within 24-48h referencing their specific comment, passives receive a one-question follow-up, promoters are asked for reviews or referrals. Send monthly product update emails referencing feedback-driven changes. [src3] [src6]

Verify: Every detractor has a follow-up logged in CRM within 48 hours. At least one product update email sent per month referencing customer feedback. · If failed: If volume exceeds capacity, prioritize by account value. Enterprise detractors get calls; SMB detractors get emails.

Output Schema

{
  "output_type": "feedback_collection_system",
  "format": "configured platform + dashboard + documented workflows",
  "columns": [
    {"name": "nps_survey_configured", "type": "boolean", "description": "NPS survey created and trigger rules active", "required": true},
    {"name": "csat_survey_configured", "type": "boolean", "description": "CSAT survey created for at least 2 touchpoints", "required": true},
    {"name": "ces_survey_configured", "type": "boolean", "description": "CES survey created for support/self-service", "required": true},
    {"name": "trigger_automations_active", "type": "number", "description": "Number of automated survey triggers configured", "required": true},
    {"name": "analysis_dashboard_built", "type": "boolean", "description": "Dashboard with NPS trend, CSAT by touchpoint, CES tracker", "required": true},
    {"name": "detractor_alert_active", "type": "boolean", "description": "Automated alert fires for NPS 0-6 and CSAT 1-2", "required": true},
    {"name": "close_loop_templates", "type": "number", "description": "Number of follow-up email templates created", "required": true},
    {"name": "first_nps_score", "type": "number", "description": "Baseline NPS score from first survey cycle", "required": false}
  ],
  "expected_row_count": "1",
  "sort_order": "N/A",
  "deduplication_key": "nps_survey_configured"
}

Quality Benchmarks

If below minimum: If NPS response rate is below 5%, switch from email-only to in-app surveys or add an incentive. If detractor follow-up rate is below 70%, simplify the escalation workflow and assign one owner for all detractor responses.

Error Handling

Cost Breakdown

Anti-Patterns

Wrong: Collecting feedback and never acting on it

Surveys without follow-up are worse than no surveys. Customers who give feedback and see no change become more frustrated. Response rates decline on subsequent surveys when feedback goes unacknowledged. [src3]

Correct: Act on the top 3 themes monthly and communicate changes

Review open-text themes weekly. Prioritize the top 3 by frequency and severity. Take action on at least one each month and send a product update email referencing the feedback.

Wrong: Sending NPS surveys after every support interaction

NPS measures relationship loyalty over time. Sending it after a single interaction conflates transaction satisfaction with brand loyalty, producing scores that fluctuate wildly and mean nothing. [src5]

Correct: Use CSAT or CES for transactional moments, NPS for periodic relationship health

CSAT after support tickets. CES after self-service. NPS quarterly. Each metric has a purpose — using it at the wrong moment produces unreliable data.

Wrong: Only surveying happy customers

Cherry-picking who receives surveys produces inflated scores that hide real problems. When churn spikes, leadership is blindsided because the metrics looked fine. [src2]

Correct: Survey all segments including at-risk accounts

Include every customer segment in survey distribution. Analyze results by segment (plan tier, tenure, usage level) to find hidden dissatisfaction.

When This Matters

Use this recipe when a company needs to build a customer feedback collection system from scratch — from survey tool selection through closed-loop follow-up workflows. Requires a customer contact list and identified touchpoints. This recipe handles survey configuration, trigger automation, analysis dashboards, and close-the-loop processes.