Send one short survey when a 311 request closes, ask the resident whether it was actually resolved, save the answer on the case, and route every "no" back to the department that owns the work. A closed case tells you staff finished a task. Only the resident can tell you the problem went away. This guide shows how to set up that loop inside the Salesforce org your city or county already runs, step by step.
Why "closed" is not the same as "resolved"
Most 311 reporting counts what the city did: requests received, requests closed, days to close. Those numbers matter, but they all come from the city's side of the counter. A pothole ticket can close because a crew visited, while the resident still drives over the same hole. A missed-pickup request can close on the day the truck came back, even if it missed the house a second time.
Asking the resident one question at the moment of closure fills that gap. It turns a count of finished tasks into a measure of outcomes, by service type, department and district. It also catches the requests that need a second visit while there is still time to fix them.
Step 1. Pick the moment and the trigger
If your 311 requests are Salesforce cases, the trigger already exists: the case moves into a closed status. List every status that means "closed" in your org, then choose which ones should send a survey. A request closed as a duplicate, or transferred to another agency, is not a moment to ask the resident about service.
Fire the survey only when the case changes into a closed status, not every time a closed case is edited. Crews and supervisors often update closed cases with notes or photos. Test this in a sandbox: close a case, edit it, and confirm only one survey went out.
Step 2. Decide who gets the survey
Send it to the resident who made the request, and only when you have a way to reach them. Many 311 requests are anonymous or come in with no contact details. Skip those, and don't treat their absence as a problem with the data. Your answers will come from residents who chose to share contact details, so report that clearly when you share results.
Add a cadence rule. Some residents report many issues, and they should not get a survey for every one. A limit of one survey per person in a set number of days protects your response rate and your residents' patience.
Step 3. Ask two questions, in plain language
Keep it to one rating question and one open question. For 311, the clearest rating question is about the outcome:
| Request type | Rating question | Measure |
|---|---|---|
| Street and sanitation (potholes, streetlights, missed pickup) | "Was your request resolved?" (Yes / Partly / No) | Resolution, reported as a share of yes answers |
| Code and noise complaints | "How satisfied are you with how we handled your report?" | CSAT |
| Online request or service portal | "How easy was it to make your request?" | CES |
Follow the rating with "What's the main reason for your answer?" Use short sentences, everyday words and a mobile-friendly layout. Offer the survey in the languages your 311 center already serves.
Step 4. Save the answer on the case
The answer belongs on the same case record as the request. That way the department supervisor sees it next to the work order, and you can report on it with the service type, department and district fields you already keep. If responses live in a separate survey tool, someone has to export and match them later, and usually nobody does.
Map three things to fields you can filter and group on: the rating, the open comment, and the date of the answer. Those three fields are enough to build every view in the dashboard below.
Step 5. Route every "no" to an owner
A "No" or a low score should create a follow-up case for the department that owns the service, with a due date. Agree the rules before go-live:
- Who owns it. Usually the supervisor for that service type and district, not the 311 agent who took the call.
- How fast. A common target is contact within one or two business days.
- What "done" means. The resident was contacted, the work was redone or the reason was explained, and the outcome is recorded on the case.
- When to reopen. If the original problem is still there, reopen or relink the original request so your days-to-close numbers stay honest.
Step 6. Give leaders one view
Department heads and the city manager's office need the same few numbers every week: the share of residents who say their request was resolved, the share of unresolved requests followed up on time, and the open follow-up cases by district. The follow-up rate is fully in your team's control, so it often moves before the resolution rate does.
Start with a 30-day pilot
- Week 1. Pick one or two high-volume service types, such as streetlights and missed pickup. Build the survey and routing in a sandbox.
- Week 2. Test with staff as residents. Check one survey per request, the answer on the case, and a follow-up case for every "No."
- Weeks 3 and 4. Go live for the pilot service types. Review answers and open follow-ups with supervisors each week.
- After 30 days. Share the results, fix what the comments point to, and add the next service types.
Practical notes for public sector teams
- Records and retention. Survey answers saved on a case may become part of the public record. Ask your records officer how long to keep them and how to handle open-text comments.
- Privacy. Only survey residents who gave contact details, and only about the request they made.
- Accessibility. Keep surveys short, readable on a phone and usable with a screen reader.
Doing it with NPS Survey CX OS
NPS Survey CX OS by SalesHub runs CSAT, CES and NPS surveys inside the Salesforce org your agency already uses. A record change such as a case closing sends the survey, the answer is saved on the case, and a low score routes to an owner. Surveys can go out by branded email, by QR code at a counter, or on your Experience Cloud site, and your data never leaves Salesforce. The public sector page has blueprints for 311, permits, benefits and field offices, and the Learning Center has the full setup guide.
State, local and education buyers can buy through Carahsoft on the CoreTrust cooperative contract (24COR-018GR). Federal and defense buyers can request a quote through Carahsoft. No government endorsement is implied.
Sources: NPS Survey CX OS public sector blueprints; SalesHub contracts at Carahsoft; How to send a CSAT survey when a Salesforce case closes. Dashboard figures are sample data.
Measure service where it happens
NPS Survey CX OS runs inside the Salesforce org your agency already uses. Buy through Carahsoft or start on AppExchange.
Public sector solutions →Start the free trial →