customers.appneural.com
CUSTOMERS
Every customer of every website in one CRM, with a Customer Card that gives 20–40% off and grows through friend referrals.
Purpose and boundaries
One timeline per person: enquiries, chatbot conversations, newsletter subscriptions and form responses from the other APPNEURAL catalogs arrive by themselves every 10 minutes, and the same person is matched by email, then by phone, so nobody shows up twice. A CRM with stages, tags, custom fields, notes, calls, meetings, tasks, a drag-and-drop deals pipeline, duplicates and merge, CSV import and export, ready-made lists and an engagement score. An AI brief (Claude) reads the whole history and writes who they are, what they want, the next step and a follow-up email. The Customer Card gives every customer a discount on every purchase (Silver 20%, Gold 30%, Platinum 40% by default, per domain) and a friend link: friends get a one-time discount, and the card moves up a tier as they use it. customers.js (one script tag) captures website forms and checks card codes at checkout. customers.appneural.com holds every domain; customer.<domain> holds one domain's customers only, behind its own passcode.
Leads before they are customers belong to Enquiry; payments belong to Payments.
- Priority
- P2
- Portfolio
- Customers & Sales
- Capability
- Customers & Sales
- Technical owner
- Not configured
- Runtime
- Cloudflare Workers / OpenNext
- Last verified
- 2026-11-08T06:19:05.614Z
Every number says what it counts
Governance evidence required
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
customer schema v1
Where it runs
customers.appneural.com
- Worker
- customer-catalog
- Health
- HEALTHY
- Last deployment
- 2026-11-04T02:18:40.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.
Configure or repair: Repository exists.
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.
Configure or repair: Repository exists.
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.