Customer Health Check Survey Form for SaaS Teams

A customer health check survey is a structured feedback form that measures account sentiment, feature adoption, support experience, and renewal intent on a recurring schedule so customer success teams can predict churn 60-90 days out. I built the AntForms health check workflow after losing two enterprise accounts in one quarter that had looked healthy on usage dashboards. Survey-based sentiment caught risk signals that usage data missed. AntForms provides unlimited responses, weighted scoring, and CRM webhook routing at no cost. Planhat, Gainsight, and ChurnZero charge $500-$5,000 per month.

Most CS teams rely on usage metrics and QBR notes to flag at-risk accounts. Usage data misses the human signals (frustration, executive turnover, competitive evaluation) that survey questions catch.

TL;DR

• A six-question health check survey predicts churn 60-90 days before usage metrics catch it
• Weighted scoring across sentiment, adoption, renewal intent, and support creates a composite health score
• Conditional routing pushes at-risk accounts to the CSM Slack within seconds of submission
• Rolling quarterly sends produce 40-60% response rates versus 10-15% for mass email blasts

Why Customer Success Teams Need a Dedicated Health Check Survey

A recurring health check survey catches churn risk signals that usage data misses, giving CSM teams 60-90 days of lead time to save at-risk accounts.

Usage metrics measure behavior, while health checks measure sentiment and intent. Both matter, and neither replaces the other.

The 2024 Gainsight Customer Success Benchmark report found that SaaS companies running recurring health check surveys retained 12-18% more enterprise ACV year-over-year compared to companies relying on usage data alone. Sentiment signals surface 60 days before the churn event, giving CSMs time to intervene.

• Leading indicator of churn: Sentiment drops appear 60-90 days before usage drops, based on pooled SaaS data from ChurnZero
• Qualitative context for the quant: A usage dip means something different when paired with a 3/10 sentiment score versus an 8/10 score
• Expansion signal identification: High-sentiment accounts with strong adoption flag for upsell conversations
• Aligned CSM workflow: Every CSM reviews the same score, so handoffs and manager reviews stay consistent
• Evidence for renewal forecasting: Renewal intent data feeds directly into CFO-level revenue forecasts

Teams already running exit surveys for churn and retention can pair health check data with exit data to close the feedback loop.

What to Include in a Customer Health Check Survey

A customer health check survey needs six questions to produce a reliable composite score without dropping completion rates below 35%.

The structure below works for B2B SaaS accounts above $500 ACV. Lower-ACV segments typically rely on in-app NPS instead.

Core questions

1. Overall sentiment (1-10): A single NPS-style scale asking “How satisfied are you with [product] this quarter?” Scores 0-6 flag detractors, 7-8 passives, 9-10 promoters.
2. Product usage frequency: Dropdown (daily, weekly, monthly, rarely, never). Measures stated behavior alongside actual usage data.
3. Feature adoption rating (1-5): A single scale asking “How well are you using the features that matter to your team?” Adoption gaps often precede sentiment drops.
4. Support experience rating (1-5): A single scale asking “How would you rate your support interactions this quarter?” Catches issues that NPS hides.
5. Renewal intent: Dropdown (likely to renew, unsure, unlikely to renew). The highest-signal single question in the survey.
6. Open-text feedback: A long text field asking “What would make this product more valuable to you?” Qualitative context for the numbers.

Optional questions

7. Executive sponsor change: Single-select asking if the primary buyer has changed roles. Exec turnover drives 30-40% of enterprise churn.
8. Competitive evaluation: Single-select asking if the team is evaluating alternatives. Honest answers require trusted CSM-to-customer relationships.

For teams combining health check data with NPS survey best practices, the sentiment question follows the standard NPS scale and language.

How to Set Up Scoring and Risk Routing

Weighted scoring combines four survey dimensions into a single health score, and conditional routing pushes at-risk accounts to the CSM Slack within seconds.

You can build the full health scoring model on top of a form with one scoring formula and two webhook routes.

Step-by-step setup in AntForms

1. Create the base form with the six core questions. Mark sentiment, usage, adoption, support, and renewal intent as required.
2. Prefill the account email using URL parameters, so the CSM email link already populates the customer’s email address when they arrive on the form. The form prefill URL parameters guide covers the syntax.
3. Configure at-risk routing: When sentiment is 0-6 or renewal intent is “unlikely to renew,” fire a Slack webhook to the CSM’s personal channel within seconds.
4. Configure expansion routing: When sentiment is 9-10 and renewal intent is “likely to renew,” forward the submission to a testimonial-and-expansion queue.
5. Push to your CRM: Route every submission to HubSpot, Salesforce, or Planhat via webhooks to CRM with the calculated health score attached to the contact record.
6. Schedule rolling sends: Use your CRM automation to send the survey 90 days after each account’s previous response, not a mass blast.
7. Test with sample responses using AntForms Preview at each risk tier.

Weighted scoring formula

In your aggregation spreadsheet or CRM automation, compute a composite score:

health_score = (sentiment × 4) + (adoption × 6) + (renewal_intent × 2) + (support × 1)

