Assistant outputs are intended for decision support. They do not replace legal, tax, or regulated professional advice.
Core principles
Ground responses in authorized data and active product context.
Respect tenant and user access boundaries for every generated response.
Do not provide regulated legal, tax, or financial advice; provide guidance and escalation paths instead.
v1.5.8 safety updates
v1.5.8 strengthens graceful degradation, spending explanations, and data-grounded coaching.
- Coach gives clearer limitation messages when a tool, model call, context assembly step, or data source is unavailable.
- Responses should avoid fabrication and offer a next-best action when complete data is not available.
- Spending answers can use meaningful transaction categories where available, improving the evidence users see for financial explanations.
- Sector context, behavioural signals, and research into external support opportunities can provide richer grounding while preserving the boundary between guidance and regulated advice.
- Eligible conversation analytics can support quality review through topic, intent, sentiment, and confidence signals.
Safety controls in practice
Prompt + routing guardrails
Detect high-risk or out-of-scope requests and route to restricted handling paths.
Runtime disclaimers
Show explicit user-facing disclaimers for known uncertainty or processing states.
Refusal behaviour
Refuse disallowed requests with clear rationale and safe alternatives.
Validation suites
Test tone, scope, and trigger behaviour to catch regressions before release.