Skip to app details
Back to app library
APPNEURAL APP FAMILYCommunication

Support

Bring support requests into one workflow

Handle support tickets across channels with SLAs, automations, and a knowledge base.

01 / OVERVIEW

See where it fits in your day.

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.

A LOOK INSIDEExample layout · sample content
Support requests, clearly organized
New
THIS WEEKWebsite access question
Sample taskA
In review
IN FOCUSProduct information request
Sample taskA
Resolved
REVIEWAccount help
Sample taskA
02 / CAPABILITIES

Built around the work you do.

What Support does for you.

01

Multiple ticket channels

Receive tickets from email, the help center, widgets, and the API.

02

Service workflows

Use SLAs and automations for support work.

03

Knowledge base

Keep help information in a knowledge base.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Support. What you can do depends on your access in the app.

01

Find the ticket

Open a request from one of the supported channels.

02

Review support context

Check the question, relevant knowledge, and service target.

03

Plan the next action

Use the support workflow suited to the request.

YOUR NEXT MOVE

Make Support part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE80 items
P2PARTIALLY VERIFIEDPUBLISHED
Overview

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.

A help desk for a connected domain: tickets with SLAs, a knowledge base, a help center and a help widget.

Pre-sales chat belongs to Chatbot.

Priority
P2
Portfolio
Communication
Capability
Communication
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-16T05:19:29.913Z
Semantic inventory

Every number says what it counts

80Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

6 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
ConfiguredGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

support schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

supports.appneural.com DEPLOYED

supports.appneural.com

Worker
support-catalog
Health
HEALTHY
Last deployment
2026-11-03T00:00:00.000Z
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

HEALTHYHTTP 200 · 475 ms · 2026-11-16T05:19:29.913Z
HEALTHYHTTP 200 · 486 ms · 2026-11-16T04:18:58.950Z
HEALTHYHTTP 200 · 1331 ms · 2026-11-16T03:19:09.469Z
HEALTHYHTTP 200 · 572 ms · 2026-11-16T02:18:54.942Z
HEALTHYHTTP 200 · 887 ms · 2026-11-16T01:18:58.435Z
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

CLOUDFLARENOT_CONFIGURED · 2026-11-16T05:19:31.110Z
GITHUBNOT_CONFIGURED · 2026-11-16T05:19:31.110Z
CATALOG APISUCCEEDED · 2026-11-16T05:19:31.842Z
DNSSUCCEEDED · 2026-11-16T05:19:30.624Z
GITHUBNOT_CONFIGURED · 2026-11-16T04:19:00.119Z
CLOUDFLARENOT_CONFIGURED · 2026-11-16T04:19:00.119Z
CATALOG APISUCCEEDED · 2026-11-16T04:19:00.925Z
DNSSUCCEEDED · 2026-11-16T04:18:59.636Z
CLOUDFLARENOT_CONFIGURED · 2026-11-16T03:19:10.485Z
GITHUBNOT_CONFIGURED · 2026-11-16T03:19:10.485Z
CATALOG APISUCCEEDED · 2026-11-16T03:19:11.251Z
DNSSUCCEEDED · 2026-11-16T03:19:10.070Z
GITHUBNOT_CONFIGURED · 2026-11-16T02:18:56.045Z
CLOUDFLARENOT_CONFIGURED · 2026-11-16T02:18:56.045Z
CATALOG APISUCCEEDED · 2026-11-16T02:18:56.837Z
DNSSUCCEEDED · 2026-11-16T02:18:55.593Z
GITHUBNOT_CONFIGURED · 2026-11-16T01:18:59.518Z
CLOUDFLARENOT_CONFIGURED · 2026-11-16T01:18:59.518Z
CATALOG APISUCCEEDED · 2026-11-16T01:19:00.222Z
DNSSUCCEEDED · 2026-11-16T01:18:59.031Z

Drift findings

RESOLVED · canonicalHostnameResolvesDNS · last seen 2026-11-16T05:19:30.385Z
Evidence & history

Trust record

DNS resolvesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Canonical hostname matchesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

HTTPS worksScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Production environment existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Repository existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Business owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Business owner exists.

Product owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Product owner exists.

Technical owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Technical owner exists.

Maintaining team existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Maintaining team exists.

Documentation existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Documentation exists.

Architecture documentation existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Architecture documentation exists.

Security review is currentScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Security review is current.

Data classification existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Dependencies existScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Dependencies exist.

Consumers existScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Consumers exist.

Health endpoint existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

SLA or SLO existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: SLA or SLO exists.

On-call existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: On-call exists.

Release existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Release exists.

Catalog inventory synchronizesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Infrastructure drift is clearScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Infrastructure drift is clear.

DNS resolvesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Canonical hostname matchesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

HTTPS worksScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Production environment existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Repository existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Business owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Business owner exists.

Product owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Product owner exists.

Technical owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Technical owner exists.

Maintaining team existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Maintaining team exists.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app