Before your campaign starts, give this guide to anyone who will work your file: callers, VAs, vendors, CRM admins, list managers, and marketing teams.
SkipMatrix files are built for coverage, not a single-number lookup.
In this guide, subject means the main prospect or record returned for the row.
Each result row keeps your original input columns and adds 340 enrichment columns: 2 system columns, 43 subject columns, 150 relative columns, and 145 associate columns.
Depending on what is available for the record, one row can include up to 121 points of contact across the subject, relatives, and associates.
If You Read Nothing Else
SUBJECT: Phone 1is where to start, not where to stop. Work every available subject phone before marking a record unreachable.Subject phones may reach the subject directly or a likely household member who can help you reach the subject.
Only mark a number a confirmed wrong number if it is not the subject, not a household member, and not someone who can help reach the subject.
Use the returned SkipMatrix name tied to each contact field, not your original input name.
Track every outcome by the phone field that produced it.
If subject phones do not connect, work relative and associate contacts as deeper fallback paths.
The sections below explain how to do each of these and which fields to watch. Anyone touching the file should still read the full guide once.
The Main Rule
Important: The SUBJECT: Phone 1 is the starting point, not the end. If your team only works SUBJECT: Phone 1, they are leaving most of the file unused. Work every available subject phone before marking a record unreachable.
Work the subject phones in order:
SUBJECT: Phone 1SUBJECT: Phone 2SUBJECT: Phone 3SUBJECT: Phone 4SUBJECT: Phone 5
Some teams work them one pass at a time. Others use a dialer setup that can attempt multiple subject phone fields efficiently. Either can work if your team can still track which phone field produced each outcome.
How SkipMatrix Subject Phones Work
The subject phone columns are not meant to be a raw list of every old number ever connected to a person.
SkipMatrix uses the subject phone columns as the best available paths to reach the subject now.
That can include high-confidence phone numbers for the subject directly. It can also include high-confidence phone numbers for a likely household member when that is one of the strongest available ways to reach the subject.
That is why SUBJECT: Phone 2, SUBJECT: Phone 3, SUBJECT: Phone 4, and SUBJECT: Phone 5 still matter.
A subject phone may reach the subject directly. It may also reach a spouse, parent, child, sibling, significant other, or another household member who can help you reach the subject.
Phone numbers can go stale, be reassigned, or disconnected. SkipMatrix prioritizes the strongest current contact paths, but the only way to confirm a number in the field is to work it.
Important: Do not assume every subject phone belongs directly to the subject. Lower-ranked subject phone fields may still be strong contact paths, especially when they point to a household member.
What the File Contains
Your output file includes your original uploaded columns first. SkipMatrix prefixes those columns with INPUT: so your team can still see the data you submitted.
After the input columns, every row includes the same 340 enrichment columns:
Section | What it includes |
System |
|
Subject | Main prospect demographics, addresses, phones, emails, and address metadata |
Relatives | Up to 5 relatives, each with name, relationship type when available, age, deceased flag, mailing address, up to 5 phones, and up to 5 emails |
Associates | Up to 5 associates, each with name, age, deceased flag, mailing address, up to 5 phones, and up to 5 emails |
Blank cells are normal. They mean that field was not available for that row. Do not treat blank cells as a file error.
Files Included With Your Results
Each completed SkipMatrix order includes four CSV files:
File | What it contains | How to use it |
All Available Data | The complete result file with your original input columns and all SkipMatrix enrichment fields | Use this as the source of truth when reviewing results, measuring coverage, or comparing vendors |
Mobiles | A filtered version for mobile-focused workflows, with landline phone numbers removed | Use this for mobile-focused calling or texting workflows |
Landlines | A filtered version for landline workflows, with non-landline phone numbers removed | Use this for voice-only calling workflows |
Missed Hits | Records that did not return a SkipMatrix match | Use this to see which records need corrected input or a different review path |
Start with All Available Data when you need the complete picture. Use Mobiles and Landlines when you need filtered files for a specific campaign workflow.
Use the Returned Name
Use the name returned with the contact data you are working.
For subject contact data, use SUBJECT: First Name and SUBJECT: Last Name.
For relative contact data, use the matching RELATIVE N: First Name and RELATIVE N: Last Name.
For associate contact data, use the matching ASSOCIATE N: First Name and ASSOCIATE N: Last Name.
Important: Use the returned SkipMatrix name tied to the contact field. Do not default to the first and last name from your original input columns when working SkipMatrix-provided contact data.
How to Work the File
1. Keep performance measurable by phone field
The goal is not always separate campaigns. The goal is clean attribution by phone column.
If your dialer or CRM can track outcomes by phone field without splitting the file, that works. If it cannot, build separate campaign lists by phone field.
At minimum, make sure you can report performance for:
SUBJECT: Phone 1SUBJECT: Phone 2SUBJECT: Phone 3SUBJECT: Phone 4SUBJECT: Phone 5Relative phone fields
Associate phone fields
This lets you see how each phone column is performing and optimize future campaigns. If every phone is mixed together with no source field, you cannot tell what is producing connects, replies, confirmed wrong numbers, appointments, or do-not-contact requests.
Important: Every outcome should tie back to the phone field used. A raw phone number with an outcome is not enough for clean campaign analysis.
2. Work every subject phone first
Do not stop after the first pass through SUBJECT: Phone 1.
Subject phone fields are the best available contact paths for the subject. In many rows, lower-ranked subject phones may be another strong way to reach the subject, a household member, or someone who can help you reach the subject.
Your team should work through all available subject phone numbers before marking the record as unreachable.
3. Use relatives and associates as deeper fallback paths
Relative and associate fields exist so your team has more paths when the subject phones do not connect.
Relatives are usually closer family connections. They may include a spouse, parent, child, sibling, or another close family member.
When available, RELATIVE N: Relationship Type gives extra context for the relative connection. It may say spouse, parent, child, sibling, grandparent, grandchild, unknown, or another relationship label.
Associates are broader connections. They may include a significant other, coworker, neighbor, former neighbor, distant relative, or another person connected to the subject through shared records.
The best household contact paths may already be included in the subject phone columns. Still, the relative and associate sections can give your team more coverage when the subject phone fields are exhausted.
A relative or associate whose mailing address matches the subject's mailing address is often one of the strongest fallback paths.
Use these fields as additional paths to reach the subject or gather better information, not as a replacement for working the subject phones first.
4. Track outcomes correctly
When a caller, vendor, or marketing team reports performance, make sure they can tell you which phone field produced each outcome.
Your team should also keep enough record identifiers to map each outcome back to the correct file and original row in All Available Data. This makes it easier to review the full record later if you need more context.
At minimum, keep these identifiers with every outcome:
Original file name
Original record ID or source identifier, if your input file includes one
Returned subject first and last name
Relevant mailing or property address from the row
Phone field used
Phone number worked
Returned contact name used, whether subject, relative, or associate
And track these outcomes:
Connects
Reached subject
Reached household member or other helpful contact
Confirmed wrong number
Do-not-contact requests
Appointments or qualified conversations
Important: Reaching a household member is not the same as a wrong number. Mark a number as a confirmed wrong number only when the caller can confirm it does not belong to the subject, a household member, or someone who can help reach the subject.
5. Control call conditions
Contact rate is not only a data-quality metric.
It is also affected by call timing, caller ID reputation, spam flags, dialing volume, dialing cadence, voicemail strategy, script quality, offer quality, and whether your team is managing outbound numbers properly.
If contact rate is low, review the data and the campaign setup together. A strong file can still underperform when the calling setup is weak.
6. Evaluate the record, not only one data point
SkipMatrix gives you multiple contact paths so your team does not hit dead ends as quickly.
If one contact point gets you to the prospect, that record did its job.
Not every data point will be perfect. The goal is maximum usable coverage: enough paths to give your team a real chance to reach the prospect.
Judge the file by whether it gave your team real paths to reach the prospect. Interest level, sales outcome, and conversation quality depend on the prospect, the offer, the caller, and the campaign.
How to Compare Results
When comparing SkipMatrix with another provider, compare the full file, not only the records where both providers returned phone numbers.
Coverage matters. If another provider returns phone data for only part of your list, the records with no result are still part of the comparison. Those records would have been dead ends without another source of contact data.
Also compare the full record, not only the first phone number. Some providers may return one or two numbers. SkipMatrix may return multiple subject, relative, and associate contact paths. If one of those contact points helps your team reach the prospect, that is part of the value.
For a clean comparison, track:
How many records did each provider return results for?
How many records each provider left without usable contact data
Whether the same campaign setup, call timing, caller ID conditions, and outreach process were used
Which contact point or phone field helped your team connect, when available
A provider cannot produce a call outcome for a record where it returned no data. Measure performance across the full file so you can see both coverage and whether the available contact paths helped your team reach the prospect.
A common pitfall: comparing only the records where both providers returned a phone number. Suppose you run a 100-record test. Provider A returns phone data for 40 records; SkipMatrix returns phone data for 95. If you compare call outcomes only on the 40 overlapping records, the two providers may look similar, but 55 records became reachable only through SkipMatrix and are missing from the comparison entirely. The same skew happens if you evaluate only the first phone number instead of the full set of contact paths returned.
Key Fields to Understand
Search Result
Shows the match status for the row.
Values include:
Unique Hit: the row got a hit and returned results.Missed Hit: the row did not return results.Duplicate Hit: the returned person is the same person already returned on a prior unique hit.
Use this field to separate rows that returned results from rows that need a different review path.
Input Method
Shows which input path produced the match.
Name-based input methods are usually more precise because the search used both a name and an address or ZIP.
For Owner Search orders, the main name-based methods are:
Name + Mailing AddressName + Mailing Street + Mailing ZIPName + Property AddressName + Property Street + Property ZIP
These methods are usually cleaner because they include the submitted person name.
Mailing Address by itself is different. It is a fallback path that can return the current person associated with the mailing address. This is useful when the submitted name is an entity, trust, LLC, incomplete name, or otherwise not enough to match directly.
The tradeoff is that the mailing address has to be accurate and current. If the mailing address is outdated, the returned person may be the current person associated with that mailing address rather than the person your team expected.
Segment Mailing Address fallback rows when you need cleaner reporting.
Other search types show different Input Method values. The same principle applies: methods that include the submitted name are usually more precise.
SUBJECT: Deceased Flag
Shows whether the subject is reported deceased.
If this value is Yes, route the row to a separate workflow instead of assigning it as a normal subject record. Some teams review relatives or associates on these rows instead of working the subject directly.
If this value is No, it means SkipMatrix did not return a deceased signal for that subject. It does not guarantee that the person is living.
Phone fields
Each available subject, relative, or associate phone can include:
Phone number
Phone type
Last seen date
Phone type values include:
LandlineWirelessVoip
Use phone type to route the record if your tools or campaign setup separates phone categories.
Relative phone columns follow the pattern RELATIVE N: Phone 1 through RELATIVE N: Phone 5. Associate phone columns follow the pattern ASSOCIATE N: Phone 1 through ASSOCIATE N: Phone 5.
Last seen dates
Phone last-seen dates show when that phone was most recently observed.
More recent dates are better starting points, but older numbers can still be useful in later passes.
SUBJECT: Mailing: Vacant Flag
Shows whether USPS reports the subject mailing address as vacant.
Use this as an address-quality signal. Do not discard the whole record automatically; review the other available contact fields.
SUBJECT: Property: Vacant Flag
Shows whether USPS reports the subject property address as vacant.
Use this when the property address matters to your workflow.
Caller and Vendor Handoff
Give your team these instructions before launch:
Work every available subject phone before marking the record unreachable.
Do not only work Phone 1.
Subject phones may reach the subject directly or a likely household contact who can help us reach the subject.
Use the returned SkipMatrix name tied to the contact field, not the original input name.
Track outcomes by phone field used. Do not report only raw phone numbers with outcomes.
Do not mark a phone as a confirmed wrong number unless it is not the subject, not a household member, and not someone who can help reach the subject.
If subject phones do not connect, use relative and associate contact data as deeper fallback paths.
Keep call conditions clean: caller ID reputation, dialing cadence, timing, script, and outbound number management all affect contact rate.
Responsibility
SkipMatrix provides data for sales and marketing workflows. You are responsible for how you use it and for following the rules that apply to your outreach, including suppression lists, do-not-contact handling, consent requirements, platform policies, and channel-specific rules where they apply. This guide is practical guidance for working your file. It is not legal advice.
