OpenContact Help Center
OpenContact sits between where your contacts come from and the tools you send with. Capture a contact once, map it correctly to the ESPs and CRMs you already use, and keep unsubscribe/bounce/complaint state synchronized everywhere — with a full audit trail.
Start here
- Getting started — connect a provider, capture your first contacts, and build a sync rule in minutes.
- Connections & integrations — the ESPs, CRMs, scheduling, and data tools you can connect.
- Sync rules — the engine that decides where each contact goes.
Core features
| Guide | What it covers |
|---|---|
| Sources | Capture contacts from forms, APIs, and lead sources |
| Contacts & lists | Your canonical contact store, lists, search, and export |
| Sync rules | Filters, destinations, fan-out vs router, suppression policy |
| Triggers | Fire rules on created, updated, unsubscribed, bounced, added-to-list |
| Suppression & compliance | Propagate unsubscribes/bounces across every provider |
| Email verification | Filter out risky emails before they sync |
| Contact enrichment | Research a contact’s name and company from its email |
| Importing contacts | Pull contacts in from a connected tool |
| List migration | Copy a list from one provider to another |
| Developer API | Read and write contacts, lists, events, and rules |
| Outbound webhooks | Get notified when events happen |
| Reports & activity | See what synced, when, and why |
| Team & roles | Invite teammates with the right access |
Build with OpenContact
Wiring OpenContact into your own app? Start with the integration guides — copy-paste code for sending contacts and verifying webhooks (Laravel available now).
Integrations
Browse every tool you can connect on the Integrations index.
Still stuck?
Send us your project ID and what you saw. Contact support.