Does Ajax Integrate with Zoom Phone? How to Get Started with Zoom Phone on Ajax
Phone time is the single largest unbilled category in most law firms, and it shows up as the five-minute call between meetings, the quick check-in with a client before a hearing, or the seventeen-minute conversation with opposing counsel that gets reconstructed at the end of the day as "TC w/ OC, .25." None of it feels worth stopping to log, and almost none of it bills for what it was actually worth.
We built Ajax's Zoom Phone capture to close that gap. Ajax watches the call as it happens in your Zoom desktop client, reads the AI Companion call summary once it appears, drafts a time entry in your voice, attributes it to the right matter, and pushes the entry to your practice management system. You don't start a timer, and you don't try to reconstruct what was said at five o'clock.
What is Ajax?
Ajax is an AI-native timekeeping tool built for lawyers. It runs as a desktop application that reads your screen across email, phone, chat, and calendar, then automatically drafts time entries in your voice across every application you use.
Ajax's privacy architecture is built around a few specific commitments worth covering up front. Screen content is processed, used to generate a draft time entry, and then automatically deleted on a rolling basis, and we don't use your data to train our models.
Our infrastructure providers (including the AI providers underneath us) are contractually prohibited from retaining or training on anything that passes through. Ajax is SOC compliant, and every lawyer's Ajax is an individual silo, so nobody at your firm can see your activity, not even managing partners.
Does Ajax integrate with Zoom Phone?
Yes. Ajax captures Zoom Phone on two channels at once, and the combination is what makes the time entries actually good.
On the desktop, Ajax reads what's on your screen during and after the call in real time: the contact card showing who's on the other end, the dialed number or caller ID, the document you pulled up to reference mid-conversation, the email you forwarded to your client while the call was happening, and the Zoom AI Companion summary panel as soon as it posts in the Workplace app. On the API side, Ajax pulls Zoom call metadata (duration, contact) as a secondary signal, which keeps mobile calls and any call you take without the Zoom window in focus from disappearing from your entries.
Ajax meshes the two streams together. The desktop gives content and context. The API gives mobile coverage and the call's hard metadata. The drafted time entry comes back describing what was discussed and what was agreed instead of a one-line "11-minute call to 212-555-0142."
Most tools that advertise a "Zoom integration" stop at call-log metadata (dialed number, duration, timestamp). Ajax pairs that metadata with the screen-level content (the AI Companion summary, the contact card, the matter-relevant document open in another window), so the narrative describes the work, not just that a call happened.
A few practical implications of capturing Zoom Phone this way:
It works no matter how you place the call (the Zoom desktop app, the Zoom web app, Zoom in Chrome, a Zoom-paired desk phone with the Zoom window open, or the Zoom mobile app)
It captures the call together with the email that confirmed it, the contract you reviewed during it, and the follow-up message you sent right after, so the entry reads as one coherent piece of work
It captures calls where Zoom AI Companion isn't producing a summary, too, though the narrative is thinner without one
One quick clarification, because the keyword brings people here who mean different things. This piece is about Zoom Phone, Zoom's cloud-based phone system for voice calls. Zoom Meetings video sessions are captured by the same mechanism, since the meeting transcript and AI Companion summary are on-screen content like everything else. We've covered the video-meeting case in its own write-up.
How Ajax captures your Zoom Phone calls, step by step
Four things happen between the moment a Zoom Phone call connects and the moment a time entry shows up for your review.
Ajax sees what's on your screen during the call
While you're on the call, Ajax is reading the same content you're seeing, pixel by pixel in real time. It picks up the contact card showing who's on the other end, the dialed number or caller ID, the document you pulled up to reference mid-conversation, the calendar event you confirmed, and the email you forwarded to your client while the call was happening. Once the call ends, Ajax also reads the Zoom AI Companion summary panel as soon as it posts in the Workplace app.
A draft entry lands in your voice
About 45 seconds after the call wraps, Ajax produces a draft entry. The narrative is written in the style of your prior time entries, which we ingest from your practice management system during onboarding. If you usually write "Tel. conf. with opposing counsel re: deposition scheduling and exchange of expert reports," that's what your Ajax-drafted entries look like. If you usually write "TC w/ OC re depo + experts," that's what they look like.
When Zoom AI Companion posts its call summary, that summary becomes the substance of the narrative. The dates, names, key discussion points, and action items it surfaces all feed into the draft. Ajax doesn't quote the summary verbatim. It reads the content, infers what was billable, and writes it the way you would.
Ajax attributes the call to a matter
This is the part most call-tracking tools get wrong. Matter attribution can't come from your CRM alone, because most of the people relevant to a case (judges, opposing counsel, expert witnesses, the paralegal at the firm across town who keeps emailing about a deposition date) aren't in it. Those names show up on the contact card or in the AI Companion summary that posts after the call.
Ajax builds matter attribution from the on-screen content of the call. When it can't confidently attribute a call to a matter, it flags the draft entry for you to assign, then it learns from the correction. From there, Ajax handles the next call from the same number on the same case automatically.
Related work gets grouped into one entry
A single piece of billable call work is usually one or two calls plus the email that confirmed the call time, plus the document you reviewed in the middle, plus the follow-up message you sent right after. As individual line items, that's five entries to wade through. As one piece of work, it's a single entry of about an hour and ten minutes.
Ajax groups intelligently across the day. You can configure whether you want block billing or itemized entries, depending on your client's billing guidelines.
What Ajax does with the call once it's captured
Captured work flows back into the system where your billing happens.
When you release an entry from Ajax, it appears in your practice management system as a time entry, ready for invoicing. We sync in both directions with Clio, MyCase, PracticePanther, SurePoint, Centerbase, Filevine, and Actionstep, and we support most other billing systems. If you edit the entry in your PMS afterward, the edit reflects in Ajax. If you add a new matter, Ajax picks it up automatically.
There's a second flow worth knowing about. Once Ajax has attributed a call to a matter, it can file the call record itself (the AI Companion summary, when it posts) into the right matter folder in your PMS or document management system. The entry shows up where you bill, and the call record shows up where the case lives, with no copy-paste in between.
How to get started with Zoom Phone on Ajax
There's nothing for you to install inside Zoom. The setup happens at the desktop level, and we handle the technical work on our end.
A typical onboarding looks like this:
We install the Ajax desktop app on every team member's machine, alongside their existing Zoom desktop client
We connect Ajax to your practice management system and pull in your matters, billing codes, and prior entries
We customize Ajax's settings to your firm's billing guidelines (UTBMS codes, client-specific narrative rules, grouping preferences, how you handle confidential calls)
Ajax runs silently in the background for about two days before your kickoff
On day one, every attorney sees real time entries already waiting for them, written in their voice, including the calls from the prior 48 hours
A note on the word customize here is that we don't train models on your data, we configure Ajax's output settings based on your firm's existing patterns. That distinction matters for security positioning, and it's the reason we can integrate with firms that handle cases for six of the eight money center banks.
Pricing starts with a flat $100 trial fee. Ongoing pricing depends on firm size, and you don't pay anything ongoing unless the trial returns ROI you can see in your own numbers. About 97% of firms that pilot Ajax move into a subscription afterward. The fastest way to see whether Zoom Phone capture is worth it for your firm is to run the trial against a week of real call work.
What this looks like in recovered revenue
A worked example for a five-attorney firm averaging $300 an hour: if each attorney recovers 25 minutes a day of previously unlogged call time, the firm captures an additional $13,750 a month. That's roughly $165,000 a year, and it's a conservative estimate. Twenty-five minutes a day is well below what most firms find sitting in their call history when they look closely.
Peakstone Law reported one attorney increasing her billable hours by 50 a month after switching to Ajax. Amy Robinson tracked 63% more billable hours over her first six months on Ajax, which she reports translated to over $350,000 in increased annual revenue.
One honest caveat here is that these projections assume the recovered time is billable and gets collected, and some of it won't be. Even at a 50% collection rate on what Ajax surfaces, the math still works for most firms.
Common questions about Ajax and Zoom Phone
Does Ajax read my personal Zoom Phone calls?
Two parts to the answer. On the API side, Ajax only sees the Zoom account you connect, so a personal Zoom number that isn't connected isn't visible to Ajax. On the desktop side, the pause button stops screen capture when you switch to a personal call.
Either way, your Ajax is yours. Nobody at the firm can see your activity, not even managing partners. Screen content is processed and then deleted on a rolling basis, and the AI providers underneath us are contractually prohibited from retaining or training on anything we send through.
Does Ajax work with Zoom Phone on mobile?
Yes. Mobile calls are captured through the Zoom API as a secondary signal, even though Ajax's desktop screen layer doesn't run on the phone. A long call from the train still lands in your draft entries with the right contact and the right duration, and gets meshed with whatever desktop work the same matter generates later in the day. The substance is thinner than a call where you also had matter documents open on your laptop, but the call itself isn't lost.
Does Ajax work if my firm uses a Zoom-paired desk phone?
Yes, as long as the Zoom desktop window is open. The window usually pops up automatically when a call comes in, and the AI Companion panel populates from the same call, so Ajax sees everything it needs to write a substantive entry.
Will Ajax replace Zoom Phone or my practice management system?
No, Ajax sits alongside both, and you keep using Zoom Phone the way you already do while the drafted entries flow into your PMS for billing.
What about calls where I never open a document or look at the Zoom window?
The call event is captured, but the narrative is thinner. The richer the on-screen signal (AI Companion summary, related doc on screen, contact card), the more substantive the time entry. A blind call with the Zoom window minimized and no AI Companion summary produces something closer to a stub entry that you can fill in by hand.
Does Ajax also capture Zoom Meetings video calls?
It's the same mechanism on a different surface, where the transcript and AI Companion summary from a video meeting are on-screen content, so they're captured the same way as a Zoom Phone call. We've covered the video-meeting case in its own article.
Final thoughts
Most billable phone work is small, like a reply call here, a five-minute clarification before lunch, or a quick co-counsel sync between hearings, and that's exactly why it leaks. Nobody stops to log a four-minute task, and by the time the week is over, the four-minute tasks have added up to half a day nobody got paid for.
Ajax catches that work because the desktop is always watching the Zoom call window, and because the AI Companion summary is doing half the work of writing the time entry for you. If you want to see what a week of your own Zoom Phone calls looks like as time entries,start a trial for $100 or book a demo.
