Regulation X clocks are gated, not absolute. Track the acknowledgement, early-intervention and appeal windows and assemble the response pack; a named servicer employee decides, and a borrower can sue on the dates.
A portfolio-level on-time rate can read as healthy while a few loan cohorts absorb most of the late responses. Nestack reports the late-response rate by cohort, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Loans boarded from transfer
7.9%
3.7×
Review
Requests taken on calls
5.8%
2.7×
Review
Appeals under review
3.5%
1.6×
Watch
Portal-submitted requests
1.3%
0.6×
Normal
Bar: late-response-rate lift vs. portal-request baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle ends by adding a case
A cycle is closed when the late notice is a case the next release must survive. That suite is what the next response sent is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Late-response rate rises in a loan cohort.
02Diagnose
The acknowledgement that went out on day eight is read back until the cause narrows to one.
03Improve
The correction ships numbered, with the loans that prompted it attached.
04Verify
All touched notice cases run again, and a single fail stops it dead.
05Learn
It is kept as a standing case, and the clock rules are revised alongside.
Learn → DetectThe return edge. The next detection runs against a suite one notice case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, clock workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Servicing workflow discovery and boundary setting.
02Servicing and document-source assessment.
03Clock, gate and notice-content rule definition and rule mapping.
04Loan-record ingestion and date mapping.
05Clock computation and gate logic.
06Confidence scoring and escalation routing.
07Employee review workflow.
08Servicing-platform integration.
09Notice and clock cases.
10Guardrails and response controls.
11Loan-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne investor, one bookProductionProduction servicing systemsAdvancedMultiple investors / books
Introduced at Pilot
Tracking to your loans and clocks✓✓✓
Employee review✓✓✓
Clock-coverage baseline✓✓✓
Introduced at Production
Reporting by investor—✓✓
Review workflow in your systems—✓✓
Approved write-back—✓✓
Servicing-platform integration—✓✓
Introduced at Advanced
Multi-state servicing rules——✓
Multi-stage servicer approvals——✓
High default volume——✓
Multi-investor response controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your loan records and delinquency fields→Loan-record ingestion and date mappingWeek 1
02Representative past default files→Clock baseline, source binding and gate mappingWeek 2
03Your notice templates and content rules→Clock, gate and notice-content rule mappingWeek 1
04Access to relevant APIs, feeds or exports→Servicing and document-source assessment, then integration setupWeek 2
05Responses you would not want litigated→Appeal cases and the evaluation suiteWeek 4
06What no response may miss→Confidence scoring, escalation routing, guardrails and approval controlsWeek 3
07Named employees, and separate personnel for appeals→Employee review workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The plan is drawn on the weeks the work truly fills, so the overlap in week 5 is work, not padding.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Servicing workflow discovery, clock mapping and the automation boundaryW2Source integration and the clock baselineW3Clock workflow, gate logic and review controlsW4Evaluation suite, notice-content checks and failure-mode testingW5Servicing integration, pilot loans and targeted correctionsW6One default cycle run under the servicing manager, then Agent Care handover
Reading the bandA bar covers the weeks its work is named in, and nothing else. The week 5 overlap is real, not padding.
At the end of W6When the default cycle validates, Agent Care takes the agent on.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Banking AI agent
Build a servicing agent around the clocks a borrower can enforce.
Show us your loan records, your notice templates and who signs them. When a notice goes out late the servicer carries the violation and the borrower's claim, not the vendor. We build to Regulation X as it stood on 14 August 2026.
