Aiô answers 24 hours, 7 days, inside the system (⌘/). Human support works 9 a.m. to 6 p.m., Monday to Friday, at suporte@ingestia.io and on the Support screen.
How to ask for help, what to include to speed up the fix, and where to follow the platform's availability.
Support#
| Channel | When |
|---|---|
| Aiô (button in the bottom-right corner, or ⌘/) | 24 hours, 7 days |
| Human — suporte@ingestia.io or the Support screen | 9 a.m. to 6 p.m., Monday to Friday (Brasília time) |
First human response time, counted in business hours:
| Plan | First response |
|---|---|
| Starter | 1 business day |
| Growth | 8 business hours |
| Business | 4 business hours |
| Scale | 2 business hours |
| Enterprise | defined in contract |
- Availability: SLA of 99.5% per month from the Growth plan, with service credit; Starter is best effort. Rules in Service level (SLA); public measurement at /status.
- Language: Portuguese, English and Spanish.
- Region: Brazil (São Paulo).
Permissions#
- Anyone in the workspace can open a request. Requests that require account action (change plan, revoke key, add a domain to the embed allowlist) may require confirmation from the workspace owner.
Before the ticket: ask Aiô#
Aiô (button in the bottom-right corner, or ⌘/) investigates your environment — including the run that just failed —, explains and, when possible, does it for you: it proposes the action and you confirm with one click. It accepts screenshots and audio. See Aiô — the assistant.
If it does not solve it, mark "did not solve my problem" when closing: the conversation becomes a ticket, already with the question, the answer and the source screen. The queue is in Support, in the avatar menu.
How to open a ticket#
- Through Aiô (⌘/) — the fastest path and the only one that already carries the context: close the conversation marking that it did not solve it.
- By email: suporte@ingestia.io, 9 a.m. to 6 p.m., Monday to Friday.
- Contact form (Business/Enterprise plans and pre-sales):
/contato-enterpriseon the site. - Before opening, check whether the answer is already in Frequently asked questions (FAQ) or in Troubleshooting.
What to include (speeds things up a lot)
- Workspace (name/identifier) and when it happened (date/time).
- What you tried to do and what you expected.
- The exact HTTP code and
errormessage (for API integrations). - Steps to reproduce; screenshots help. Never paste secrets (API key, embed secret, passwords) — if a secret leaked, revoke/rotate it first.
Severities#
We use these levels to prioritize the queue:
| Severity | Example |
|---|---|
| Critical | platform unreachable; one customer's data visible to another (suspected) |
| High | core function broken with no workaround (ingestion/BI stopped) |
| Medium | function with a workaround; intermittent error |
| Low | question, improvement, cosmetic adjustment |
Suspected data leak between customers or of a credential: treat it as Critical, revoke/rotate the credential immediately and report it in the ticket.
Validation (how to know your ticket moved forward)#
- You receive a confirmation with a ticket identifier and follow progress on the Support screen.
- Feature state changes are reflected in Status and availability.
Example#
A Power BI integration started returning 429. The customer checks the
error catalog, sees it is rate
limiting, reduces parallelism and — since it persists — opens a Medium
ticket with the time, the Retry-After received and the call frequency.
Cost#
- Opening and following tickets: R$ 0. Support does not consume credits.
Security#
- Never send secrets in the ticket. The team never asks for your password or the raw value of an API key.
- Sensitive requests (revoke key, change plan) may require confirmation from the workspace owner.
Resources#
- Frequently asked questions (FAQ)
- Blog / educational content
- What's new — product changes
- Technical troubleshooting
- Status and availability
- Verify an Ingestia Academy credential
- Legal documents · Privacy · DPA · Subprocessors
Next steps: Troubleshooting · Status and availability.