One profile per person — with the full relationship graph attached.
360° contact profiles with relationships, a complete activity timeline, custom fields, consent tracking, and built-in duplicate detection.
Contacts is GENECRM's relationship workbench: a searchable, filterable table backed by a full profile drawer for every person in your workspace. Contact "kind" (customer, prospect, partner, vendor, other in a generic workspace; client, prospect, COI and beneficiary once you pick the financial-services preset) and the label used for the account/household grouping are both vocabulary-driven from your industry preset — a financial-services workspace calls the grouping "Household," a generic workspace calls it "Account," a nonprofit calls it "Organization," without any code change.
360° contact profile drawer
Opening a contact surfaces everything attached to them in one slide-over: GENE intelligence summary, the relationship graph, their linked account/household, an email thread with compose-in-place, notes, enrichment data, and the full activity timeline — with a quick-log form to add a new call, email, meeting, note, or task without leaving the drawer.
- Header shows kind badge, title, company, and contact methods (email, phone, LinkedIn)
- Inline email compose and send directly from the profile
- Quick-log activity form covers note / email / call / meeting / task / SMS
Relationships graph
Contacts can be linked to one another with a typed relationship (spouse, child, parent, sibling, trustee, beneficiary, advisor, attorney, accountant, professional, referrer, employer, and more) and an optional metadata payload. The profile drawer lists every relationship the contact participates in, with a link straight to the related contact.
- Relationship types are vocabulary-validated, not free text
- Relationships are bidirectional in the API (queried by either side of the link)
- Used to power a full family/professional-network view for households
Vocabulary-driven kinds and account label
The kind filter chips, the New Contact form's kind dropdown, and the badge coloring on every row are all generated from the tenant's contact_kinds vocabulary rather than a hardcoded enum — and every place the UI would otherwise say "Account," it instead reads whatever account_label your industry preset defines.
- Contact kind badges recolor automatically per kind (customer, prospect, partner, vendor, and whatever your preset adds)
- Linked-household card label adapts to the preset ("Household", "Account", "Organization", "Family", "Customer")
Custom fields and enrichment
Every contact carries a custom_fields JSON payload validated against your workspace's custom-field schema for the contact entity, plus a system-populated enrichment block (state, derived signals) that's rendered read-only in the profile as key/value pairs. Contacts are auto-enriched at creation time.
- Custom fields are schema-validated server-side on create and update
- Enrichment runs automatically on contact creation
Consent tracking and duplicate detection
Consent state (opted-in / opted-out, per channel) is tracked per contact and checked before certain outreach actions fire, alongside GDPR-style export/forget endpoints. Separately, a duplicate-detection pass groups likely-duplicate contacts two ways — an exact match on normalized email, and a match on normalized name plus company — and offers a one-click merge that reassigns activities, tasks, relationships, custom-object records, and emails from the duplicate onto the surviving record, filling in any blank fields from the merged contact.
- Consent is tracked per channel with opted_in / opted_out status
- Duplicate groups are surfaced with the matched field explained
- Merge reassigns all linked records (activities, tasks, relationships, emails) and backfills blank fields
- Client-facing teams that need a single source of truth per person, not per deal
- Compliance-sensitive workspaces that need consent state visible before outreach
- Ops teams cleaning up duplicate records after a CSV import or integration sync
Contacts & Accounts — common questions
It's whatever your industry preset calls it. GENECRM ships eight presets — generic calls it "Account," financial services and insurance call it "Household," nonprofit calls it "Organization," education and faith call it "Family," and banking and field service call it "Customer" — and the label shows up consistently across the linked-account card, filters, and forms.
Contact kinds come from your workspace's contact_kinds vocabulary, which starts from your industry preset and can be edited by an admin — the filter chips, badges, and New Contact form all reflect whatever list is configured.
Merging reassigns activities, tasks, relationships, custom-object records, and emails from the duplicate contact onto the surviving contact, and fills in any blank fields on the survivor from the duplicate before deleting it.
Per contact, per channel — a contact can be opted in on email and opted out on SMS, for example, and outreach checks consent state before certain actions.