Service Delivery Satisfaction Survey Template
Measure satisfaction with a specific, recently completed service so you can spot what broke (timeliness, communication, quality, effort) and route fixes to the right owner. Use the core question set for fast, repeatable tracking, then add optional modules only when you need deeper diagnostics.
Trusted by 5000+ Brands
When to Send a Service Delivery Satisfaction Survey (3 best triggers)
Trigger 1: Immediately after completion (job closed, milestone delivered)
Internal starter target: Send within 24 hours of completion; ask about that specific service instance (adjust after you confirm your baseline response rates and operational constraints).
- Use a short recall window: reference the visit/order/project phase from the last 7-14 days (shorter is better; adjust after your baseline).
- Keep the subject line and first question concrete: "Thinking about your service completed on [date]..."
- Prioritize this trigger when you need actionable fixes by step (arrival, work quality, handoffs).
Send quickly because experience details fade and timing can shift what people report; a patient-experience study found survey timing was associated with reported experiences (survey timing and patient-reported hospital experiences).
Trigger 2: After an issue is resolved (ticket closed, escalation completed)
Internal starter target: Send shortly after closure (often 1-2 hours, same day where possible) so you capture the full effort to resolution; adjust after your baseline.
- Anchor the survey to the resolved case: ticket ID, channel, and closure date.
- Add one question on effort and one on communication quality during resolution.
- Use this trigger when service recovery and "how hard was it" matters more than the original delivery step.
Set simple anti-fatigue rules so the same customer does not get hit repeatedly; use a cooldown and sampling to reduce bias from over-surveying (how to reduce response bias).
Trigger 3: Periodic pulse for ongoing/managed services
Internal starter target: Send monthly or quarterly; ask about a recent window (for example, the last 30 days) rather than "overall" so results stay actionable. Adjust cadence and window after your baseline.
- Use this when the customer experience is continuous (managed services, recurring routes, public services).
- Apply a strict cooldown: internal starter target is to not invite the same contact more than once every 30 days (adjust for volume, contract cadence, and response rates).
- Sample high-volume interactions: internal starter target is to invite about 10%-20% of closed tickets each week to keep volume stable (adjust after your baseline).
Follow recognized survey fielding basics (clear invitations, consistent mode, and predictable reminders) so your results stay comparable over time (AAPOR best practices for survey research).
Must-Ask Questions for Service Delivery (core + optional modules)
"Overall, how satisfied were you with the service you received?"
Why it matters: This is your primary outcome for the specific service instance. You will use it to trend and to spot which teams need attention.
When to use: Include in every run. If you use a 1-5 scale, a common top-box definition is 4-5 (document your definition and keep it consistent).
"The service was completed within the expected timeframe."
Why it matters: Timeliness is a frequent root cause of low satisfaction and repeat contacts. This question tells you if the experience matched your SLA promise.
When to use: Use on every transaction survey; keep the wording stable and follow Likert scale question design so trends are real.
"Communication was clear and timely throughout the service."
Why it matters: Late or vague updates create rework, missed access windows, and escalations. Clear communication is also an easy fix compared with process redesign.
When to use: Include when customers rely on status updates (field service, IT/managed services, logistics).
"The work was done correctly the first time."
Why it matters: First-time quality links directly to repeat visits, reopens, and cost. This item points you to training, parts, documentation, or QA gaps.
When to use: Use when you can tie outcomes back to rework or defect categories.
"It was easy to get this service completed."
Why it matters: Effort shows friction that CSAT can hide (multiple handoffs, repeated verification, unclear next steps). Lower effort usually means fewer follow-up contacts.
When to use: Include when customers interact across systems or teams (triage + dispatch + onsite + billing).
"If you contacted us about a problem, it was resolved to your satisfaction."
Why it matters: Issue handling often drives the lowest scores. This item helps you separate "delivery was fine" from "recovery failed."
When to use: Use as a conditional question shown only when a case/escalation exists.
"What should we improve for next time?"
Why it matters: Open text tells you what to fix and gives examples you can share with teams. It also catches issues you did not list (access problems, missing parts, unclear scope).
When to use: Include in every run; keep it optional and follow open-ended question tips to get specific, usable comments.
"How likely are you to recommend us to a colleague or friend?"
Why it matters: This is a relationship signal, not a per-ticket fix list. Use it when you want a stable, longer-term read on loyalty beyond a single interaction.
When to use: Add only if you will trend it at the account/relationship level over time (not as a technician-by-technician scorecard).
Internal starter core (5-8 items): Overall CSAT + timeliness + communication + quality-first-time + effort + (conditional) issue resolution + one open text. Adjust after your baseline and based on which teams can act.
- Add Scheduling if you book appointments: "Scheduling was easy" and "Arrival was within the promised window."
- Add Handoffs if work crosses teams: "I did not have to repeat information" and "Ownership was clear."
- Add Professionalism for onsite delivery: "Staff were professional and respectful" and "The work area was left clean."
- Add Third-party provider if partners deliver: capture "provider name" so you can route fixes.
Wording guardrails: Ask one idea per question, avoid blame (no "Why did you fail..."), and keep scale labels consistent across runs. Use a short set aligned to your customer satisfaction monitoring goals (see ISO 10004 guidance for monitoring customer satisfaction).
Routing fields to include (internal starter set: pick 3-6): service type, channel, region/site, team/provider, urgency/priority, and customer role (end user vs manager). Add/remove fields based on what you can reliably capture and actually route.
Choose Your Main Metric: CSAT vs CES vs NPS (and when to combine them)
| Metric | Best use | Recommended time frame | Best question format | Common misuses (avoid these) |
|---|---|---|---|---|
| CSAT | Transaction quality: "How was this specific service?" | Internal starter target: within 24 hours; keep recall within 7-14 days (shorter is better). Adjust after your baseline. | 1-5 satisfaction scale; a common top-box definition is 4-5 (document and keep consistent) | Changing the scale or wording between runs; using only CSAT with no driver items (you cannot tell what to fix). |
| CES (effort) | Friction and process pain: "How hard was it?" | After the journey ends (completion or resolution) | 1-5 "easy to hard" or agreement with "It was easy..." | Asking effort before the service is complete; mixing effort with satisfaction in a single question. |
| NPS | Relationship loyalty and trend tracking (account-level) | Internal starter target: monthly or quarterly pulse; not tied to one ticket. Adjust after your baseline. | 0-10 recommend question; report %promoters - %detractors | Treating NPS as a per-ticket or per-technician KPI; reacting to week-to-week noise without enough responses (see evidence debates such as longitudinal research on Net Promoter and revenue growth). |
Default: CSAT (1-5) + one effort item + one open-text prompt.
Add NPS only if you will trend it at the relationship level and you already have a close-the-loop process for low transaction scores.
Scoring and Reporting That Leads to Action (drivers, segments, and alerts)
- Pick one scoring rule and lock it
Default: Report top-box % for CSAT plus a consistent summary for your driver items (timeliness/communication/quality/effort).
- If you use a 1-5 CSAT scale, a common top-box definition is 4-5. Document your definition and keep it consistent across periods.
- Use the same scale direction everywhere (higher = better).
- Keep your definitions stable (what counts as "completed," what counts as "resolved").
- Build the dashboard cuts you will actually act on
Default cuts: service type, region/site, team/provider, urgency/priority, and channel.
- Route ownership: region cut goes to the regional service manager; provider cut goes to vendor management; urgency cut goes to dispatch/triage owners.
- Trend weekly or monthly, not daily, unless volume is very high.
- Run a simple driver check before you debate fixes
Default workflow: Compare driver item averages for low CSAT (for example, 1-2) vs high CSAT (for example, 4-5) using your documented scale definitions.
- If timeliness drops hardest among low CSAT, start with dispatch windows, parts availability, or staffing.
- If effort drops hardest, map the journey and remove handoffs, repeats, and unclear instructions.
- Use open-text themes to name the specific break ("missed arrival window," "no status updates," "had to repeat issue").
- Set alert rules for low scores and route them fast
Internal starter targets (adjust after your baseline): CSAT 1-2 triggers an alert to the service manager (or case owner) quickly (for example, within 15 minutes), with a follow-up target (for example, within 24-48 hours).
- Include: customer name (if identified), contact method, service date, case ID, assigned team/provider, and the open-text comment.
- Log a close-the-loop ticket with root cause and corrective action (training, parts, scheduling, communication playbook).
- Apply small-sample guardrails before you rank teams
Internal starter rule: Avoid ranking teams/providers when n < 30 for the period; trend over time or roll up to a higher level. Adjust the minimum based on volume, variability, and the risk of making a wrong call.
- Use sample size guidance before comparing teams to set minimum n and to avoid false "best/worst" lists.
- Show confidence bands or flag low-n cells in internal reporting.
Once your scoring and alert rules are live, review the key drivers each week and assign one fix owner per driver (not a committee).
How to Customize and Keep the Survey Short (without losing signal)
- Keep the core short (internal starter: 5-8 questions): Overall CSAT + timeliness + communication + quality + effort + (conditional) issue resolution + one open text. Adjust after your baseline and based on what you can route.
- Add one module at a time: Add Scheduling or Handoffs only when you have a clear owner who will change that step.
- Match your wording to your SLA language: Use "promised window" or "expected timeframe" (not internal codes) so customers answer the same way you report.
- Use keep/drop/add by service model: Keep timeliness/communication/effort for all; add professionalism for onsite work; add handoffs for shared services; add documentation clarity for professional services.
- Stay strict on length for high volume: Use the short version when you send thousands of invites per month. Longer questionnaires can reduce response rates (see the randomized trial on questionnaire length and reminders).
- Send one clear ask: Put the rating question first, then drivers, then open text. Avoid long intros and multiple competing CTAs.
- Use consistent distribution hygiene: Keep the same channel (email/SMS/in-app) for trending, and use a consistent reminder plan (internal starter target: 1-2 reminders) based on your baseline response behavior.
- Drop questions you will not act on: If you cannot name the owner and the decision ("what changes if this score is low?"), remove the question.
Core (internal starter): 5-8 items for post-completion or post-resolution. Extended (internal starter): 10-15 items only when you need diagnostics by step (scheduling, handoffs, professionalism, third-party). Adjust after your baseline and based on what you will act on.
Frequently Asked Questions
How soon after service delivery should I send the survey?
Send it as close to completion or resolution as you can while details are fresh (internal starter target: within 24 hours, adjusted to your operations and baseline). Keep the recall window short (internal starter: last 7-14 days) and reference the exact job/ticket date in the first question.
What is the best default metric for service delivery: CSAT, CES, or NPS?
Use CSAT as your default transaction metric, then add one effort (CES-style) item and one open-text question so you can diagnose what to fix. Add NPS only if you will trend it at the relationship/account level over time, not as a per-ticket KPI.
How many questions should a service delivery satisfaction survey have?
Use a short core survey for high-volume operations (internal starter: 5-8 items) so you can keep response rates steady and still route fixes. Use an extended version (internal starter: 10-15 items) only when each added item maps to a clear decision (for example, fixing scheduling, handoffs, or professionalism).
Should this survey be anonymous or identified?
Use identified responses when you have a defined follow-up workflow (who calls back, by when, and what gets logged) and you tell customers how you will use their feedback. Use anonymous or confidential responses when candor is the priority, and avoid collecting PII you do not need to act.
How do I analyze results to find what is driving dissatisfaction?
Start with overall CSAT, then compare the driver items (timeliness, communication, quality, effort) for low vs high CSAT groups to see what drops the most using your documented scoring rules. Next, review open-text themes and segment by service type, team/provider, region, urgency, and channel so you can route fixes to the right owner.
What should I do when someone gives a very low score?
Trigger an alert (for example, CSAT 1-2) and route it to the service manager or case owner quickly, with a defined follow-up SLA (internal starter targets are often minutes to alert and 24-48 hours to follow up; adjust after your baseline). Use a short script (apologize, confirm facts, ask what would make it right), log root cause and corrective action, and never argue, pressure for a higher score, or promise what you cannot deliver.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED