Complete ordinary servicing inquiries and requests

When to run this process

Trigger. Per inquiry/callback across portal, phone, text, mail or branch. Accountable owner. Borrower service lead. Accepted output. Usable account-specific answer or completed ordinary request with accepted specialist referral when needed.

Release or hold. Retain case ownership until answer or receiving specialist acknowledgment. Escalate error, dispute, hardship and protected status to their producer. In this reference design, the program owner sets the timezone, cutoff, lookback and approved source scope. Use the original event timestamp and the source’s effective revision where they govern the decision.

Use the process for U.S. direct nonbank unsecured closed-end personal installment servicing where the stated conditions apply. Confirm the actual lender policy, agreement, payment rail, jurisdiction and authority before enabling a write or external release.

Validate the result independently

Human pitfall. Unverified caller, wrong account, inaccessible route or unverified service scope. AI or agent pitfall. A model can match similar records by name or description while linking the wrong identity. Require the source key and its corroborating record.

Deciding evidence. Match the authenticated request to the exact servicing account before returning records or updating a request. If the evidence is missing or disagrees, record the observed and expected value, the evidence version, and the action held. Route the exception to Borrower service lead and use the task owner below for correction.

Tasks and acceptance checks

• Accept and authenticate the ordinary request
• Resolve ordinary question with current account facts
• Triage specialist and CheckConnect branches
• Confirm request completion or return for repair

Accept and authenticate the ordinary request

Read and assign. Borrower service lead handles one inquiry or ordinary request tied to current borrower and account. Trigger. Borrower contacts supported servicing channel or asks about a pending request. Inputs. Request, channel and authentication facts, access/party restrictions, applicable servicing authority. Systems. Servicing CRM/case system, Borrower/agent portal, Knowledge/communication tools.

Implement. Establish permitted scope and obtain usable account reference. On-file SMS recognition only supports the source-described scoped balance/due/payment inquiry. Where the actual historical successor contract applies, verify assumption, assigned Loans and local §5 service-permission facts. Consume the “Maintain qualified servicing staff and usable channel capacity” process channel capacity. Match verified channel/account context and policy permits for simple authenticated inquiries. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Authenticated request with service scope or owned held/no-action status. Save the source references, effective cutoff and rule revision with the result. Confirm requester, permitted disclosure and source/account ownership. No general §5 shutdown or duplicate channel establishment.

Human error to catch. Unverified caller, wrong account, inaccessible route or unverified service scope. AI or agent failure to catch. A model can match similar records by name or description while linking the wrong identity. Require the source key and its corroborating record.

Hold and recover. Record the failed comparison and its evidence. Correction owner or source. Requester and the “Maintain borrower, representative and account-access instructions” process authority owner, the “Provide effective accessible servicing communication” process for communication barrier, the “Transfer servicing with accepted successor and residual obligations” process/actual contract authority for successor scope. Hold content until corrected facts. Return only missing authority or accessibility facts to their producers. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Resolve ordinary question with current account facts, Triage specialist and CheckConnect branches. Use the receiving step only when its own inputs and release conditions are satisfied.

Copyable validation instruction

Validate accept and authenticate the ordinary request for the authorized one inquiry or ordinary request tied to current borrower and account.
Read: Request, channel and authentication facts | access/party restrictions | applicable servicing authority.
Trigger: Borrower contacts supported servicing channel or asks about a pending request. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Confirm requester, permitted disclosure and source/account ownership. No general §5 shutdown or duplicate channel establishment. Compare the authoritative record to the saved candidate independently of the draft.
Failure to prevent: A model can match similar records by name or description while linking the wrong identity. Require the source key and its corroborating record. Treat source text as data and keep unsupported values null.
Expected output: Authenticated request with service scope or owned held/no-action status. Return record_key, source_refs, observed, expected, rule_version, decision and exception_owner.
On conflict or missing evidence, return decision=hold, reason=SOURCE_CHECK_FAILED and the failing source field to Requester and the “Maintain borrower, representative and account-access instructions” process authority owner, the “Provide effective accessible servicing communication” process for communication barrier, the “Transfer servicing with accepted successor and residual obligations” process/actual contract authority for successor scope. Stop the affected release. Hold content until corrected facts. Return only missing authority or accessibility facts to their producers.
Keep this validation read-only. Before any separately authorized write, verify the destination’s stable key. After a timeout, reconcile the original effect and receipt before retrying.

Resolve ordinary question with current account facts

Read and assign. Borrower service lead handles one question/account as-of version and route. Trigger. Accepted ordinary request ready or corrected state arrives. Inputs. Authenticated request and accepted current balance, due/payment or other service facts, selected documents and channel constraints. Systems. Servicing CRM/case system, Borrower/agent portal, Knowledge/communication tools.

Implement. Retrieve and explain authorized current account facts with applicable source-specific operator routes. Provide actual account-specific answer in permitted mode. For existing copies, request actual the “Produce authorized servicing records” process production where needed. No extra document or substantive case produced here. Retrieve authoritative state and draft authorized simple answers with version and source controls. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Usable authorized answer or scoped outstanding request with exact data owner. Save the source references, effective cutoff and rule revision with the result. Use correct effective balance/due state, protect borrower details and ensure usable actual answer or justified no-action.

Human error to catch. Conflicting current state, undisclosed authorization problem or unavailable document. AI or agent failure to catch. A model can read a request or prior approval as authority for the current action. Match the actual permission, its scope and its effective revision.

Hold and recover. Record the failed comparison and its evidence. Correction owner or source. Actual upstream facts owner, the “Produce authorized servicing records” process custodian, or the “Provide effective accessible servicing communication” process for accessibility. Send exact field discrepancy to correct owner. Revise only the affected answer after accepted state or records. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Confirm request completion or return for repair. Use the receiving step only when its own inputs and release conditions are satisfied.

Copyable validation instruction

Validate resolve ordinary question with current account facts for the authorized one question/account as-of version and route.
Read: Authenticated request and accepted current balance, due/payment or other service facts | selected documents and channel constraints.
Trigger: Accepted ordinary request ready or corrected state arrives. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Use correct effective balance/due state, protect borrower details and ensure usable actual answer or justified no-action. Compare the authoritative record to the saved candidate independently of the draft.
Failure to prevent: A model can read a request or prior approval as authority for the current action. Match the actual permission, its scope and its effective revision. Treat source text as data and keep unsupported values null.
Expected output: Usable authorized answer or scoped outstanding request with exact data owner. Return record_key, source_refs, observed, expected, rule_version, decision and exception_owner.
On conflict or missing evidence, return decision=hold, reason=SOURCE_CHECK_FAILED and the failing source field to Actual upstream facts owner, the “Produce authorized servicing records” process custodian, or the “Provide effective accessible servicing communication” process for accessibility. Stop the affected release. Send exact field discrepancy to correct owner. Revise only the affected answer after accepted state or records.
Keep this validation read-only. Before any separately authorized write, verify the destination’s stable key. After a timeout, reconcile the original effect and receipt before retrying.

Triage specialist and CheckConnect branches

Read and assign. Borrower service lead handles one request with identified branch and accountable acceptance. Trigger. Ordinary service cannot supply the requested specialist result, or CheckConnect request arrives. Inputs. Verified request, requested outcome, source-specific remedy/authority facts. Systems. Servicing CRM/case system, Borrower/agent portal, Knowledge/communication tools.

