Multiple ticket channels
Receive tickets from email, the help center, widgets, and the API.
Bring support requests into one workflow
Handle support tickets across channels with SLAs, automations, and a knowledge base.
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.
What Support does for you.
Receive tickets from email, the help center, widgets, and the API.
Use SLAs and automations for support work.
Keep help information in a knowledge base.
A suggested path for Support. What you can do depends on your access in the app.
Open a request from one of the supported channels.
Check the question, relevant knowledge, and service target.
Use the support workflow suited to the request.
Live host, inventory, governance, health checks, verification, dependencies and history.
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.
6 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
supports.appneural.com
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.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.