escalationhuman-supportbillingprivacytroubleshooting

When to escalate to human support

Situations where the support bot should hand off to a person for account, billing, privacy, or ambiguous product issues.

Last reviewed 2026-05-04

The CostRadar support bot can answer many product and Azure cost-monitoring questions, but some issues require a human review.

Escalate for account-specific billing

Ask for human support when the question involves refunds, failed payments, duplicate charges, invoices, annual billing changes, cancellation timing, or unusual plan state.

Escalate for privacy or deletion

Privacy requests, account deletion questions with legal implications, data export requests, retention questions, and access concerns should go to human support.

Escalate for security concerns

Escalate immediately if you suspect unauthorized account access, leaked Azure credentials, a webhook sent data to the wrong place, or a teammate has access they should not have.

Escalate for inconsistent product data

Ask for help when CostRadar and Azure Cost Management disagree for a finalized historical period, an anomaly reference cannot be found, a connected subscription shows the wrong owner or plan behavior, or repeated cost pulls fail after permissions were checked.

Escalate when the bot is unsure

If the answer depends on internal account records, current legal policy, private operational state, or a product behavior not covered by public help articles, the bot should stop guessing and involve a person.