Features
Sales & CRM
Contacts with their origin and their consent, tags, lists, deals, segmentation, ticketing.
Business Deals + Tickets
Kanban pipeline (won/lost + metrics) and tickets.
E-commerce + Catalog
Product catalog, cart/order → WhatsApp.
Integrations + HubSpot
Deal sync to HubSpot, signed webhooks to CRM/Zapier (new consent, won deal).
A CRM knows who your contacts are. OptinProof also knows what you can do with them.
Contact and origin
Every list that comes in carries where it came from, and keeps it: the contact brings its history along.
Consent and evidence
For every channel, permission does not come from a checkbox. Native proof is the signature collected with your form. Evidence from an export stays the state declared by the supplier, apart from that proof.
Campaigns, automations, channels
Campaigns on WhatsApp, email and SMS and automations start from here, and reach only people with permission for that channel.
Traceability
Entries, withdrawals and sends stay on record: when someone asks you about a message, you have the trace of the consent it started from.
Not whether you can reach them: why not
One badge per channel, with the reason
Next to every person there is a row of badges, one per channel, and each one says what is missing: you do not have the contact detail, you do not have permission, or they told you to stop. Those are three different things and each one is fixed a different way. And where we do not know, we say so instead of guessing.
A stop switches off the channel, not everything
Someone who leaves WhatsApp leaves WhatsApp: if they had also left you their email or SMS consent, those stay alive. Permission is per channel, and the exit is recorded with the date, the channel it came from and a receipt with a code that can be quoted; the contact detail stays where it is, and what changes is the permission.
The contacts you already have are not thrown away
Bring the history, not just the list
From the exports of Mailchimp, HubSpot, your online shop or any CSV, OptinProof reads the traces the file carries: when people signed up, whether they confirmed, whether they unsubscribed. It keeps those states apart from native proof. The full diagnosis, with the legitimate paths, is in development.
An import is not proof
An acquired contact is not a proven consent. The Forensic Engine does not invent what is missing and does not open sends on its own: evidence stays evidence, and full proof is born when the person signs your form.
Ready to start
Your brand deserves a flawless channel
Tell us how you work and sign a real consent on the application page. We review every business: access comes only with an invitation. You can try the demo in the meantime.