Does Ajax Integrate with RingCentral? How to Get Started with RingCentral on Ajax
Every hour a lawyer works but doesn't bill is revenue that disappears. Phone calls leak this way constantly. The 22-minute call with a client gets billed for 22 minutes, but the contract you pulled up during the call, the email reply you drafted two hours later, and the case note you typed mid-call almost never make it onto the invoice.
We built Ajax's RingCentral capture to close that gap. Ajax watches the work as it happens across the RingCentral app and everything you touch around the call, 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 unified communications platform.
Ajax's privacy architecture is built for the sensitivity of legal work, including the call notes, voicemail transcripts, and client documents that pass through a typical RingCentral session. 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 RingCentral?
Yes. Ajax captures RingCentral 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 around the call: the contact name, the duration, the call notes textbox, the voicemail transcript when your RingCentral tier provides one, SMS threads, team chat, and the AI Notes summary if you have that turned on. It also reads everything else open at the same time, including the contract you pulled up while the client was talking, the email you replied to mid-call, and the calendar block you set up afterward. On the API side, Ajax pulls RingCentral call metadata (duration, contact) as a secondary signal, which keeps mobile calls and any call you take without the RingCentral window in focus from disappearing from your entries.
One piece of honesty up front. Ajax doesn't capture the audio of the call itself. The narrative is built from the on-screen content (notes, transcripts, AI Notes summary, the documents alongside the call) and the API metadata. The audio stays between you and the person on the other end of the line.
Ajax meshes the two streams together. The desktop gives content and context; the API gives mobile coverage and call metadata. The drafted time entry comes back describing the actual piece of billable work, not just a line item that a call happened.
Most tools that advertise a "RingCentral integration" in legal tech are click-to-dial buttons or call-log syncs into a practice management system. They tell you the call happened and how long it was. They don't tell you what work happened around the call, which is where most of the billable time leaks. Ajax catches both.
A few practical implications of capturing RingCentral this way:
It works across the RingCentral desktop app, the web app, the RingCentral chat window, and the RingCentral mobile app
It captures the call together with the document, contract, or email you worked on for the same matter, so the entry reads as one coherent piece of work
It captures voicemails you listened to, SMS threads you read, and team chats you scanned, even when you didn't reply
How Ajax captures your RingCentral work, step by step
Four things happen between the moment your RingCentral call starts and the moment a time entry shows up for your review.
Ajax sees what's on your screen
While you take a RingCentral call, type a case note in the call notes panel, scan a voicemail transcript, or read an SMS thread, Ajax reads the same content you're reading. Pixel by pixel, in real time. It picks up the contact name, the phone number, the duration, the notes you type, and any transcript or AI summary RingCentral produces.
It also picks up what you have open on the rest of your screen during the call, including the contract you pulled up while the client was talking, the email you replied to mid-call, and the calendar entry you made afterward. All of it on the same matter, captured as one piece of work.
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 "Call with client re: discovery; reviewed responses; emailed OC," that's what your Ajax-drafted entries look like. If you usually write "Telephone conference with client regarding discovery responses, followed by review of draft responses and email to opposing counsel," 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 case (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 call notes, the AI summary, the SMS thread, and the docs you have open during the call.
Ajax builds matter attribution from that content. When it can't confidently attribute a call to a matter, it flags the draft entry for you to assign, then learns from the correction. From there, Ajax handles the next call from the same number about the same case automatically.
Related work gets grouped into one entry
A single piece of billable phone-adjacent work is usually a 22-minute call, plus the contract you reviewed in the middle of it, plus the ten-minute follow-up email two hours later. As individual line items, that's three entries scattered across the day. As one piece of work, it's a single entry of about 45 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. The call summary and any notes you typed during the call travel with the entry as part of the narrative, so what shows up on the invoice reads like a lawyer wrote it.
How to get started with RingCentral on Ajax
There's nothing for you to install inside RingCentral. 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, drawn from a couple of days of real RingCentral and screen activity, 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. About 97% of firms that pilot Ajax move into a subscription afterward. The fastest way to see whether Ajax's RingCentral 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 30 minutes a day of previously unlogged phone-adjacent work, the firm captures an additional $16,500 a month. That's a hair under $200,000 a year, and it's a conservative estimate. Thirty minutes a day is well below what most firms find sitting around their phone activity 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. 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 RingCentral
Does Ajax record my client calls?
No. Ajax doesn't capture audio. We capture what's visible on your screen, which includes the RingCentral call window, the call notes textbox, voicemail transcripts, and AI Notes summaries if RingCentral generates them. Your Ajax is yours, and nobody else at the firm can see what's in it, not even managing partners.
Does Ajax work with RingCentral on mobile?
Yes. Mobile calls are captured through the RingCentral API as a secondary signal, even though Ajax's desktop screen layer doesn't run on the phone. A call you take on the RingCentral mobile app while you're on the train still shows up 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 matter documents were open on your laptop, but the call itself isn't lost.
What if I don't use RingCentral AI Notes or RingSense?
Ajax still captures the on-screen call metadata: contact name (if it's in your RingCentral directory), duration, time, and any notes you type into the call notes panel. It also picks up everything else you did on screen during the call. The AI Notes transcript makes the first-try matter attribution more confident, especially for matters Ajax hasn't seen before.
Will Ajax replace RingCentral or my practice management system?
No. Ajax sits between them. You keep using RingCentral exactly the way you do today. The drafted entries go into your PMS for billing.
What about voicemails I never call back?
Those still count. If you listened to the voicemail, scanned the transcript, or read the SMS that came in with it, Ajax saw that work happen and turns it into a draft entry. You're billing for the time you spent assessing what the caller wanted, even if you decided no response was needed.
What doesn't Ajax capture?
Anything that never touches a screen. The audio of the call itself. In-person conversations. Handwritten notes from a hallway chat with a partner. Pen-and-paper work is a blind spot for any screen-based tool, ours included.
Final thoughts
Phone-adjacent work is where the most billable time hides, because the call duration is the only part anyone remembers to log. The contract you reviewed during the call, the email reply two hours later, and the case note you typed while the client was still on the line all stay invisible unless someone notices.
Ajax catches that work because the desktop is always watching the content of your screen, and because the matter context comes from the call and the documents around it. If you want to see what a week of your own RingCentral activity looks like as time entries, start a trial for $100 or book a demo.
