What goes in
Agency account files, identity fields, contact candidates, address history, known restrictions, prior outcomes, and evidence returned through the organization’s contracted provider APIs.
Collection agency decision software
Quorum is a CAS-1 collections adjudication engine for collection agencies, receivables teams, collection law firms, and other operations that must review incomplete or conflicting account records before treatment. It sits above customer-owned evidence sources and converts them into one canonical outcome, a registered reason, evidence lineage, execution status, and the next allowed step.
Agency account files, identity fields, contact candidates, address history, known restrictions, prior outcomes, and evidence returned through the organization’s contracted provider APIs.
Normalizes records, compares evidence, reverses contact paths, evaluates identity collisions, builds address timelines, applies restrictions, and routes unresolved ambiguity to structured review.
A completed decision packet with the operator state, evidence summary, restrictions, unresolved questions, contact-path status, reason code, and next allowed step.
Decisioning instead of another data list
Traditional skip-trace databases and enrichment providers are valuable sources, but their output is usually a set of records, candidates, attributes, or confidence signals. The agency is still responsible for reconciling conflicts and deciding what happens next. Quorum performs that decision-layer work without replacing the organization’s provider relationships.
| Capability | Raw enrichment or skip-trace output | Quorum decision layer |
|---|---|---|
| Primary output | Possible phones, emails, addresses, people, or profiles | A documented operator state and next allowed step |
| Conflicting evidence | Returned for the user to interpret | Normalized into evidence, contradictions, and review reasons |
| Restrictions | May appear as separate fields or source returns | Applied as routing constraints that can block or limit a path |
| Ambiguity | Often represented as lower confidence or multiple candidates | Converted into a named manual-review or insufficient-confidence outcome |
| Auditability | Provider response or lookup history | Decision reason, evidence summary, unresolved questions, and policy-aware next step |
For a deeper explanation, read how the Quorum decision layer differs from data enrichment.
Recovery workflow
Quorum is designed to run after an account file enters the organization and before the record is released into an approved operational workflow. It does not contact consumers, replace legal review, or create a permissible purpose. The customer remains responsible for provider contracts, data rights, policies, and downstream treatment.
See industries and use casesStandardize names, phones, emails, addresses, identifiers, account references, and known restrictions from a recovery file.
Use customer-owned provider access. Quorum discovers safe provider endpoints, selects calls according to the evidence gap, and normalizes returned data.
Check reversals, same-name collisions, address chronology, household relationships, life events, and restriction signals before producing a state.
Send Proceed records forward, isolate targeted Review work, Block prohibited paths, and return No Result only after the permitted investigation is complete.
What the decision packet can include
Subject identity, aliases, prior surnames, candidate clusters, and collision risk.
Residential, institutional, employment, business, estate, and associated-location evidence organized chronologically.
Phone, email, mail, spouse, attorney, estate, employment, or third-party location-information paths with supported, ambiguous, restricted, or unsupported status.
Agency suppressions, known wrong-party history, cease indicators, attorney representation, bankruptcy, deceased or estate signals, and workflow exclusions where available.
Named ambiguity that tells the operator exactly what remains unresolved instead of dumping a full record into a generic queue.
A plain operational instruction tied to the evidence and policy state, such as enter the approved workflow, obtain more evidence, route to review, or do not advance.
Questions from collection and recovery teams
No. Quorum is a decision and audit layer that can sit above existing collection, receivables, CRM, and provider systems. It determines how a record should be routed before the customer’s downstream workflow acts.
No. Organizations keep their own contracted provider relationships. Quorum discovers and orchestrates safe provider endpoints, normalizes the evidence, and produces the finished decision.
No software can replace legal advice, licensing obligations, permissible-purpose requirements, or agency policy. Quorum helps apply configured restrictions and produces an auditable decision packet, while the customer remains responsible for its legal and operational decisions.
Quorum returns Review when a named evidence issue remains, No Result only after a complete investigation, or Run Failure when execution could not complete. Ambiguity is never hidden as a weak positive match.
Quorum is a subscription metered in completed decisions — never per profile and never per lookup. You bring your own provider keys, so provider charges stay on your account. A Block sourced from your own suppression list consumes no allowance. Terms are set in conversation against your file, your provider stack, and your volume. CAS-1 licensing and creditor-program terms are separate.
More operational and commercial answers are available in the Quorum FAQ.
Agency-operated evaluation
Your team connects its authorized providers, uploads a controlled file, runs the decision engine, and reviews completed decision packets without handing the file to Quorum. Guided setup is available for early agencies; routine operation is designed to be self-service.