Does agent matching need consumers’ personal details?
No. The data is pseudonymised only. BestPair never asks for consumer names, Social Security numbers, phone numbers, email or street addresses, or bank or card details. It works from account IDs, account details such as balance, days delinquent, placement date, consumer age band, state and ZIP code, and call and payment history keyed to each collector. Account IDs are your own, so BestPair cannot tell who a consumer is. The matching is calculated off-site by BestPair, on AWS in the United States.
New to BestPair? See what it is and how it works
What BestPair receives
Agent matching (BestPair calls it predictive pairing) learns which collector does best with which kind of account. That takes four things, all keyed to your own IDs:
- Account IDs and account details. Balance, days delinquent, placement date, consumer age band, state and ZIP code. A date of birth is never needed.
- Call history. Which collector called which account, when, and how the call ended.
- Payment history. Which accounts paid, when, and how much.
- Data about your own collectors. Each collector’s agent ID, start date and results. This is data about your staff, and BestPair processes it too.
Personal data is pseudonymised only. BestPair never asks for consumer names, Social Security numbers, phone numbers, email or street addresses, or bank or card details. Account IDs are your own, so BestPair cannot tell who a consumer is. Call recordings and notes stay with you too. If a file arrives with anything extra, BestPair deletes it and asks for a resend. The full file list.
Where the matching runs
Off-site. BestPair calculates the matching on its own side, on AWS in the United States, and it does not run inside your environment. Storage and access are different questions. The data is stored and processed only in the United States. The founder and R&D team are in Australia and may access it remotely from company-managed devices.
Your floor sends its files by encrypted SFTP to a folder BestPair provides, never by email. The assignments come back keyed to your account IDs and collector IDs, and your dialer applies them through its routing.
Some agencies ask for a version installed on their own servers. BestPair does not offer one. The matching and its model updates run on BestPair’s side, so your IT team has no vendor software to install, patch or monitor inside your network.
What the agency keeps
- The link between an account ID and a consumer. Only your systems can turn an ID back into a person. If you mask the IDs before sending them, even the ID BestPair sees is one only you can reverse.
- Every contact with consumers. People make every call. BestPair never dials, calls, texts or contacts anyone.
- Offers, scripts and compliance rules. What collectors say, what they offer and your FDCPA, Regulation F and TCPA controls stay exactly as they are. BestPair changes only which collector works which account.
- Your systems of record. Recordings, notes, payment processing and client reporting stay in the systems you already run.
Before any file moves
Expect your legal or compliance team to want sign-off before even a sample file is shared. That is reasonable, and it goes faster when they can see the field list first. No separate NDA is needed to start: the Order Form and the Data Processing Addendum cover confidentiality. Send your team the file list and this page, and ask BestPair for the Security Overview and the Data Processing Addendum, both available on request. What a security review asks. The account details themselves are covered in more depth in which account details help predict payment.
Common follow-up questions
Can we mask or hash our account IDs before sending them?
Yes. Use your own logic, and keep it the same across files and across months so calls, payments and account details still join up. Assignments come back on the masked ID, and only your systems can turn it back into an account.
Can BestPair run inside our own environment instead?
No. The matching is calculated off-site by BestPair and does not run on your servers or inside your dialer. The files are pseudonymised, and account IDs are your own, so BestPair cannot tell who a consumer is.
If the files carry no consumer names or contact details, do they still need protecting?
Yes. Account and payment history is confidential business information for you and your clients. No separate NDA is needed to start: the Order Form and the Data Processing Addendum cover confidentiality. Files travel encrypted (TLS 1.2 or higher and SFTP) and are encrypted at rest, and BestPair holds SOC 2 Type 1.
What it could mean on your floor
Two minutes
Watch the explainer
What your dialer does with the next account, what pairing changes, and what the Floor Assessment measures. With captions.
Watch the videoYour floor
Try the calculator
Four numbers off your dialer and collections reports give an illustrative figure for your floor. It is at best informed guesswork until your own history is measured.
Open the calculatorA live test
Read the case study
170,000 telecom accounts split at random before the first call, and how the result was counted.
Read it
Would it be a bad idea to spend 45 minutes finding out?
If your shop does not qualify, you will hear it on the call, not after you have paid for a report.
Book a 45-minute fit call