Wealth Management Personalized Macro Orchestration Plan
Design an automated, variable-injected macro strategy for high-net-worth client support and advisory workflows.
Apply this prompt when moving private banking and wealth advisory support teams away from static generic templates toward hyper-personalized, compliant communication blocks. It aligns dynamic CRM data with strict fiduciary standards.
Role: VP of Client Success Systems and Workflow Engineering for Private Wealth.
Context
- Client Asset Bracket: {{aum_bracket}}
- Primary CRM & Ticketing Infrastructure: {{crm_system}}
- Advisory Tier Hierarchy: {{advisory_tier_matrix}}
- Mandatory Fiduciary Disclaimer Policy: {{compliance_disclaimer_rule}}
- Macro Taxonomy Depth: {{macro_taxonomy_depth}}
- Target Agent Adoption Benchmark: {{target_agent_adoption_rate}}
Task
Architect an enterprise macro implementation plan for private wealth client associates that leverages dynamic data interpolation, preserves high-touch relationship tonality, and maintains absolute adherence to fiduciary regulatory standards.
Method
- Analyze current relationship manager communication patterns across the {{aum_bracket}} client base to isolate automatable touchpoints.
- Construct a taxonomy model across {{macro_taxonomy_depth}} hierarchical levels to ensure instant macro retrieval during live interactions.
- Define variable placeholder mappings connecting {{crm_system}} data objects (e.g., portfolio benchmark, custodian name) directly into message bodies.
- Design conversational fallback paths for scenarios where automated CRM attributes are unpopulated.
- Embed the mandatory requirements of {{compliance_disclaimer_rule}} conditionally based on product type discussed.
- Outline a rollout schedule categorized by the tiers in {{advisory_tier_matrix}} to pilot dynamic macros.
- Formulate a change management and adoption measurement strategy targeting {{target_agent_adoption_rate}} within 90 days.
- Establish a quarterly governance committee charter to prune stale templates and review client satisfaction shifts.
Constraints
- MUST NOT use generic support sign-offs; language must reflect tailored private banking concierge tone.
- MUST dynamically inject the exact disclosures mandated by {{compliance_disclaimer_rule}}.
- Templates must never display raw variable syntax (e.g., {{field}}) if data fields are null.
- Macro deployment must preserve full audit trail compatibility within {{crm_system}}.
Output format
- Section 1: High-Touch Macro Strategy & Design Philosophy (max 250 words)
- Section 2: CRM Dynamic Variable & Field Mapping Specification
- Section 3: Multi-Level Macro Taxonomy Blueprint (structured list)
- Section 4: Rollout, Adoption & Audit Governance Plan
Self-review
- Ensure the tone reflects the expectations of clients within {{aum_bracket}}.
- Confirm fallback logic is documented for missing {{crm_system}} data fields.
- Check that the adoption roadmap realistic reaches {{target_agent_adoption_rate}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.