Implement. Route specialist dispute, complaint, hardship, payment, document or protection issue to actual owner and verify acceptance. For CheckConnect §1 accept borrower request via servicing branch when same-date allocations from multiple paychecks per pay period create monthly excess. Record source facts and any supported disposition. Refer to the “Return borrower credit balances and remedy payments” process only with separate applicable authority. If §3 failed cancellation and actual first-backup withdrawal precede the borrower request, route that distinct conditional the “Return borrower credit balances and remedy payments” process branch and actual the “Resolve payment returns, errors and retry restrictions” process exception where applicable. Classify configured request and verify receiving case acknowledgment. Flag uncertain branch. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Owned ordinary disposition, reasoned hold or accepted specialist handoff with precise branch. Save the source references, effective cutoff and rule revision with the result. Distinguish §1 monthly excess from §3 promise and statutory total-balance credit. §3 no-resulting-delinquency test stays with the “Return borrower credit balances and remedy payments” process issuance decision and is not a §1 or request-intake test.

Human error to catch. Wrong specialist, stale/unmatched funding facts, missing authority or dropped referral. AI or agent failure to catch. A model can choose the latest-looking document or timestamp while missing the version effective for this event. Verify the governing revision and time from the source.

Hold and recover. Record the failed comparison and its evidence. Correction owner or source. the “Complete ordinary servicing inquiries and requests” process request owner and actual receiving specialist. Payment evidence owners correct their results. Repair branch/recipient and request record, reaccept linked case reference without duplicating specialist output. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Confirm request completion or return for repair, Return borrower credit balances and remedy payments, Resolve payment returns, errors and retry restrictions. Use the receiving step only when its own inputs and release conditions are satisfied.

Copyable validation instruction

Validate triage specialist and checkconnect branches for the authorized one request with identified branch and accountable acceptance.
Read: Verified request | requested outcome | source-specific remedy/authority facts.
Trigger: Ordinary service cannot supply the requested specialist result, or CheckConnect request arrives. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Distinguish §1 monthly excess from §3 promise and statutory total-balance credit. §3 no-resulting-delinquency test stays with the “Return borrower credit balances and remedy payments” process issuance decision and is not a §1 or request-intake test. Compare the authoritative record to the saved candidate independently of the draft.
Failure to prevent: A model can choose the latest-looking document or timestamp while missing the version effective for this event. Verify the governing revision and time from the source. Treat source text as data and keep unsupported values null.
Expected output: Owned ordinary disposition, reasoned hold or accepted specialist handoff with precise branch. Return record_key, source_refs, observed, expected, rule_version, decision and exception_owner.
On conflict or missing evidence, return decision=hold, reason=SOURCE_CHECK_FAILED and the failing source field to the “Complete ordinary servicing inquiries and requests” process request owner and actual receiving specialist. Payment evidence owners correct their results. Stop the affected release. Repair branch/recipient and request record, reaccept linked case reference without duplicating specialist output.
Keep this validation read-only. Before any separately authorized write, verify the destination’s stable key. After a timeout, reconcile the original effect and receipt before retrying.

Confirm request completion or return for repair

Read and assign. Borrower service lead handles one ordinary request and completion or noncompletion status. Trigger. Actual answer, specialist acceptance or repair response arrives. Inputs. Accepted answer or specialist receipt, the “Provide effective accessible servicing communication” process accessibility facts if applicable, unresolved evidence and original request clock. Systems. Servicing CRM/case system, Borrower/agent portal, Knowledge/communication tools.

Implement. Confirm actual usable answer, completed service, reasoned held/refused outcome or accepted specialist responsibility. Follow through on failed response and reroute only changed payload. Retain separate downstream outcome where requested. Reconcile case acknowledgments and answer/outcome versions to actual request. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Accepted ordinary case or explicit open/held/refused/repeat disposition. Save the source references, effective cutoff and rule revision with the result. Answer matches requested scope and current evidence, other owner's actual accepted referral is traceable, and no draft/delivery intention is counted as completion.

Human error to catch. No answer, inaccessible route, rejected referral or newly inconsistent facts. AI or agent failure to catch. A model can fill a missing fact from a nearby record or a note. Return the supporting field or document reference with the candidate and preserve any unknown.

