ForHosting KIT · Developer Utilities

Calculate Survey Response Rate from Sent and Completed Surveys

Survey response rate shows what share of the people you contacted completed your survey.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

Enter the total number of surveys sent and the number completed to receive the percentage immediately. The calculator applies the standard completed-divided-by-sent formula, validates that the counts are usable, and returns a stable result suitable for reports, dashboards, campaign reviews, and automated research workflows. It also rejects a zero sent count because no meaningful response rate can be calculated without invitations.

Start with counts that describe the same survey effort

A useful response rate begins with two counts drawn from the same campaign, distribution window, and audience. The surveys sent value should represent the invitations that belong in your reporting denominator, while surveys completed should count the finished responses attributed to those invitations. Before calculating, decide how your team handles bounced email, duplicate invitations, test submissions, partial responses, and reopened questionnaires. That policy matters because changing the denominator or numerator changes the result even when the arithmetic is flawless. Enter whole, non-negative counts rather than estimates or formatted text. The completed count cannot be larger than the sent count, since every completed survey must correspond to one that was sent within this simple model. If you need to compare several waves, calculate each wave separately first. Keeping each cohort distinct makes differences in timing, channel, audience, and questionnaire design visible instead of blending them into an average that may hide a weak campaign. Record the chosen counting policy beside the result so colleagues can reproduce it later.

Understand the formula and the returned percentage

The calculation divides surveys completed by surveys sent and multiplies the quotient by one hundred. For example, a campaign with two hundred completed surveys from eight hundred sent surveys has a response rate of twenty-five percent. The result answers a specific question: what proportion of distributed surveys produced completed responses? It does not measure whether the sample is representative, whether respondents answered carefully, or whether the questionnaire reached the intended population. The calculator rounds only the final percentage to six decimal places, preserving enough detail for small campaigns and downstream comparisons while keeping the JSON output stable. A zero sent count produces an error because division by zero cannot describe participation. Zero completed surveys with a positive sent count is valid and produces zero percent. When presenting the result, choose display precision appropriate to the audience; a dashboard might show one decimal place, while an analysis file can retain the returned value. Always keep the underlying counts nearby, because identical percentages based on ten invitations and ten thousand invitations carry very different levels of evidence.

Use response rate as a diagnostic, not a quality verdict

Response rate is most valuable when compared consistently across survey waves, invitation channels, reminders, or audience segments. A falling percentage can prompt a review of subject lines, survey length, mobile usability, incentive design, contact timing, or list quality. A rising percentage may indicate that those changes helped, but it should still be interpreted with completion quality and sample composition. Avoid comparing rates produced under different counting rules without explaining the difference. One team may exclude undeliverable invitations while another leaves them in surveys sent, creating unequal denominators. For operational reporting, store the two input counts and the calculated percentage together, then annotate the reporting period and inclusion rules in your own system. Automation can call this capability for each completed campaign at $0.002 per request, ensuring the same validation and formula are used every time. The calculation contains no network access, randomness, or current-time dependency, so identical inputs always return identical outputs. That determinism makes it suitable for scheduled dashboards, quality checks, experiment summaries, and reproducible research records.

Review an outreach campaign

Calculate the share of distributed customer surveys that became completed responses after a campaign closes.

Compare survey waves

Apply the same formula to each wave so participation trends can be compared on a consistent basis.

Populate a research dashboard

Generate a validated response-rate field from stored sent and completed counts in an automated reporting workflow.

How is survey response rate calculated?

Divide surveys completed by surveys sent, then multiply by one hundred to express the result as a percentage.

What happens when surveys sent is zero?

The calculation returns an invalid-input error because a response rate cannot be defined with a zero denominator.

Can completed surveys be greater than surveys sent?

No. This calculator rejects that input because completions must belong to the surveys represented by the sent count.

Are partial responses counted as completed?

Only if your reporting policy classifies them as completed. Decide that policy before entering the completed count and apply it consistently.

How much does an automated calculation cost?

Each API request costs $0.002. The same deterministic formula can also support consistent recurring reports.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/biz/survey-response-rate-calc

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/biz/survey-response-rate-calc \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"surveys_sent":800,"surveys_completed":236}'
{
  "surveys_sent": 800,
  "surveys_completed": 236
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "biz.survey_response_rate_calc",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →