An example of debt collection as a governed process: agents do the 10 steps, and a person signs the gate before anything irreversible happens. Download it, import it into your workspace, and adapt it to your systems.
minctrl.process/v1 · hash d7f5ab004ffb…1965
Collections is high-volume, script-driven outreach gated by FDCPA / Reg F / TCPA — where one mistimed automated contact is a class-action vector. Accounts are segmented and worked with compliant, logged outreach and self-serve payment plans; only legal escalation, settlements and disputed debts reach a manager, who signs.
Reporting a debt to a credit bureau or escalating to legal action is hard to unwind and directly affects a consumer, so a human signs off before those steps and before any deviation from the FDCPA/Reg F contact limits.
| Rule | What it requires |
|---|---|
| FDCPA / Regulation F (CFPB) | Regulation F sets a call-frequency presumption of no more than 7 calls within a 7-day period per particular debt, and no call within 7 days of a conversation about that debt; it also governs communication times, places and content. |
| Debt validation notice | Consumers must receive the validation information / notice and, if they dispute in writing within 30 days, collection must pause until the debt is verified. |
| Cease-communication & FCRA furnishing | A written cease-communication request must be honored, and any furnishing of debt data to a consumer reporting agency must be accurate and follow FCRA dispute-handling rules. |
A summary for orientation, not legal advice.
A minctrl.process/v1 document: the graph and the hash of the process it becomes.
Import into Minctrl opens this example in your workspace; one click stores it as your first version. Import JSON does the same with the file, and a file changed after download is refused.
Every connector starts in shadow: steps run, nothing leaves Minctrl until you configure a connector and switch it live.
Change signers, time limits and steps on the canvas. Each save is a new version; a running case stays on the version it started with.
The flow tracks every contact against Regulation F's call-frequency presumption — no more than 7 calls in a 7-day period per debt, and no call within 7 days of a conversation about that debt — plus permitted times and channels. Attempts that would breach the caps are blocked, and the contact log is retained as evidence.
A written dispute within 30 days of the validation notice pauses collection on that debt until it is verified. The AI agent routes the dispute and holds outreach; a cease-communication request is honored the same way, and both are recorded with a tamper-evident audit hash.
No. Furnishing a debt to a consumer reporting agency, or escalating to legal action, is hard to reverse and directly affects the consumer, so it parks at a human sign-off gate. The AI clears the reversible outreach volume; a person owns the steps that hit someone's credit file.
| Example | Steps | Gates |
|---|---|---|
| Bookkeeping & close | 13 | 1 |
| SOX ITGC audit | 13 | 1 |
| Mortgage-underwriting | 13 | 1 |
| Tax-prep | 12 | 2 |