Phone numbers,
whether you may call them,
and which vendor sold them twice.
You get a link. Connect the providers you already pay for, on your own credentials, and run your own accounts inside your workspace. Located contacts come back — phone, address, employment — with a documented determination on every one. Nothing you run is resold or syndicated, and no consumer data crosses into another customer’s workspace.
And the one thing no data vendor will ever tell you: which of them is selling you a file you already bought. Gallus names it — counted, per provider, against your own accounts.
Flat monthly price. Unlimited accounts. Month to month, cancel any time.
What You Get
One run. Three answers.
You run your own file in your own workspace, against the providers you already pay for, on your own credentials. Three things come back, and you can act on any of them independently of the others.
Where they are
Phone numbers, addresses, and employment, located across every provider you connect. Every contact arrives carrying the sources that produced it, so you can see whether one provider found it or four did — and whether you may act on it at all.
Who uses it: the operating floor, on the accounts they are already working.
Whether you may act
One outcome per account — Proceed, Review, Block, No Result, or Run Failure — with the reason, the evidence behind it, and the next allowed step. Attorney representation, deceased status, and restricted paths stop an account before anyone dials it.
Who uses it: compliance, and whoever answers for a wrong-party call.
Where the answer came from
Every contact arrives with its sources attached, and CAS-1 establishes whether those sources are independent before their agreement counts for anything. Evidence tracing back to a single upstream file is reported as one source rather than several — so you see the weight behind an answer, not a tally of how often it repeated.
Who uses it: whoever answers for the quality of the file.
Why the third one changes the first two. A number four sources agree on looks safer than a number only one returned. If those four trace back to a common origin, the agreement is not corroboration — it is the same claim arriving four times, and the count is what makes it convincing. Independence is what separates a contact your collectors can work from one that merely looks well supported.
Before You Ask
The reasons people say no.
"We already pay for skip trace."
You keep them. Gallus runs on your credentials, through your existing contracts. It does not replace your providers — it tells you which of them are worth keeping. Most agencies find they can cancel at least one.
"We would have to switch something."
No. You upload in your workspace and export from it. Nothing is ripped out, no dialer integration is required, and your collectors do not have to learn anything on day one.
"What if it does not work on our data?"
Then you cancel after a month. There is no contract and no minimum term. Your exposure is one month, and you will know inside the first week whether the report tells you anything you did not already know.
"Our compliance team will have questions."
Send them the compliance architecture page before the first call, along with your vendor security questionnaire. We would rather answer it early than discover in week six that we are the reason a deal is stalled.
"Will this slow the floor down?"
It should speed it up. Your collectors currently burn dial attempts on numbers that were never right. Gallus marks those before anyone picks up the phone, and unlimited pricing means nobody has to ration which accounts get checked.
"You are a small company."
We are, and we say so in writing rather than waiting to be asked — including in the security overview we hand to your reviewers. Month-to-month terms exist precisely so that our size is your decision to make, not a risk you are locked into.
Why They Sign
The reasons people say yes.
One outcome per account.
Proceed, Review, Block, No Result, or Run Failure. A canonical determination — not a score to interpret, not a lookup result to argue about. Every account leaves with exactly one, and the floor knows what to do with it.
Every decision shows its work.
Source, timestamp, and evidence lineage are retained on every production decision, alongside the registered reason and the policy basis. When someone asks why an account was worked the way it was, the answer already exists.
Agreement has to be earned.
Sources that trace back to one upstream file do not stack into corroboration no matter how many of them return the same answer. Independence is established before agreement counts for anything.
Accounts stop before the dial.
Attorney representation, deceased status, and restricted paths are detected and routed at determination time — not discovered afterwards by the person who already placed the call.
A failure is never dressed as an answer.
No Result is valid only after the permitted investigation completes. Routing and execution failures stay Run Failure and are reported separately, so an empty result is never quietly counted as a clean one.
Channel policy, account by account.
Call, SMS, email, and mail each come back allowed, blocked, or review, with the preferred next allowed step attached. The determination says not only whether you may act, but how.
Flat price, unlimited accounts.
Month to month, cancel any time. Nothing meters the work, so every account gets the full standard applied — the small balances exactly as the large ones.
The Standard Behind the Product
CAS-1 means Collections
Adjudication Standard 1.
CAS-1 is Gallus Resolve's deterministic operating standard for deciding whether an account may Proceed, requires Review, must be Blocked, produced No Result after a complete investigation, or experienced Run Failure.
It applies proprietary evidence-independence, restriction, execution-integrity, and decision-control rules. Detailed adjudication standards are provided under confidentiality during diligence and implementation.
Gallus uses customer-authorized first-party records, attached reports, and approved connected providers. Every production decision retains source, timestamp, and evidence lineage.
Bureau data is used when permitted and required by the customer-approved workflow. A bureau pull is valuable evidence, but it is not treated as a universal prerequisite.
No Result is valid only after the permitted investigation is complete. Provider or routing failures remain Run Failure and cannot be disguised as a substantive decision.
Six providers returning the same answer is not six confirmations when all six resell one upstream file. That is one opinion, counted six times, and treating it as corroboration is how a wrong number survives review. CAS-1 does not credit agreement until the evidence behind it is established as independent. The rules that make that determination are proprietary and are shared under confidentiality.
What Gallus Resolve Produces
A Recovery-Path
Decision Packet
Every account gets a CAS-1 determination packet — not a score and not a lookup result. It records the canonical outcome, evidence lineage, execution status, and policy basis.
The Decision is the Product
High-volume files become operator-ready decisions.
Records In
Gallus accepts files where names, phones, emails, addresses, or source records may be incomplete, stale, duplicated, conflicting, or unsafe to use directly.
File IntakeDecision Routing
Every account is evaluated under CAS-1 against first-party anchors, attached CBR evidence when available, provider returns, restrictions, and independent-family requirements. The engine returns a canonical decision — not a score.
Operator StateProof Returned
Operators receive the CAS-1 outcome, registered reason, evidence basis, restrictions, contact-path map, execution status, hashes, and next allowed step.
Review OutputControlled Evaluation
Prove Gallus on an authorized account set.
A limited-account evaluation lets your team run customer-selected accounts through the complete Gallus workflow using its approved records, policies, and evidence connections.
Evaluation activity remains inside a protected workspace and is bounded by an approved account allowance. Gallus documents system behavior and decision integrity; it does not predict liquidation, legal outcomes, or recovery performance.
- ✓Customer-selected accounts processed in a protected workspace
- ✓One terminal operating result for every record
- ✓Separate Proceed, Review, and Block queues
- ✓Run failures reported separately from substantive decisions
- ✓Determination and evidence integrity records for every account
- ✓Reconciled account counts and balances
Built For
Recovery Operations Teams
Controlled Trial
Run a controlled review
on a sample file.
Trial access is available by request. Your team uploads its own file, runs Gallus Resolve, and reviews decision packets, contact-path maps, suppressor flags, and next allowed steps in an audit-only evaluation with no consumer contact.