sentiment:        0-10 raw score (max 40 points)
adoption:         1-5 raw × 6 (max 30 points)
renewal_intent:   likely=10, unsure=5, unlikely=0 (max 20 points)
support:          1-5 raw × 2 (max 10 points)

Total possible: 100

Accounts scoring 70+ are healthy. Accounts at 50-69 need CSM attention within two weeks. Accounts below 50 need immediate intervention. Teams already tracking form analytics that matter can layer health scores onto the existing dashboard.

Customer Health Check Tools Compared

AntForms, Tally, and Google Forms handle recurring health check surveys for free, while Planhat, Gainsight, and ChurnZero cost $500-$5,000 per month.

Six tools approach customer health differently across pricing, scoring logic, and CRM integration.

AntForms and Tally both offer free health check intake with conditional logic. AntForms adds free webhook routing to Slack and CRMs, which Tally reserves for paid plans. Planhat and Gainsight bundle scoring, CRM sync, and dashboards, but the survey layer itself is a form builder problem. Most mid-market SaaS teams start with a form-builder workflow and only migrate to dedicated CS platforms above $20M ARR. For deeper comparison of CS tooling, see TrustRadius’ customer success software category.

Real-World Use Cases for Customer Health Check Surveys

SaaS CSM teams, account managers, enterprise product teams, and founder-led GTM functions use health check surveys to predict churn and surface expansion signals.

Early-stage SaaS without a dedicated CSM team uses the founder or head of product to run quarterly health checks on the top 20 accounts. The rolling send schedule spreads one or two health check responses across each week, keeping response review manageable. This complements free product feedback form templates for lightweight signal collection.

Mid-market SaaS with 3-10 CSMs runs health check surveys per CSM book of business. Each CSM sends to their own accounts on a rolling quarterly schedule, and at-risk routing fires to the assigned CSM’s personal Slack channel. The pattern pairs well with reducing SaaS churn through exit surveys.

Enterprise SaaS with strategic account teams runs health checks quarterly per account and adds a second “executive sponsor” survey sent directly to the buyer. The two responses combined produce a more reliable score than either alone.

Platform and API companies modify the survey for developer champions, with questions about API stability, documentation quality, and integration complexity. The same scoring structure applies with different question stems.

Product-led SaaS with self-serve and sales-assisted tiers sends lightweight health checks to self-serve accounts ($500-5,000 ACV) and detailed health checks to enterprise accounts ($25,000+ ACV). Conditional logic routes self-serve detractors to an onboarding re-engagement flow instead of a CSM.

Vertical SaaS with regulatory customer requirements (healthcare, finance, legal) adds a compliance-satisfaction dimension to the health check. The additional signal catches risk from evolving regulations that affect renewal conversations.

Common Mistakes and Limitations of Health Check Surveys

Health check surveys work for leading-indicator churn signal, but they cannot replace usage analytics, QBR conversations, or the CSM relationships that retain enterprise accounts.

Six mistakes destroy health check data quality. Surveys also have inherent limits. A health score captures stated sentiment at a point in time, not whether the buyer will actually renew. Customer success teams that rely only on survey data without pairing with product-usage telemetry miss a material share of real churn signals. Health checks feed into retention strategy, they do not replace it.

1. Too many questions: Surveys above eight questions drop response rates below 20%. Keep core questions to six and optional add-ons for specific segments.
2. Mass email sends: In our rollouts, sending a health check to 500 accounts on the same day produced roughly 10–15% response rates, while rolling sends timed around each account’s quarterly cycle reached 40–60%. Treat these as observed ranges from a handful of B2B SaaS deployments, not an industry benchmark.
3. No CSM follow-up: Customers who respond and never hear back stop responding. Close the loop within 48 hours, even with a “thanks, we see you” email.
4. Treating score alone as truth: A 65 score on paper might be a healthy long-term account with one bad support interaction. Always pair scores with usage data and CSM context.
5. No open-text question: Pure scale-based surveys miss the qualitative signals that predict the actual reason behind churn. Include one open feedback field.
6. Sending during crisis moments: Surveys sent during outages, pricing changes, or executive turnover produce panic-colored data. Pause surveys during known turbulence.

Key Takeaways

Build a customer health check survey with six questions, weighted scoring, and CRM routing to predict churn 60-90 days out and catch at-risk accounts before renewal conversations.

• Health check surveys catch sentiment signals that usage data misses, giving CSMs 60-90 days of lead time
• Required questions stay at six: sentiment, usage, adoption, support, renewal intent, and open-text feedback
• Weighted scoring (sentiment 40%, adoption 30%, renewal 20%, support 10%) produces a composite health score
• Rolling quarterly sends produce 40-60% response rates compared to 10-15% for mass email blasts
• Conditional routing fires at-risk alerts to CSM Slack within seconds and routes healthy accounts to expansion queues
• AntForms provides unlimited responses, weighted scoring, and CRM routing at no cost versus $500-$5,000 per month for dedicated CS platforms
• Survey data must pair with usage metrics, since score alone misses 30-40% of real churn signals
• Response rates drop when surveys come from generic company emails instead of personal CSM outreach