Avocet CRM for RevOps
RevOps uses Avocet CRM because its data quality does not depend on rep compliance: records are assembled from email and calendar, every field carries its provenance, deduplication proposes rather than assumes, and every merge is reversible and audited.
How does deduplication work, and can I trust it?
Deterministic rules run first — normalised email, then email domain plus name similarity, then company relationship — and every candidate carries a confidence score. Only matches above a threshold we can defend in front of a customer merge automatically; everything else waits in a review queue for a person.
Merges are reversible and audited. Nothing uncertain merges silently, because one wrong merge destroys trust in the entire import and no explanation of the algorithm gets that trust back.
Can I tell which fields a human entered and which the AI inferred?
Yes. Every record carries a provenance value — human, imported, AI-inferred or AI-generated — and the AI never silently overwrites a human-entered value. Insights can be rejected in one click, and the rejection is stored.
That last part is the one people underestimate. A system that cannot be told it is wrong accumulates errors invisibly until someone stops believing all of it at once.
What happens when an import partially fails?
You get a per-record result. Every row is reported as created, updated, skipped or failed, with the reason — not a summary count that leaves you to guess which 40 of 12,000 rows did not land.
Imports run as background jobs with durable steps and retries, so a 50,000-row file with AI enrichment does not depend on an HTTP request staying open.
Is there a real audit trail?
Yes, and it is append-only at the database permission level rather than by convention. Every privileged write records its actor in the same transaction as the change, so a mutation that exists without its audit entry is not a state the database can reach.
What access controls are there?
Five roles — owner, admin, manager, sales rep, viewer — resolved to capabilities in exactly one module, so there is one place to read and one place to change what a role can do. Viewer seats are free and unlimited.
Role checks in the interface are convenience only. The enforcing copies are a capability assertion in the domain layer and a row-level security policy in the database, and the read-only case is tested at the SQL level in continuous integration.