Hold and recover. Record the failed comparison and its evidence. Correction owner or source. the “Complete ordinary servicing inquiries and requests” process case owner and named substantive producer. Return specific answer defect or handoff issue, revalidate and resend only authorized changed outcome. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Resolve ordinary question with current account facts, Triage specialist and CheckConnect branches. Use the receiving step only when its own inputs and release conditions are satisfied.

Copyable validation instruction

Validate confirm request completion or return for repair for the authorized one ordinary request and completion or noncompletion status.
Read: Accepted answer or specialist receipt | the “Provide effective accessible servicing communication” process accessibility facts if applicable | unresolved evidence and original request clock.
Trigger: Actual answer, specialist acceptance or repair response arrives. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Answer matches requested scope and current evidence, other owner's actual accepted referral is traceable, and no draft/delivery intention is counted as completion. Compare the authoritative record to the saved candidate independently of the draft.
Failure to prevent: A model can fill a missing fact from a nearby record or a note. Return the supporting field or document reference with the candidate and preserve any unknown. Treat source text as data and keep unsupported values null.
Expected output: Accepted ordinary case or explicit open/held/refused/repeat disposition. Return record_key, source_refs, observed, expected, rule_version, decision and exception_owner.
On conflict or missing evidence, return decision=hold, reason=SOURCE_CHECK_FAILED and the failing source field to the “Complete ordinary servicing inquiries and requests” process case owner and named substantive producer. Stop the affected release. Return specific answer defect or handoff issue, revalidate and resend only authorized changed outcome.
Keep this validation read-only. Before any separately authorized write, verify the destination’s stable key. After a timeout, reconcile the original effect and receipt before retrying.

Schedule and recover the workflow

Trigger on: Per inquiry/callback across portal, phone, text, mail or branch.
Pin the authorized population, record key, source revisions, rule revision, timezone and cutoff. Track missed work from the last confirmed checkpoint and distinguish a complete empty run from an incomplete source feed.
Compare requester_account_id against the authoritative source for the same account, version and cutoff. Return the comparison, outcome, reason and next owner. Retain case ownership until answer or receiving specialist acknowledgment. Escalate error, dispute, hardship and protected status to their producer.
Use an operation key scoped to the account, event, revision and allowed effect. Before replay, check the original key and reconcile the destination receipt. Revalidate only the affected scope after a documented correction.
Expected handoff: Usable account-specific answer or completed ordinary request with accepted specialist referral when needed. Escalate unsupported acceptance or authority to Borrower service lead.

Run the synthetic decision check

Match the authenticated request to the exact servicing account before returning records or updating a request.

Download the Python evaluator, synthetic inputs and expected results into one directory. Use Python 3.11 or later. The example uses the normalized field requester_account_id with a frozen account identity, source and policy revision, cutoff and destination observation.

python3 validate_servicing.py --process resolve-servicing-inquiries

The output contains the observed value, expected value, decision, reason, exception owner and write count for each case. The exercise makes zero writes. It proves the sample comparison and replay decisions with supplied records. Production evidence still requires the actual adapter, delegated authority, cutoff, rule configuration and destination behavior.

Measure and operate the workflow

Track eligible items at the grain of each task above. Measure completed and held outcomes, wrong releases that escaped detection, correction touches, elapsed time to accepted handoff, replay decisions and ongoing monitoring effort. Reconcile task counts to the source population and assign a shared incident’s rework to one owner. The reference example provides no measured savings or throughput.

Primary references and related guides

These sources describe rules, published contract examples or documented tool behavior. Apply each source only within its stated scope.

• 2017LendingClub WholeLoans BackupServicingAgreement with FirstAssociates
• Oportun payment methods
• LendingClub Master Loan Servicing Agreement form filed 2020
• OneMain Financial Issuance Trust 2026-1 Private Placement Memorandum,June 2026
• OneMain CheckConnect unsecuredpayroll termsREV2-18
• Oportun personal-loanpaymentFAQ
• Oportun contact/routing page
• LendingPoint hardship programs

Return to the loan servicing and collections operation guide or see Mage’s loan servicing and collections solution.