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
InventoryACTIVE1 items
P2VERIFIEDPUBLISHED
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-18 14:03:01
Semantic inventory

Every number says what it counts

1Catalog 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

support.appneurox.com DEPLOYED

support.appneurox.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

No health checks have been recorded.
Security

Review posture

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

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

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

App libraryOpen app