One workspace without mixing client data
Agencies often manage different providers, forms, and routing logic for every client. OpenContact separates each customer journey into its own project.
Project isolation
Contacts, lists, sources, provider connections, rules, API keys, and webhook subscriptions remain scoped to one project. A credential for one client cannot access another project’s records.
Access by responsibility
Admins manage provider credentials and the team. Editors maintain contacts and automations. Developers manage APIs and outbound webhooks.
Repeat the operating model
Use the same capture → route → suppress → audit pattern while allowing each project to connect its own stack and define its own conditions.
Make handoff explainable
Activity streams, contact timelines, and rule tests give both agency operators and clients a clearer account of what the system did.