Does Ajax Integrate with Dialpad? How to Get Started with Dialpad on Ajax
Phone time is the work lawyers bill for least. A quick check-in with a client between meetings, an eight-minute call with opposing counsel about a scheduling conflict, a conference-call status update where nobody took notes. None of it feels worth stopping to log, and by the time the day is over, half of it is gone.
We built Ajax's Dialpad capture to close that gap. Ajax watches what happens on your screen during a Dialpad call, reads the live transcript Dialpad's AI generates, drafts a time entry in your voice, attributes it to the right matter, and pushes it to your practice management system. You don't start a timer and you don't reconstruct anything at the end of the day.
What is Ajax?
Ajax is an AI-native timekeeping tool built for lawyers. It runs as a desktop application that reads your screen in real time and automatically drafts time entries across every application you use, including your phone system.
Ajax's privacy architecture is built for the sensitivity of legal work, including call transcripts, contact cards, and the matter documents on screen alongside a privileged conversation. Screen content is processed, used to generate a draft time entry, and then automatically deleted. 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. 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 Dialpad?
Yes. Ajax captures Dialpad 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 the call in real time: the contact card showing who's on the line, the duration counter, the live Dialpad AI transcript scrolling past, and everything else on screen alongside it (the contract you pulled up, the email you scanned to confirm a date, the follow-up you typed afterward). On the API side, Ajax pulls Dialpad call metadata (duration, contact) as a secondary signal, which keeps mobile calls and any call you take when the Dialpad window isn't visible 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 the actual piece of billable work, not just a line item that a call happened.
Most legal-tech tools that advertise a "phone integration" stop at call-log metadata: who you called, the number you dialed, the duration, the timestamp. That gives you "Call to (212) 555-0142, 11 minutes" and not much else. Ajax pairs the screen-level content with the metadata, so the narrative describes what the call was actually about.
A few practical implications of capturing Dialpad this way:
It works whether you take calls in the Dialpad desktop app, the Dialpad web app, a Dialpad-connected browser tab, or the Dialpad mobile app
It captures the call together with the contract you pulled up mid-call, the email you scanned to confirm a date, and the follow-up you sent right after
It captures calls you take on a Dialpad-paired desk handset, as long as Dialpad's desktop window is open
How Ajax captures your Dialpad calls, step by step
Four things happen between the moment a 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 a Dialpad call, Ajax is reading the same content you're reading, pixel by pixel, in real time. It picks up the contact card with the caller's name, the dialed number, the call duration counter, and the Dialpad AI transcript scrolling down the screen as the conversation happens. Everything else on screen during the call comes with it: the matter document you opened, the email thread you scanned, the case management page you pulled up to check a deadline.
A draft entry lands in your voice
About 45 seconds after the call ends, 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 "Telephone conference with opposing counsel re: discovery dispute and meet-and-confer scheduling," that's what your Ajax-drafted call entries look like. If you usually write "TC w/ OC re depo schedule," that's what they look like.
Ajax attributes the call to a matter
This is the part most phone-tracking tools get wrong. Matter attribution can't come from your CRM alone, because most of the people relevant to a call (judges, opposing counsel, peripheral parties, a co-defendant's paralegal, the kids in a custody case) aren't in it. Their names live in the transcript and on the contact card.
Ajax builds matter attribution from the content of the call itself. 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, the next call from the same opposing counsel about the same case lands on the right matter automatically.
Related work gets grouped into one entry
A single piece of billable matter work is usually one or two phone calls, plus the email confirming the call time, plus the document you pulled up mid-call, plus the follow-up email summarizing what was agreed. As individual line items, that's five entries to wade through. As one piece of work, it's a single entry of about ninety 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 calls flow 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 summary, including the transcript, into the right matter folder in your PMS or document management system. So the entry shows up where you bill, and the call record shows up where the case lives, with no dragging or copy-paste in between.
How to get started with Dialpad on Ajax
There's nothing for you to install inside Dialpad. 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
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)
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
A note on the word customize. 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. The fastest way to see whether Dialpad 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 work, the firm captures an additional $13,750 a month. That's about $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 logs when they look closely.
Across the firms we work with, the average is about 12% more billable hours captured once Ajax is in place. The lift comes from the small, easy-to-miss work the desktop sees and a manual timer never would.
One honest caveat. These projections assume the recovered time is billable and gets collected. 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 Dialpad
Does Ajax read my personal Dialpad calls?
Two parts to the answer. On the API side, Ajax only sees the Dialpad account you connect, so a personal Dialpad 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 Dialpad on mobile?
Yes. Mobile calls are captured through the Dialpad API as a secondary signal, even though Ajax's desktop screen layer doesn't run on the phone. A call you take on the Dialpad mobile app at lunch 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 I use a Dialpad-connected desk phone?
Yes, as long as the Dialpad desktop or web app is open on your computer when the call comes in. Dialpad's app usually pops up automatically with the contact card and live transcript, which is the surface Ajax reads.
Will Ajax replace Dialpad or my practice management system?
No. Ajax sits between them. You keep using Dialpad the way you already do. The drafted entries go into your PMS for billing.
What doesn't Ajax capture from a call?
Anything that never appears on screen. A call where you closed the Dialpad window, walked away from your desk, and took handwritten notes will produce a thinner entry. Ajax sees the call event but loses the substance of what was said. Pen-and-paper work is a blind spot for any screen-based tool, ours included.
Final thoughts
Most billable phone work is small. A clarification before a deposition, a callback you didn't plan for, a five-minute check-in with a client between hearings. That's exactly why it leaks. Nobody stops to log a five-minute call, and by the time the week is over, the five-minute calls have added up to half a day nobody got paid for.
Ajax catches that work because the desktop is always watching the content of your screen, and because the Dialpad AI transcript carries the substance of the conversation. You get an entry that describes what you did with that ninety minutes on the phone. If you want to see what a week of your own Dialpad calls looks like as time entries,start a trial for $100 or book a demo.
