Contact data needs a clear route
A contact fills in a form, books a call, joins a CRM, buys, and later unsubscribes. Each tool sees one step. Someone still has to reconcile the lists and make sure the opt-out arrived everywhere.
OpenContact is the layer that does that. It keeps one record per contact, applies rules you can read, and carries suppression across tools. It does not replace your CRM or email platform.
What we believe
- Capture once. A contact should not be retyped for every tool.
- Routing should be readable. You can see a rule’s trigger, conditions and destinations, and test it first.
- An unsubscribe belongs to the person. It applies everywhere you send email, not only in the tool where it happened.
- You should be able to switch providers. Moving lists should not mean rebuilding the pipeline.
- Every action is traceable. Source, rule, payload and result are logged per contact.
- Developers get real primitives. Scoped keys, idempotency, sandbox keys, signed webhooks and OpenAPI.
Who uses it
- SaaS teams linking signups, lifecycle email and sales.
- Agencies keeping client projects and credentials separate.
- Newsletter operators working across audience platforms.
- Revenue teams linking forms, meetings, payments and CRM follow-up.
- Developers who want a contact and event layer behind their app.