Pincite Audio is not case management

Practice management software is a system of record. It holds your matters, your contacts, your calendar, your documents, and it is where the firm's work lives.

Pincite Audio is not that, is not trying to become that, and connects to Clio on purpose narrowly. If you are evaluating it as a replacement for anything, it replaces the afternoon spent scrubbing through a recording — not the place your matters live.

Three verbs

The Clio integration does exactly three things: it authenticates you, it lets you search your matters and documents, and it fetches a file you point it at.

Everything a practice-management integration usually grows was cut rather than deferred: there is no sync engine, no picklists, and no phrase sets. Those features are how an integration becomes a second system of record that quietly disagrees with the first one, and the cheapest way not to have that problem is not to build them.

It reads; it does not write

The connection requests read access, and the code matches that request. The only POST Pincite Audio makes to Clio is the OAuth token exchange that establishes the connection in the first place. Every product operation is a GET, and there is no PUT, PATCH, or DELETE anywhere in the integration.

Stated precisely, because a technical reader will check: what is verifiable here is the scope Pincite requests plus the absence of write operations in its own code. Nothing about that arrangement asks Clio to enforce anything on your behalf.

Nothing is mirrored

When you search for a matter, that search runs against Clio, live. There is no cached copy of your matter list, no nightly import, no local index that was accurate last Tuesday.

This is the strongest form of the "not case management" argument, and it is a design consequence rather than a claim: a system with no local copy cannot present a stale one. What persists after a pull is the audio you asked for, a record of which Clio document it came from, and the document's name, which is stored encrypted the way any filename in this system is.

Per-user, and where that stops

Each person connects their own Clio account. Every call Pincite Audio makes to Clio runs under that user's own token, so Clio's own permissions decide what Clio returns, and there is no firm-wide service token that could see more of your Clio than the person using it can.

That boundary is worth drawing exactly, because it is easy to assume it extends further than it does. It governs what Clio hands over. Once a recording has been pulled, it lives in a Pincite Audio matter, and who can open it is decided by this system's own matter access — not by anything carried over from Clio. If you rely on access separation configured in your practice management system, it does not follow you here — access to a recording is a fact about this system's own records, and it has to be reasoned about here on its own terms.

Two ways in

Pulling from Clio is a convenience, not a dependency. Audio can also be uploaded directly, and both routes go through the same pipeline — same normalization, same speaker-label discipline, same coverage check, same markers where nothing came back. The artifacts differ only in recorded provenance: a pulled recording carries where it came from.

If your recordings already live in Clio, the pull saves you a download and a re-upload. If they do not, nothing is missing.