Collections 101 · The daily work
Outbound calling
Attempts, contacts and conversations are three different things. How an outbound operation is actually structured, and the rules that shape it.
Attempts are not contacts
An outbound operation runs on three numbers that beginners tend to collapse into one. An attempt is a call placed. A contact is a call answered by a human being. A right-party contact is a conversation with the person actually obligated on the account. Most attempts are not contacts, and a fair share of contacts are not right-party contacts, because phone numbers on charged-off accounts are old, reassigned, shared, or belong to somebody else entirely.
That gap is why the job feels the way it does, and it is also why the rules governing frequency are written in terms of attempts per person per debt rather than per phone number: an operation that dials six numbers for one consumer has still called that consumer six times.
How the queue gets built
Accounts are not dialled in the order they arrived. A work list is assembled by rules: how new the placement is, the balance, the last outcome recorded, whether a payment arrangement is due, whether a promise was broken, what time zone the consumer is in, and whether anything on the account forbids contact altogether.
That last check runs first and it runs on the account, not on the collector's memory. Accounts flagged for bankruptcy, attorney representation, a cease request, a dispute in progress, deceased, or service member protections do not belong in a calling queue at all. Nor do numbers a consumer has told you not to use, or channels they have withdrawn consent for.
Where a number came from is also part of the record. A number supplied by the consumer, a number from the creditor's file and a number produced by skip tracing are not equivalent, and treating them as equivalent is how firms end up calling people who have nothing to do with the debt.
The rules that shape the day
Four constraints do most of the shaping, and each of them is set out with its primary sources in this site's compliance reference rather than summarised here.
Frequency. Federal rules place limits on how often a collector may call a consumer about a particular debt within a period, counted in a specific way. The counting rules are the part people get wrong; the linked explainer works through them.
Time and place. There are constraints on when a consumer may be called and on calling them somewhere they have said they cannot take calls.
What you may say to somebody else. Leaving a message risks disclosing the debt to a third party. A tightly limited form of message exists precisely so a collector can ask for a return call without disclosing anything.
Consent for the technology used. Depending on how a call or text is placed, separate consent rules apply, and a consumer can withdraw that consent.
None of these are things a new collector should be reconstructing from memory on a call. In a well-run operation they are enforced by the system before the call is placed, which is a great deal safer than a policy everybody has read.
The disposition is the record
Every attempt ends with a disposition code: no answer, busy, voicemail, wrong number, third party, refused, promise to pay, dispute raised, attorney representation stated, cease requested, and so on. Those codes are not statistics. They are the evidence layer.
When a client samples your work six months from now, the codes are what get read: did the collector recognise a dispute when they heard one, did contact actually stop after a cease request, did an attorney representation get recorded on the account rather than in a note nobody parses. A collector who dispositions accurately is doing compliance work whether or not it is described that way, and a collector who reaches for the nearest code to close the screen is quietly destroying the firm's ability to prove anything.
What this looks like in practice
Illustrative. A collector opens the next account in the queue. The screen shows the two numbers permitted for this consumer, how many attempts have already been made against this debt inside the current window, and a note that the third number on file was supplied by a skip-trace vendor and has not been verified.
The first number rings out. The collector leaves a message in the limited-content form, which discloses nothing about the debt to whoever might hear it, and dispositions the attempt as voicemail. The second number is answered by someone who is not the consumer and says they have never heard the name. That disposition is not no answer and not wrong party in some vague sense — it is recorded as a third party who denied knowing the consumer, because that is what will matter if anybody ever asks why the number stopped being called.
What to carry out of this lesson
- Frequency rules count attempts per consumer per debt, not per phone number.
- The suppression check runs before dialling, on the account, not from memory.
- A limited-content message exists so a collector can ask for a call back without disclosing the debt.
- Disposition codes are the evidence a client's audit will read.
Key terms
Defined once, in the glossary. These link to the definition and its sources.
- Right-party contactA right-party contact, or RPC, is a live conversation with the consumer actually obligated on the account, as opposed to a wrong number, a third party, or an unanswered attempt.
- 7-in-77-in-7 is the Regulation F telephone-frequency rule under which a debt collector is presumed to comply with the FDCPA's harassment prohibition if it places no more than seven calls to a particular person about a particular debt within seven consecutive days, and none within seven days after a telephone conversation about that debt.
- Limited-content messageA limited-content message is a voicemail for a consumer that contains only the content Regulation F permits and, because it is defined not to be a "communication" in connection with debt collection, can be left without triggering the mini Miranda or risking a third-party disclosure.
- Disposition codeA disposition code is the standardized value a collector or system writes to an account after a contact attempt, recording the outcome — right-party contact, wrong number, no answer, refusal, promise to pay, dispute, attorney representation — and driving the next scheduled action.
- Promise to payA promise to pay, or PTP, is a consumer's commitment during a contact to pay a stated amount on a stated date, logged on the account and used to schedule follow-up and suppress other collection activity until the date passes.
- Skip traceSkip tracing is the process of locating a consumer or verifying current contact information — address, telephone number, employer — when the information supplied at placement is stale or wrong.
Where the rules are written down
This lesson describes how the work is done. What the law requires is set out in the reference, with its primary sources.
- How Does the 7-in-7 Call Frequency Rule in 12 CFR 1006.14(b)(2) Actually Count?12 CFR 1006.14(b)(2) presumes compliance at seven calls per seven days per debt, and bars calls for seven days after a telephone conversation.
- TCPA Consent and Revocation: What Do 47 U.S.C. 227 and 47 CFR 64.1200 Require for Collection Calls and Texts?Consent and revocation under 47 U.S.C.
- What Is the FDCPA (15 U.S.C. 1692), and Who Does It Actually Cover?The FDCPA's scope, the 15 U.S.C.
This is an informational reference, not legal advice, and using it creates no attorney-client relationship. Limitations periods turn on facts this page cannot know — which state's law governs, the contract type, when the claim accrued, and whether anything tolled or revived it. Confirm against the primary source and your own counsel before acting.