Phone-Field Coverage: Check a Sales Call List Before Dialing

By Trellus Team · October 23, 2026

Before handing a call list to a rep, check whether its phone data is actually available in the workflow they will use. A contact can have a number somewhere in the CRM and still arrive in the selected view with no phone field the rep can use.

Start with the selected records, not the total number of populated cells. One contact with three numbers does not cover three contacts. An empty export column does not prove the underlying record has no number. And a neatly formatted value does not prove that the intended person will answer it.

This guide uses phone-field coverage as a documented team reporting convention, not a standardized KPI. The twelve-record example below shows how to check the list, explain the gaps and hand off repairs without turning a data check into permission to call.

Ask two questions before calculating coverage

The first is about presence: does a selected contact record contain a nonblank value in at least one of the phone fields included in your audit? Write down those fields. A number in an unexamined custom field is not evidence either way until you inspect it.

The second is about a narrower, practical field check: does at least one of those values meet your documented format rule and appear in the actual selected calling workflow? Keep this label beside the result. Don't shorten it to “verified contacts” or “callable people.”

For example, a reviewer might check that the value can be interpreted under the workflow's documented country and extension handling, then confirm that the same value is available to the rep in the selected view. If that handling is unknown, mark the format assessment unresolved. Don't guess a country, strip an extension or rewrite every number into one universal format to make the report pass.

These checks stop short of several other questions: whether a line is assigned or active, who owns it, whether the contact is the intended person, and whether outreach is permitted now. A record can pass the field check while any of those questions remains unresolved.

Save the list and the counting rule

Save the list name, membership, selection time and time zone before reviewing it. Use a stable contact-record ID to count each selected record once. If the same ID appears twice in an export, remove the repeated row from the calculation, not from the CRM.

Different IDs may still describe the same person. Keep those suspected duplicates visible for review; a stable record count is not proof of a unique-person count. Conversely, two legitimate contacts may share a company switchboard. Matching phone values alone are not grounds to merge or delete their records.

Write the scope precisely: “These twelve selected CRM contact records, checked in this view at this time.” That is more useful than “our database is 83% complete” when you have examined only one list.

Keep contact restrictions and other exclusions beside the audit. The example below retains every selected record in the phone-data denominator, including a restricted one. If you also report a separately defined eligible subset, show its membership rule and count alongside the original list. Never remove restricted or incomplete records silently to raise the percentage.

A twelve-record audit you can check by hand

This is a fictional worksheet, not customer data or a target. An export contains thirteen rows, but two have the same ID, R03. After counting that repeated ID once, there are twelve distinct selected records.

The audit includes the selected primary, mobile and named custom phone fields. “Pass” below means that at least one value meets the example's documented format rule and is available in the actual selected calling view. It does not mean the record is cleared for outreach.

R04 and R05 are two selected records, not two verified direct lines. R03 is one selected record, not two because it has multiple phone fields or appears twice in the export. R11 remains unknown: it is not counted as a blank record just because the export omitted information.

Show the counts behind both percentages

For this example, known populated-field coverage = distinct selected records with at least one observed nonblank audited phone field ÷ all distinct selected records × 100.

Ten records have a known nonblank value: R01–R05, R07–R10 and R12. Known populated-field coverage is 10 ÷ 12 = 83.3%, rounded to one decimal place. Beside it, show one known blank record and one unknown record. The result reports observed presence, not complete knowledge of every record.

Now apply both the format and availability checks. Seven records pass: R01–R05, R09 and R12. Documented field-check coverage = 7 ÷ 12 = 58.3%. Four have an identified gap or unresolved assessment; one has unknown source-field status.

The difference matters. If the handoff says only “ten records have phone data,” the rep inherits R07's note, R08's unavailable field and R10's unresolved interpretation. If it says “seven contacts are callable,” it overstates what the audit established, especially for R09 and R12.

Use one primary field-check result per record so these groups add back to twelve. Keep other concerns as separate flags. R09's association question and R12's restriction do not become extra records in the field-status breakdown. Nor does passing this narrow check clear either concern.

If the selected list is empty, report “not applicable: zero selected records,” not 0% coverage. If some records remain unknown, keep their count visible rather than silently dropping them from the denominator or marking them passed.

Turn the gaps into a small repair queue

Give each issue to someone who can resolve that particular question. “Clean the list” is hard to finish; “inspect the missing phone fields on R11 and return the observed status” has a clear endpoint.

• Missing value, R06: the data owner checks an approved source and records what was actually found. No number found is a valid outcome; do not fabricate a value to fill the cell.
• Format issue, R07 and R10: a reviewer checks the original value and the applicable workflow rules. Preserve an unresolved interpretation if there isn't enough evidence to correct it.
• Availability gap, R08: the workflow owner investigates why the known source value is absent from this selected view. A source-field change alone does not prove that an old export or saved worklist has changed.
• Unknown source status, R11: someone with appropriate access inspects the omitted fields. Lack of access is not proof that the data is missing.

Handle R09's association question separately. A plausible format cannot settle who a number belongs to. When an actual wrong-person or wrong-number observation disputes an association, use the wrong-number record-repair guide. Don't treat an unanswered call as that evidence, and don't place test sales calls just to make this worksheet look complete.

Keep R12's restriction in force. Phone data and outreach eligibility answer different questions; completing one does not override the other. This worksheet is not a consent, suppression or legal-clearance process.

Recheck the same records in the actual worklist

Suppose an approved review supplies R06 with a value that meets the agreed rule, and R08's value becomes available in the selected workflow. The reviewer reopens the actual worklist and confirms both changes. R07, R10 and R11 remain as before.

On the original twelve-record list, field-check coverage is now 9 ÷ 12 = 75%. Known populated-field coverage is 11 ÷ 12 = 91.7%, with one presence status still unknown. These are fictional before-and-after checks, not an improvement claim about Trellus or a forecast of answered calls.

If R06 and R08 were merely deleted, 7 ÷ 10 would be 70%, but that would describe a smaller population, not two repaired records. Report removals and reasons explicitly. Save the original audit and the recheck so the difference can be explained without reconstructing a changing list.

A repair is complete for this worksheet only when the necessary evidence is visible where the rep will work. A successful edit in a source record is an intermediate step. An imported copy, stale export or different selected phone field can still leave the original problem in place.

Copy this pre-block review card

List name, saved membership time and time zone: ____
Selected export rows / distinct contact-record IDs / repeated-ID rows: ____
Suspected duplicate-person records still unresolved: ____
Audited phone fields and actual calling view: ____
Documented format and field-availability checks: ____
Known populated / known blank / unknown-presence records: ____
Field-check pass / identified gap or unresolved assessment / unknown-status records: ____
Separate association, shared-line and restriction flags: ____
Original denominator and any separately reported eligible-subset rule: ____
Repair per record, responsible owner and next review time: ____
Reopened worklist evidence and remaining unknowns: ____

Keep this handoff short enough to act on: “Twelve selected records; seven pass the documented field check, four need specific review and one lacks source-field evidence. R09's association question and R12's restriction remain separate. No calling clearance is implied.” Share record references through your approved internal process, not a public worksheet containing personal phone data.

Measure what happens after the list is handed over

Once work begins, list penetration asks which selected records actually received an attempt. Contact rate asks about observed conversations under a stated outcome definition. Neither can be inferred from phone-field coverage.

If a block stalls despite the checked fields being available, inspect the actual stopping point rather than repeating the data audit. The stalled call-block guide separates an empty queue, research, conversation, wrap-up and failure. The useful result here is narrower: a list whose known data gaps have names, owners and a visible next step.