Frequently asked questions

What is OpenContact?

OpenContact is a contact-routing layer between lead sources and the tools that use contact data. It keeps a canonical record, evaluates routing rules, syncs destinations, and carries suppression state across connected providers.

Does OpenContact replace my CRM or email provider?

No. It connects the tools you already use and makes the data flow between them explicit.

Which tools can I connect?

OpenContact currently has 22 configured integrations across email marketing, CRM, scheduling, data, payments, forms, and webhooks. Browse the catalog.

Can I use a tool that does not have a dedicated integration?

Yes. Custom Webhook accepts JSON with configurable email and name field paths. You can also use the project-scoped REST API.

What happens when someone unsubscribes?

OpenContact records the event on the canonical contact and can propagate suppression to the provider destinations selected by your rules. Provider retries and repeated suppression actions are de-duplicated.

Can a form re-subscribe someone who opted out?

An existing contact who previously unsubscribed is not silently re-subscribed by another form submission.

Can I test a routing rule before enabling it?

Yes. Dry-run the rule against a real or sample contact to see which conditions and destinations match and what fields would be sent. The test does not change provider data.

Can OpenContact import existing contacts?

Yes. Readable connections can import provider lists, CRM contacts, spreadsheet rows, Airtable records, Calendly invitees, Ghost members, or Stripe customers with email addresses.

Can I move a list between providers?

Yes. Direct migrations stream contacts from a selected source list into a destination list and report fetched, pushed, and failed totals. Migration does not activate ordinary sync rules or verification.

Does OpenContact verify email addresses?

Optional verification can identify disposable, role-based, public-domain, and block-list signals before rules run. Use the result as a routing condition.

Can I delete a contact?

Admins can erase a contact permanently. OpenContact also sends an erasure request to each email provider the contact was synced to and records it. Admins and editors can export all data held on a contact first.

Is there an API?

Yes. The versioned API supports contacts, lists, events, rules, webhooks, and API keys. It includes scoped permissions, idempotency, incremental reads, sandbox keys, and an OpenAPI specification.

How is usage measured?

Plans limit projects, lists per project, contacts, members per project, API rate and monthly provider syncs. Actions on OpenContact’s own lists do not count as syncs. See pricing.

Are connected provider charges included?

No. Each provider bills separately, and adding or migrating contacts can affect that provider’s subscriber limits.

How are credentials stored?

Provider credentials and webhook secrets are encrypted at rest and omitted from ordinary serialized responses. See security.

Where can I get help?

Use the help center for setup details or contact us for product and support questions.