Macros
AuraScore 81/100

Loan Servicing Macro Quality & Defect Root-Cause Analysis

Investigate borrower support macros to eliminate repeat ticket loops, statutory disclosure errors, and servicing friction.

Use this prompt when loan servicing operations suffer from high ticket reopening rates and borrower confusion. It delivers an analytical deep dive into underwriting and servicing macro defects, agent adherence, and root causes.

Template

Role: Senior Quality Assurance & Customer Operations Lead specializing in retail lending, mortgage servicing, and regulatory adherence.

Context

  • Lending Platform Name: {{lending_platform_name}}
  • Servicing Macro Transcripts: {{servicing_macro_transcripts}}
  • Ticket Reopen Rate Statistics: {{reopen_rate_statistics}}
  • Disclosure Compliance Standards: {{disclosure_compliance_standards}}
  • Target Borrower Lifecycle Stage: {{borrower_journey_stage}}
  • Agent Macro Adherence Data: {{agent_adherence_records}}

Task

Deliver an in-depth root-cause analysis of loan servicing response macros to eliminate borrower misunderstanding, rectify regulatory disclosure deficiencies, and systematically drive down ticket reopening rates.

Method

  1. Segment {{servicing_macro_transcripts}} across {{borrower_journey_stage}} to identify where standard responses fail to clarify amortization, payoff, or escrow calculations.
  2. Correlate specific canned phrases with spikes in {{reopen_rate_statistics}} to identify macro ambiguities that trigger secondary borrower inquiries.
  3. Audit all automated payment, forbearance, and delinquency macros against {{disclosure_compliance_standards}} to detect non-compliant phrasing.
  4. Analyze {{agent_adherence_records}} to distinguish between macro design flaws and agent modification errors during ticket handling.
  5. Evaluate cognitive load in macro structures, determining whether technical servicing terminology confuses distressed or non-expert borrowers.
  6. Identify missing conditional guidance segments that cause agents to dispatch mismatched templates during complex loan modification events.
  7. Develop a redesigned macro decision tree with standardized, compliance-cleared language blocks for high-volume servicing scenarios.

Constraints

  • Analysis MUST quantify how macro text defects directly contribute to the metrics in {{reopen_rate_statistics}}.
  • You MUST NOT recommend removing mandatory truth-in-lending disclosures or fee itemization breakdowns.
  • Findings must differentiate between borrower comprehension defects and statutory compliance violations.
  • Recommendations must provide measurable quality scorecards for frontline quality assurance teams.

Output format

Structure the final analysis into four clear sections:

  1. Defect Taxonomy & Reopen Root-Cause Analysis (350-450 words detailing specific linguistic and structural drivers of ticket churn).
  2. Compliance & Disclosure Gap Evaluation (comparative matrix listing macro name, statutory defect, and associated liability risk).
  3. Re-engineered Lending Macro Library (minimum 3 complete servicing macros featuring standardized placeholder syntax and conditional handling notes).
  4. QA Scorecard & Adherence Protocol (200-300 words outlining agent auditing standards and macro maintenance intervals).

Self-review

  • Verify that root-cause conclusions explicitly map back to {{servicing_macro_transcripts}} content.
  • Confirm that all proposed servicing macros strictly satisfy {{disclosure_compliance_standards}}.
  • Check that the proposed QA scorecard directly addresses issues identified in {{agent_adherence_records}}.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

support-success
support-macros
financial-services
macros
loan-servicing
lending