supports.appneural.com
SUPPORTS
A help desk for every website: tickets from email, the help center, the widget and the API, with SLAs, automations and a knowledge base.
Purpose and boundaries
Tickets numbered per domain arrive by email (support@<domain> through Email Routing, threaded by Message-ID and [#n]), the help-center request form, a one-tag website widget, the API and the chatbot handover. An inbox with views, search and bulk changes; a ticket page with internal notes, history, macros and replies emailed in the customer's thread. First-reply and solve SLAs per priority in business hours, automations on create, reply and status change, round-robin assignment, acknowledgements, satisfaction surveys, auto-close and pending reminders. A knowledge base shown in the help center and the widget. Each domain has its help center, customer ticket pages and its own desk at support.<domain>, in its brand, for the owner and team members. Claude triages new tickets, drafts and rewrites replies, summarizes threads, writes articles from solved tickets and reads the reports.
Pre-sales chat belongs to Chatbot.
- Priority
- P2
- Portfolio
- Communication & Engagement
- Capability
- Communication & Engagement
- Technical owner
- Not configured
- Runtime
- Cloudflare Workers / OpenNext
- Last verified
- 2026-11-08T06:19:47.876Z
Every number says what it counts
Governance evidence required
6 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
support schema v1
Where it runs
supports.appneural.com
- Worker
- support-catalog
- Health
- HEALTHY
- Last deployment
- 2026-11-03T00:00:00.000Z
Confirmed infrastructure only
Technical context
Documentation
Registered relationships
Checks and verification
Review posture
GitHub · Cloudflare · DNS · catalog APIs
Drift findings
Trust record
No remediation required.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Human-reviewed drafts
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.