Agent output or workflow issue
Send the Agent name, expected outcome, date range, examples with private data removed, and the business impact.
Loading AI Team page
Use support to route Agent issues, access problems, billing questions, security concerns, setup changes, and service availability checks to the right review path.
Send the Agent name, expected outcome, date range, examples with private data removed, and the business impact.
Report the connected system, permission problem, rotation need, or revoked access without sending the credential itself.
Include the Agent, invoice or charge context, provider usage concern, spend cap, and whether work is blocked.
Use the public support path for non-secret impact context, then AI Team routes the issue through controlled operator review.
Ask for review when the Agent needs new systems, higher volume, different approval rules, or a new risk profile.
Check public status for broad service issues, then contact AI Team when your Agent or setup path still needs review.
What to send
A useful support request shows what changed, what was expected, and where the Agent or provider path got stuck.
Priority routing
AI Team separates live-work blockers, access risks, billing disputes, security concerns, and scope changes so the fix follows the right control path.
Live Agent work is blocked or producing materially wrong outcomes.
Access, credential rotation, permission, or connected-system cleanup is needed.
Billing, pass-through provider usage, or spend-cap behavior needs review.
A security, privacy, or public availability issue may affect buyers or client records.
A requested fix changes scope, setup, price band, approval rules, or go-live readiness.
No secrets
Use hello@aiteam.ae or the contact form for non-secret context. AI Team will ask for a controlled access path if the issue requires credentials, private records, or connected-system changes.
Service changes
When the fix needs new systems, higher volume, different approvals, extra provider usage, cancellation, credit, export, deletion, or connected-system cleanup, AI Team routes the request through the policy that controls that outcome.
The public status page covers confirmed buyer-visible service issues. Support handles Agent-specific output, access, setup, billing, provider usage, retention, and handoff questions with non-secret evidence.
This page explains routing for buyers. The applicable checkout, order form, support terms, invoice, service policy, DPA, retention policy, and legal review control formal response windows and commercial outcomes when they differ.
Read support termsFAQ
These answers help buyers report issues without turning support into an unsafe credential or private-data channel.
No. Public support is for non-secret context only. Credentials, private records, regulated records, customer exports, and confidential files are handled through controlled access review or an approved secure path.
No. Public support expectations explain routing. Response windows, priority coverage, service levels, refunds, credits, and cancellation outcomes are controlled by the applicable agreement.
Include the Agent name, expected outcome, date range, request ID when available, non-secret examples, approval or provider context, and the business effect. Do not include credentials or private records.
AI Team routes the issue back through setup, service policy, billing governance, or deployment readiness when the fix requires new systems, higher volume, new approval rules, extra risk, or a different price band.
Use the public status page for confirmed buyer-visible service issues. Individual Agent, setup, access, billing, or provider-cost issues should still be sent through support or contact.