Private Banking Wealth Onboarding Macro Architecture Specification

Role: Principal Client Experience Architect specializing in Private Banking Operations and Wealth Management Support Systems.

Context

• Financial Institution: {{institution_name}}
• Wealth Segment: {{target_client_tier}}
• Operational Platform: {{crm_ticketing_platform}}
• Friction Points: {{kyc_friction_scenarios}}
• Compliance Mandate: {{compliance_framework}}
• Escalation Criteria: {{escalation_threshold}}

Task

Author a comprehensive Macro Architecture Specification that defines standardized, multi-tiered response macros, conditional dynamic merge tags, and compliance routing triggers for support teams managing high-touch wealth management onboarding bottlenecks.

Method

1. Analyze {{kyc_friction_scenarios}} against {{compliance_framework}} to classify documentation blockers by risk profile and client sensitivity.
2. Map {{target_client_tier}} relationship dynamics to establish appropriate tone vectors, formatting norms, and white-glove communication protocols.
3. Architect macro taxonomy categorized by document collection, identity remediation, and jurisdictional tax residency verification within {{crm_ticketing_platform}}.
4. Design dynamic field insertion logic to safely pull custom client attributes without exposing non-public personal information across shared views.
5. Define deterministic escalation branch macros when client inquiries cross {{escalation_threshold}} or require private banker intervention.
6. Embed regulatory disclosure text blocks required by {{compliance_framework}} that cannot be manually edited or truncated by frontline agents.
7. Formulate explicit agent usage guidelines, detailing variable replacement checkpoints and mandatory audit tagging before ticket resolution.
8. Establish QA scoring rubrics to evaluate agent execution fidelity and client sentiment impact.

Constraints

• MUST embed immutable compliance disclosure snippets for all tax and identity inquiries under {{compliance_framework}}.
• MUST NOT include placeholders for sensitive PII; all dynamic parameters must reference system variables from {{crm_ticketing_platform}}.
• Every macro specification must contain fallback copy for incomplete account records.
• Tone must remain discreet, authoritative, and tailored to {{target_client_tier}} expectations.

Output format

Generate a technical specification structured under the following mandatory sections:

1. Executive Summary & Macro Taxonomy Tree (max 200 words)
2. Dynamic Field Variable Schema (data dictionary table)
3. Tiered Macro Templates (minimum 4 detailed macro specs with conditions, exact copy, and merge tags)
4. Regulatory Safeguards & Audit Rule Set
5. Agent Execution & QA Governance Protocol

Self-review

• Confirm all 6 variables ({{institution_name}}, {{target_client_tier}}, {{crm_ticketing_platform}}, {{kyc_friction_scenarios}}, {{compliance_framework}}, {{escalation_threshold}}) are addressed in the body.
• Verify that each macro specifies trigger conditions, required permissions, and variable fallback logic.
• Ensure no placeholder text exists and compliance disclosure blocks are fully articulated.