Every entry arrives withits own record
Email, calls and chats become billing entries — matched to the matter, with the source attached.
Gmail
Outlook
Zoom
Microsoft Teams
Google Meet
WhatsApp
ClioCalendarGmailOutlookZoomMicrosoft TeamsGoogle MeetWhatsAppClioCalendarReconstruction doesn't fail randomly. It fails downward.
The only bridge between work done and work billed is memory at 7pm — and memory leaks one way.
Lawyers recall the 45-minute deposition prep, not the six four-minute exchanges. Those six are the higher-value work.
We quote 28 minutes — the most conservative figure, published by a competitor.
Put your own firm's numbers in.
Change any input. Nothing is sent anywhere — this runs in your browser.
Connected by OAuth in a browser. Never installed on a device.
The billable event leaves a record on a server. Connect the channel, not the lawyer — laptop, screen and browser history stay out of it.
Threads read as they arrive, matched to a matter.
Graph subscription on the mailbox, not the desktop.
Meeting length, participants and transcript where enabled.
Calls and meetings, with the transcript when your tenant keeps one.
Calendar-linked meetings and their attendance record.
The channel clients actually use — no app on the lawyer's phone.
Not connected, and not counted. We say so rather than imply coverage.
Seven steps, and one of them is a gate.
- 1
Seen this already?
Providers re-deliver — marking an email read is enough. A message already decided stops here and costs nothing.
- 2
Resolve who, against your real client list
Identities are mirrored from Clio. An unknown sender is reported as unknown rather than attached to the nearest plausible matter.
- 3
Has this thread been filed before?
If any message in the conversation already has a matter, the rest inherit it. One conversation is never split across two matters.
- 4
Choose among that client's open matters
Knowing “can you send the signed copy over?” belongs to the Henderson lease and not the Henderson divorce is a language judgment. It is the judgment that gates this whole category.
- 5
Write the narrative a billing partner would accept
Drafted from the actual record, not from a subject line. Meetings use the best content rung available and every entry records which rung it was.
- 6
Apply your rules, not ours
Minimum increment, rounding direction, and the confidence gate are per-firm settings. We estimate effort; the firm decides how effort becomes a number.
- 7
The gate
Above your threshold: ready to release. Below it: held, with the reason and the record attached.
“I don't know” is a first-class outcome. Under-billing is invisible; over-billing is a client dispute or a bar complaint. We would rather leave money on the table than put a wrong number in front of your client.
Two architectures. Only one has to ask your partnership for permission.
Automatic timekeeping is not a new category. Almost everyone in it installs an agent on the lawyer's machine and reads the screen. That approach captures more raw activity. It also puts privileged material in front of a capture tool, reads as a gotcha to the person being measured, and still cannot see the phone.
We connect to the channel, in a browser, with the firm's consent — and see only communications a client took part in.
The honest version of the trade: a screen agent sees more of the day. We see less of the day and more of the client. Everything we file traces to a communication a client took part in — which is the only kind of time that survives invoice review anyway.
A billing product that is confidently wrong is worse than no product.
Nothing is filed on a guess
Below your confidence gate, an entry is held with its reason. It does not quietly reach Clio and it does not reach a client.
No meeting summarised from its title
Content comes from recap, then transcript, then the organiser's description, then title only — and every entry records which rung it used.
No duplicate charge, ever
Providers re-deliver. Every stage keys off provider IDs and prior decisions, because a duplicate delivery in a billing product is a duplicate charge to a client.
We won't connect a client's own mailbox
We tried it once. Every message inside looked internal and a whole conversation was silently frozen out of billing with no error. Refused now at three separate layers.
One bad payload can't drop a batch
Malformed deliveries are quarantined individually and replayed. The failure mode we design against is the invisible one.
Firms are isolated in the database
Not only in application code. One firm seeing another firm's client communication is not a bug you recover from.
Published, per seat, and every channel is in the base plan.
Mobile messaging isn't an upsell here, because it's the channel your clients actually use. Seats reconcile automatically as you invite and deactivate people.
Firms on Clio that want the evening back and the entries defensible.
Start a trialFirms with billing guidelines to enforce and a prebill cycle to run.
Start a trialLarger firms with residency requirements or a second practice management system.
Talk to usThe awkward ones first.
Seven questions partners actually ask on the first call. The answers are the same ones we'd give in the room.