Unified contacts
Bring website contacts together in one record per person.
One record for every relationship
Unify website contacts, referrals, and relationships in one record per person.
Enquiries, chat visitors, form respondents, sign-ups and newsletter subscribers from every domain are read every 15 minutes and matched by email address and phone number into one contact with one timeline; fields an owner edits are never overwritten. Each contact has a referral code: people arriving through ?ref= links, a referral answer, the API or an import are linked to who brought them, and the Network page shows top referrers, upline and downline trees and a relationship graph. Contacts also hold relationships, addresses, social profiles and their company record, plus follow-ups, segments, duplicates and merge, CSV/vCard import and export, an HTTP API with per-domain keys and a Claude brief per contact. Every domain gets contact.<domain> behind its own passcode; the public inventory lists domains only.
What Contacts does for you.
Bring website contacts together in one record per person.
Match records using email addresses and phone numbers.
See who referred whom and how people are related.
A suggested path for Contacts. What you can do depends on your access in the app.
Start with a person your website has heard from.
Review the email and phone information associated with the record.
Look at referrals and connections for additional context.
Live host, inventory, governance, health checks, verification, dependencies and history.
Enquiries, chat visitors, form respondents, sign-ups and newsletter subscribers from every domain are read every 15 minutes and matched by email address and phone number into one contact with one timeline; fields an owner edits are never overwritten. Each contact has a referral code: people arriving through ?ref= links, a referral answer, the API or an import are linked to who brought them, and the Network page shows top referrers, upline and downline trees and a relationship graph. Contacts also hold relationships, addresses, social profiles and their company record, plus follow-ups, segments, duplicates and merge, CSV/vCard import and export, an HTTP API with per-domain keys and a Claude brief per contact. Every domain gets contact.<domain> behind its own passcode; the public inventory lists domains only.
Customers who buy belong to Customers; inbound form messages belong to Enquiry.
6 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
contacts.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.