Customer Onboarding Agent Tool Dependency Matrix
Map function execution paths, data dependencies, and fallback chains for digital identity verification agents.
Use this template when building multi-tool customer onboarding and AML screening workflows in retail or corporate banking. It generates a clear matrix of tool dependencies, validation gates, and human-in-the-loop escalation rules.
Role: Principal Financial Crime Automation Lead architecting multi-tool verification workflows for regulated digital onboarding.
Context
- Banking Entity: {{bank_entity}}
- Operating Jurisdictions: {{jurisdiction_scope}}
- Integrated KYC/Identity Endpoints: {{kyc_tool_endpoints}}
- Sanctions & PEP Provider: {{sanctions_database_vendor}}
- Case Escalation SLA: {{escalation_sla_minutes}} minutes
- Privacy & Data Governance Law: {{data_privacy_regulation}}
Task
Develop an exhaustive tool dependency and fallback matrix for an autonomous onboarding agent at {{bank_entity}} that orchestrates identity checks, watchlist screening, and document validation across {{jurisdiction_scope}}.
Method
- Sequence the linear and parallel function calls needed to onboard individuals and commercial entities.
- Map specific endpoints in {{kyc_tool_endpoints}} and {{sanctions_database_vendor}} to discrete verification steps.
- Establish prerequisite data inputs that must be validated before each downstream tool is invoked.
- Design data redaction gates to prevent PII leakage under {{data_privacy_regulation}} before payload transmission.
- Define deterministic criteria for positive matches, false positives, and partial matches across screening tools.
- Formulate fallback API routes and manual triage assignments when third-party endpoints fail.
- Calibrate decision timeouts to guarantee onboarding handoffs meet the {{escalation_sla_minutes}} SLA.
Constraints
- MUST represent the core execution logic as a comprehensive Markdown dependency matrix.
- MUST NOT allow identity verification tools to execute if prerequisite consent tokens are unverified.
- Output schemas MUST explicitly flag all fields containing PII governed by {{data_privacy_regulation}}.
- Escalation protocols MUST specify operational handoff queues for breach of the {{escalation_sla_minutes}} limit.
Output format
1. Workflow Architecture Overview
A structured summary (3-4 bullet points) explaining the orchestration strategy for {{bank_entity}}.
2. Onboarding Tool Dependency Matrix
A Markdown table containing columns: Step #, Tool / Function Identifier, Endpoint Source (from {{kyc_tool_endpoints}} or {{sanctions_database_vendor}}), Input Prerequisites, Output Artifacts, PII Classification, and Fallback Strategy.
3. Exception Escalation Matrix
A table mapping error codes and verification ambiguities to routing destinations, response timeouts, and actions within the {{escalation_sla_minutes}} threshold.
Self-review
- Check that every tool listed in {{kyc_tool_endpoints}} and {{sanctions_database_vendor}} is assigned a clear dependency chain.
- Confirm PII handling strictly respects {{data_privacy_regulation}} constraints.
- Verify all exception states possess an explicit path to human escalation under {{escalation_sla_minutes}}.
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.