Skip to content

ClientVerse Documentation

ClientVerse is a Salesforce-native relationship and business-development CRM for law firms. It answers the four questions a firm asks constantly: who do we know, what have we done, what are we pursuing, and how do we stay organized about it.

This site documents ClientVerse Core 1.1.7 and ClientVerse Modules 0.4.0.

Start where you are

  • I use ClientVerse day to day

    Attorneys, business development, marketing, relationship managers.

    User Guide — task-oriented, no data model knowledge needed.

  • I run a ClientVerse org

    Administrators, IT, CRM owners.

    Admin Guide — access, configuration, upgrades. Troubleshooting — organized by symptom.

  • I am deploying ClientVerse

    Implementation teams and consultants.

    Implementation Guide — install order, migration, go-live.

  • What changed?

    Release Notes — current release, and the history behind it.

Two editions

ClientVerse ships as two packages, and which parts of this site apply to you depends on what your firm has installed.

Edition Who has it What it is
ClientVerse Core Every client The foundational CRM — the apps, the data model, and the relationship and BD workflows.
ClientVerse Modules 🧩 Optional add-on Premium capabilities on top of Core: Dispatch (notifications and digests), Whitespace (revenue-opportunity scoring), and — new and off by default — AI and Analytics.

Anything requiring Modules is marked with a 🧩 badge throughout. If your firm is on Core only, you won't see those features, and that is expected.

Going deeper

  • Feature guides — one capability at a time: what it is, who it's for, how it works.
  • Product guides — the by-app view: what each ClientVerse app is for and who lives in it.
  • Training — the six-class curriculum, with objectives and click-paths.
  • Configuration reference — the object, application and permission-set inventory.
  • Glossary — Experience, Matter, ERM, Connection, Classification, and the rest.

Facts on this site — versions, counts, object and permission-set names — are generated from the released package rather than written from memory. If a page disagrees with the package facts, the facts are correct and the page is a bug.