One contact record your whole stack can share

OpenContact keeps the identity, profile, source, and subscription state of every contact in one canonical record—even when that person appears in several connected tools.

Organize your contacts · Explore sync rules

The context behind an email address

A contact can carry name, company, phone, country, tags, custom fields, consent data, first-touch source, verification results, and current subscription status.

Search by name, email, or company. Open a contact to see the profile and the timeline of events that changed it.

Status that drives behavior

OpenContact distinguishes subscribed, unsubscribed, suppressed, bounced, complained, and unknown contacts. Rules can filter on that status, and a suppressed contact is handled as a suppression downstream rather than being added back as an active subscriber.

Lists with a purpose

Use lists to organize contacts by source, campaign, lifecycle stage, or segment. A list can:

• become the audience for a sync rule;
• trigger a workflow when a contact joins;
• serve as an import, export, or migration boundary;
• keep operational groupings separate from provider-specific lists.

Every contact retains at least one list membership, so it never loses all organizational context.

Bulk operations without losing history

Add selected contacts to another list, remove them from a list, unsubscribe them in bulk, or export a selection to CSV. Changes remain part of the contact’s recorded history.

Fields that travel

Custom fields and tags can become rule conditions or map into provider-specific fields. OpenContact suggests the field and consent keys already present in your project while you build mappings.

Next steps

See contact importing · Explore reporting · Read the contact guide