Contact support
Contact Chatevo support when dashboard troubleshooting does not resolve your issue, you need plan upgrades, or you have compliance requests.
Contact channels
Section titled “Contact channels”| Channel | Address | Best for |
|---|---|---|
| support@chatevo.ai | All issues; include details below | |
| Dashboard | Help → Contact support | Attaches org context automatically |
| Enterprise | Named account manager | SLA-backed incidents, DPA, custom limits |
Support hours: Monday–Friday, 9:00–18:00 UTC. Enterprise SLAs define 24/7 coverage where contracted.
Before you write
Section titled “Before you write”Include as much as applies — it shortens resolution time:
| Field | Example |
|---|---|
| Organization name | Acme Corp |
| Admin email | admin@acme.com |
| Deployment / assistant ID | dep_abc123, asst_7xK9mN2p |
| Page URL or API endpoint | https://www.acme.com/support |
| Timestamp (UTC) | 2026-07-16T14:22:00Z |
| Error message or HTTP status | 403 domain_not_allowed |
| Steps to reproduce | 1. Open widget 2. Send “track order” 3. See error |
| Screenshots | Network tab, console errors |
Issue-specific guides
Section titled “Issue-specific guides”Try these docs first — support will ask the same diagnostic questions:
| Issue | Guide |
|---|---|
| Widget missing | Widget not loading |
| 403 on widget | Domain not allowed |
| Tool auth failure | Tool 401/403 |
| Poor answers | Empty answers |
| 429 errors | Rate limit |
Severity levels
Section titled “Severity levels”| Level | Definition | Example |
|---|---|---|
| P1 — Critical | Production widget or API down for all users | Every visitor sees errors |
| P2 — Major | Significant degradation | Tools failing; partial outage |
| P3 — Minor | Workaround exists | Styling issue, single doc not indexing |
| P4 — Question | How-to, billing, feature request | DPA request, plan comparison |
Mark P1/P2 clearly in the subject line: P1 — Widget down on production.
Security issues
Section titled “Security issues”Report vulnerabilities to security@chatevo.ai (not public issues). Include reproduction steps; we acknowledge within 2 business days.
Do not post API keys, JWT secrets, or webhook signing secrets in tickets — rotate if accidentally exposed.
Compliance requests
Section titled “Compliance requests”| Request | Contact |
|---|---|
| GDPR export/deletion help | support@chatevo.ai |
| DPA execution | support@chatevo.ai (see DPA) |
| Subprocessor list | Legal / subprocessors |