Outsourced calling buyer guide
Partial completion rules for outsourced survey calling
Preserve valid answers while distinguishing interruption, refusal, ineligibility, and dropout in survey reporting.
Direct answer
How should an outsourced survey team record a partially completed interview?
Define survey contacts with approved eligibility, consent, instrument version, progress state, callback rules, and final disposition definitions, keep the research owner who decides instrument logic, usable-response rules, and analysis treatment accountable, test the workflow with real examples, and judge the provider on partial interviews classified reproducibly with valid answers preserved and missing data left explicit. Expand only after the records, calls, notes, and handoffs agree.
What to get right first
- Scope survey contacts with approved eligibility, consent, instrument version, progress state, callback rules, and final disposition definitions.
- Require respondent identity boundary, eligibility answers, consent, question path, saved responses, break point, reason, callback permission, instrument version, and final status.
- Keep decisions with research owner who decides instrument logic, usable-response rules, and analysis treatment.
- Measure partial interviews classified reproducibly with valid answers preserved and missing data left explicit.
Control map
Split caller work from owner decisions
Swipe or scroll sideways to see every scorecard column.
| Call lane | Filipino caller | Owner or manager | Useful check |
|---|---|---|---|
| Scope | Reviews only the released queue and current brief. | The research owner who decides instrument logic, usable-response rules, and analysis treatment defines purpose, access, and limits. | Eligible work is identifiable |
| Call | Uses approved language and records attributable facts. | Maintains policy and approved answers. | No unsupported commitment |
| Exception | Pauses and routes the unresolved question. | Makes and records the decision. | One named next owner |
| Close | Reconciles outcome, note, and next action. | Reviews quality and changes the brief. | partial interviews classified reproducibly with valid answers preserved and missing data left explicit |
Example pilot board
Small numbers make the first review easier
Record why the interview stopped
A partial interview can end because of a dropped connection, respondent refusal, scheduled continuation, loss of privacy, language mismatch, eligibility termination, fatigue, or technical failure. These events are not interchangeable. The disposition should describe the stopping event and whether another contact is permitted. It should not decide whether an analyst will later use the answers.
Callers need a short decision tree that follows the approved instrument. If the respondent withdraws consent or refuses further contact, stop and apply the required instruction. If the connection drops, use the preapproved callback rule. Never turn a refusal into a callback simply to improve completion numbers.
Build the evidence for survey calling
The working queue is survey contacts with approved eligibility, consent, instrument version, progress state, callback rules, and final disposition definitions. Before release, inspect respondent identity boundary, eligibility answers, consent, question path, saved responses, break point, reason, callback permission, instrument version, and final status. Put those items in the system the caller will use, with a source and owner for any field that can change the decision. If evidence is missing, route the record instead of asking a live caller to repair the business rule during the conversation. Save the rule version and release time so later review uses the instruction that was actually available.
Apply a firm stop: do not guess missing answers, convert a refusal into a callback, or label every interrupted interview complete because some responses were saved. The research owner who decides instrument logic, usable-response rules, and analysis treatment remains responsible for policy, sensitive changes, commercial commitments, and exceptions. A caller can capture the contact's words and preserve uncertainty without taking over that authority.
Preserve answers without filling gaps
Save only answers the respondent actually supplied through the approved path. Leave unanswered questions missing. Do not infer a response from earlier conversation, copy an answer to a similar item, or select a neutral option so the record can close. The instrument version and last completed question should travel with the partial record.
Branching matters. A skipped question may be correct because an earlier answer made it inapplicable, while another blank may show where the interview ended. Store the path as well as the values. This lets the research owner distinguish legitimate skip logic from dropout without asking the caller to reconstruct the session.
Control continuation as the same interview
When continuation is allowed, confirm the respondent request, safe contact details, preferred window, and point of resumption. Prevent a second caller from opening a fresh interview and duplicating earlier answers. The returning caller should see enough context to resume without exposing unnecessary response content or pressuring the person to continue.
Set an expiry for continuations and define what happens after it. Some studies may retain the partial answers; others may exclude the record under a written analysis rule. That choice belongs to the research owner. The caller role ends with accurate capture of consent, progress, and stopping reason.
Copy-ready words
Scripts your caller can adapt
"I am calling about the specific request in the record. Is now a suitable time to confirm the approved details?"
"I can record that question accurately, but the named owner must make that decision."
"I have recorded the outcome, the next action, who owns it, and when the follow-up is due."
Review flow
Move from one clean list to steady calls
Swipe or scroll sideways to see all five review steps.
- 1
Define
Release survey contacts with approved eligibility, consent, instrument version, progress state, callback rules, and final disposition definitions.
- 2
Test
Work common cases and known exceptions.
- 3
Compare
Check source, call, note, and outcome.
- 4
Repair
Correct the rule or field causing the defect.
- 5
Decide
Expand, narrow, or stop based on evidence.
Test and release the survey calling partial workflow
Use a bounded sample that includes ordinary records and this harder set: Distinguish a dropped connection with callback permission from a respondent ending the interview, an eligibility termination, a language mismatch, and a scheduled continuation. Review the source, call evidence, saved note, disposition, next action, and owner as one chain. The central measure is partial interviews classified reproducibly with valid answers preserved and missing data left explicit, with exceptions and unresolved work shown separately from successful activity.
Watch for using one partial disposition that conceals why the interview ended and whether contact may resume. Protect personal information with named accounts, the smallest practical data view, controlled recordings and exports, and prompt removal of access when the assignment changes. Record corrections by cause and confirm the repaired instruction on a new sample. Expand only after the evidence shows that the caller boundary, system fields, and owner handoff work on the difficult cases as well as the routine ones.
Audit disposition separately from usability
Replay sampled paths against timestamps, saved responses, break reason, callback permission, continuation, and final disposition. Confirm that the status matches the evidence and that unanswered fields remain missing. Include completed interviews so reviewers can see whether callers are using partial codes to avoid difficult closing questions.
Report partials by stopping reason, instrument section, language, time band, and caller only where those comparisons are appropriate and privacy rules allow them. A concentration at one question may reveal wording or tool trouble. Repeated technical drops require a platform fix. The research owner decides analytical treatment after the operational record is trustworthy.
Buyer questions
Outbound calling FAQ
What should the client decide before a provider starts?
The client should approve the queue purpose, permitted records, script, access, dispositions, escalation owners, contact rules, and quality standard. The research owner who decides instrument logic, usable-response rules, and analysis treatment remains accountable for decisions outside that brief.
What is the most useful first metric?
Use partial interviews classified reproducibly with valid answers preserved and missing data left explicit. Report the eligible denominator and show exceptions rather than mixing them into a general activity count.
When should the workflow pause?
Pause when identity, permission, source data, suppression state, system availability, or owner authority is unclear. Also pause when the caller would need to guess missing answers, convert a refusal into a callback, or label every interrupted interview complete because some responses were saved.
Numbered sources
These primary pages support the dated figures, exact quote, calling rules, and Philippines context used in this guide. A qualified adviser should apply the rules to your list, call type, and contact locations.