Philippines staffing blog
Keep a Source Ledger for Every Calling List
A list without provenance is a compliance and quality risk. Record the source, permission basis, age, and owner before any dial.
Direct answer
What outbound call center outsourcing means
A calling list should carry a source ledger that names where each record came from, when permission was obtained, what the person agreed to, and who owns the list. The caller can work the approved list and flag gaps, but the list owner decides whether a record is eligible.
What to get right first
- Record the source, collection date, permission basis, and list owner for every imported record.
- Reject a list that cannot explain how the number was obtained and what the person agreed to receive.
- Separate list eligibility from dialer availability so a technical fix cannot bypass a missing permission.
- Review a sample of records against the source before the campaign opens.
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 |
|---|---|---|---|
| New import | Checks the file identifier and flags missing source fields. | Approves the source and the permission basis. | Every imported record has a source and an owner. |
| Eligibility check | Compares the record with the approved campaign scope. | Resolves ambiguous or conflicting permission. | Excluded records do not reach the dialer. |
| Dialer load | Confirms the eligibility status travels with the record. | Owns the import and the reconciliation. | Loaded count matches the approved count. |
| Source review | Samples records against the original source. | Pauses or repairs the source. | Defects have a named owner and date. |
Example pilot board
Small numbers make the first review easier
Define the ledger fields
A useful ledger has a stable record identifier, the source name, the date and channel of collection, the permission basis, the scope of consent, the suppression status, the list owner, and the last verification date. It also carries the import file hash and the person who approved the import. These fields let a reviewer answer why this number is eligible without interviewing the person who built the list.
Do not use a free-text note as the only evidence. A field that says referred by partner is not a permission basis. Link the record to the actual source, such as a web form submission, a contract, or a documented inbound request. If the source cannot be produced, mark the record as ineligible until the owner resolves it.
Check the permission scope
The permission must match the campaign. A person who asked for a product demo has not agreed to a debt-collection call or an unrelated upsell. Record the campaign or purpose that the permission covers. If the list is reused for a new purpose, the owner must confirm that the original permission extends to it or obtain a new one.
Check the jurisdiction and the channel. A permission for email is not a permission for automated calls. A request for a callback at a specific time is not a general marketing consent. When the scope is ambiguous, the safe action is to exclude the record and route the question to the list owner. The caller should not decide legal scope on a live call.
Test the ledger against the dialer
Before the campaign opens, compare the ledger with the records loaded into the dialer. Confirm that the same identifier is used and that the eligibility status travels with the record. Check for records that were added manually, imported twice, or changed after approval. A dialer that is technically ready can still call an ineligible person if the status field is missing.
Run a small test batch with known eligible and known ineligible records. Verify that the ineligible records do not appear in the calling queue. Check the suppression list separately. If a record is removed from the ledger but remains in the dialer, the control has failed. Document the test and the correction.
Review provenance before expansion
Sample the list each month and trace a handful of records back to the source. Look for missing dates, copied consent language, and records that were purchased from a broker without a clear chain. A high volume of records is not evidence of quality. A smaller list with a defensible source is easier to operate and safer to defend.
When a source fails the review, pause that source rather than the whole campaign if the other lists are sound. Record the reason, the affected records, the owner, and the date of the fix. Recheck the source before it is used again. The ledger is a living control, not a one-time import document.
Copy-ready words
Scripts your caller can adapt
"I have the number on the list, but I cannot see how it was added or what the person agreed to receive. I am taking it out of today's queue and sending it to the list owner for review."
"The record shows a request for a product demo, not a general marketing call. I am not treating that as permission for this campaign. The list owner will confirm the scope before we call."
Review flow
Move from one clean list to steady calls
Swipe or scroll sideways to see all five review steps.
- 1
Receive the list
Log the file, source, owner, and import time.
- 2
Check the fields
Reject records without a source or permission basis.
- 3
Load and reconcile
Compare approved records with the dialer queue.
- 4
Sample and review
Trace records to source and repair the defective list.
When a source changes
A source can change its form, its consent language, or its owner. When that happens, the old records do not automatically inherit the new permission. Version the source and record the effective date. If the new form is narrower, recheck the records collected under the old form before the next campaign. A bulk update that applies the new basis to old records can create a permission the person never gave.
Treat a source change like a mini migration. Map the old field to the new one, identify records that cannot be mapped, and decide whether they are excluded or reviewed by the owner. Keep the old export for the retention period. The point is not to preserve every record. It is to know which records are still eligible and why.
Who approves an exception
An exception should be narrow, documented, and time-bound. The list owner may approve a record with a missing date if the original source can be reconstructed and the campaign is otherwise eligible. The approval should state the record, the missing field, the evidence used, the approver, and the expiry. A blanket exception for a whole list is not a control.
Review exceptions monthly. A pattern of missing dates from one source is a source problem, not a reason to keep approving individual records. Fix the intake or stop using the source. The exception log should shrink over time; if it grows, the approval process is becoming a workaround.
Buyer questions
Outbound calling FAQ
Can a purchased list be used?
Only if the company can show a lawful basis and the scope covers the campaign. A broker's assurance is not enough. The list owner decides.
What if a record has a phone number but no date?
Treat it as incomplete. Exclude it until the source and date are recovered or the owner approves a documented exception.
Who owns the ledger?
The business owner of the campaign or the data source, not the caller. The caller maintains accurate notes and flags gaps.
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.