Using Live Account Data

Live account data helps Jardine answer account-specific questions. It should make decisions clearer, not riskier.

Core Rules

1. Identity mapping must be reliable.
2. Pull only the fields needed for the decision.
3. Always define fallback behavior.

Setup Sequence

1. Pick one account-specific use case.
2. Configure credentials and identity fields.
3. Test with controlled examples.
4. Check behavior when data is missing.
5. Roll out in small stages.

Safe Fallback Examples

If live data is missing:

1. Give a non-account-specific answer when safe.
2. Escalate to a human when account status is required.

If Something Is Off

Works for some users but not others

Identity mapping is usually the issue.

Data is returned but answer is still wrong

Returned fields may be incomplete for that decision.

Team cannot explain why context was used

Narrow connector scope and improve trace visibility.

Next Step

Continue with Daily Operations.