Does Ajax Integrate with VXT? How to Get Your IT Team to Enable VXT on Ajax
The phone is one of the highest-value billable surfaces in any law firm, and one of the easiest to lose track of. VXT already handles part of the problem. It captures the duration of the call and pushes a time entry to your practice management system after you hang up.
The minutes around the call are the ones that leak. The prep doc you reviewed in the ten minutes before dialing, the case law you skimmed in another tab while opposing counsel was talking, the follow-up email you wrote ninety seconds after the line went dead. None of it lands in the VXT entry, and most of it never gets billed.
We built Ajax's desktop capture to close that gap. Ajax watches the work happening around your VXT calls, drafts a time entry in your voice, attributes it to the right matter, and pushes it to your practice management system. The second half of this article walks through what your IT team needs to know to enable it.
What is Ajax?
Ajax is an AI-native timekeeping tool 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. Phone systems, email clients, document tools, browsers, calendars. If it lives on your screen, Ajax sees it.
Ajax's privacy architecture is built for the sensitivity of legal work, including matter files, client communications, and the work happening on screen during privileged calls. Screen content is processed, used to draft your time entry, and then deleted on a rolling basis. 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 VXT?
Yes. The way we do it is worth understanding before you start.
There is no Ajax-side plugin to install inside VXT, and Ajax doesn't pull data from VXT through a VXT-side API. The way the two tools coexist is simpler than that: VXT keeps doing what VXT does (the call, the recording, the post-call time entry pushed to your PMS), and Ajax watches the screen and groups everything around it. The unit of capture on the Ajax side is the screen, so any application you have open is in scope by default.
VXT's own time tracking is real and useful for what it does. After a call ends, you click a button in VXT and a time entry with the duration, the contact, and your default billing rate lands in your practice management system. That handles the call itself cleanly.
Ajax extends what gets captured around the call. A few practical implications of doing it this way:
It works whether your attorneys take calls in the VXT desktop app or the browser app
It doesn't require anything to be enabled inside VXT, and your VXT admin isn't involved
It captures the call together with the matter file you have open, the case law you were reading, and the email you sent right after
It groups the call with the rest of the matter work for the day, so the entry reads as one coherent piece of work
How Ajax captures your VXT work, step by step
Four things happen between the moment a VXT call starts and the moment a time entry shows up for your review.
Ajax sees what's on your screen during the call
While the call is happening, Ajax reads the VXT window (the contact name, the phone number, the call duration counter, any in-call notes you type) along with everything else in view. The matter file in another tab, the case law you're skimming, the email thread you're working from, the calendar invite that triggered the call. Pixel by pixel, in real time.
One thing to flag up front. Ajax doesn't read the call audio. We read what's on the screen, so the narrative we draft comes from the VXT window, your in-call notes, and the documents you have open. The audio itself stays between you and the person on the other end of the line.
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 "Conference call with opposing counsel re: deposition scheduling," that's what your Ajax-drafted entries look like. If you usually write "Call w/ OC re depo," that's what they look like.
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 plenty of the people relevant to a case (judges, opposing counsel, peripheral parties, a co-defendant's paralegal) aren't in it. Those names live in email threads, documents, and the metadata of the calls themselves.
Ajax builds matter attribution from the content of everything on screen during the call. The VXT contact card, the matter file you have open, the prep email you pulled up before dialing. When Ajax can't confidently attribute a call to a matter, it flags the draft entry for you to assign, then it learns from the correction. The next call from the same number about the same case is handled automatically.
Related work gets grouped into one entry
A piece of billable phone work is rarely just the call. It's the fifteen minutes of prep, the twenty-minute call, the ten-minute follow-up email, and the five-minute Slack message to a colleague summarizing what was decided. As individual line items, that's four entries to wade through. As one piece of work, it's a single fifty-minute entry attributed to the right matter.
Ajax groups intelligently across the day. You can configure block billing or itemized entries depending on your client's guidelines.
What Ajax adds on top of VXT's built-in time tracking
VXT captures the call itself. Ajax captures the call plus everything around it. Most firms run both, and the entries don't collide.
What VXT can see is the duration, the contact, and any in-call notes the attorney enters into VXT directly. That's the foundation of the call-side time entry that lands in your PMS.
What VXT can't see is the work that happens around the call:
The matter file the attorney had open while talking
The email written ninety seconds after the call ended
The case law tab in the browser
The prep notes reviewed beforehand
None of that runs through VXT. All of it is part of the same billable hour.
When VXT has already pushed a call entry to your practice management system, Ajax sees that entry and groups the surrounding work around it instead of double-writing the same minutes. The result is one richer entry with the call at its center, ready for review.
Captured VXT work flows back to whichever practice management system your firm already uses. We sync in both directions with Clio, MyCase, PracticePanther, SurePoint, Centerbase, Filevine, and Actionstep, and we support most other billing systems. Release an entry from Ajax and it becomes an entry in your PMS. Edit it in either place and the edit shows up in both. Add a new matter or an activity code on the PMS side and Ajax picks it up automatically. VXT integrates with Clio and MyCase too (alongside about 15 other practice management systems on VXT's integrations directory), so for most firms the destinations match and you're not pushing entries into different places.
How to get your IT team to enable VXT on Ajax
There's nothing to enable inside VXT. The work is on the Ajax side, and most IT teams green-light Ajax in a single review meeting. Five things to bring to the table.
Walk IT through what Ajax reads and where it goes
Ajax's privacy architecture is built for the sensitivity of legal work. Screen content is processed, used to draft the entry, and then deleted on a rolling 30-day window. Ajax does not use client data to train its models. The AI providers underneath Ajax are contractually prohibited from retaining or training on data that passes through. Ajax is SOC compliant. Every lawyer's Ajax is an individual silo, and managing partners see aggregate metrics only, never raw activity.
Ajax works with firms that handle cases for six of the eight money center banks. If the security posture clears that bar, it generally clears the bar for any mid-market firm too.
Hand IT the docs
During the trial, our team provides the SOC report and a security one-pager on request. For firms with longer-form security questionnaires (the kind with 80 line items about data flow, encryption, vendor management, and incident response), we fill those out directly. Most security reviews close inside a week.
Coordinate the desktop deployment
Ajax is a native desktop application, deployed per machine. Most firms install it through their existing MDM (Jamf on Mac, Intune on Windows). It coexists with endpoint detection and DLP tooling without configuration headaches. For firms without centralized MDM, our team supports per-machine install via a guided link sent to each attorney.
Confirm VXT is being used on the desktop
Ajax captures the desktop and the browser. If your attorneys take VXT calls in the desktop app or the browser app, that activity is visible to Ajax. If a call only happens on a mobile phone with no mirroring, the call isn't captured by Ajax. The VXT mobile entry still flows to your PMS through VXT's own integration, so the call itself isn't lost. The surrounding desktop work that happened in parallel still gets captured by Ajax.
Coordinate the PMS sync
If your firm already uses VXT to push call entries into your PMS (Clio, MyCase, or one of the other systems VXT supports), you can leave that flow on. Ajax respects whatever's already in the PMS and groups the surrounding work around it. If you'd rather have one tool pushing every time entry, attorneys can skip the post-call push step in VXT and let Ajax handle all entries including the call itself. Either configuration works, and the IT team can change the convention later without a redeployment.
One 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 and billing guidelines. That distinction matters for security positioning, and it's the reason firms with strict data policies move from a security review to a signed pilot without a months-long detour.
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 VXT-anchored 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 call-adjacent work (the prep, the follow-up email, the doc pulled up mid-call), 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 in their phone workflow 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 VXT
Does Ajax read my call audio?
No. Ajax reads what's on your screen. The narrative Ajax drafts is built from the VXT window, the matter file, your in-call notes, and the email thread you pulled up. The audio itself never enters the picture.
Will I get double-billed if Ajax and VXT both push entries?
No. Ajax sees the call entry VXT already sent to your PMS and groups the surrounding work around it rather than writing a second entry for the same minutes. You end up with one richer entry anchored on the call.
Will Ajax replace VXT?
No. VXT runs the phone system, the call routing, the SMS, the AI call summaries. Ajax handles the timekeeping for everything you do on your desktop, including the work around the call. They sit alongside each other and don't overlap on what each tool is built to do.
Does Ajax work with VXT calls taken on mobile?
Ajax is a desktop application, so mobile-only calls aren't captured by Ajax. The VXT-side time entry for the call still flows to your PMS through VXT's own integration, so the call itself isn't lost. If you take a VXT call on your phone while also working in a matter file on your laptop, the desktop work is captured by Ajax and grouped with the VXT call entry once it reaches the PMS.
What about a call I take in VXT without opening the matter file?
Ajax can still attribute the call from the VXT contact card and any related browser tabs. The entry will be thinner than one with full surrounding context, and Ajax may flag it for you to confirm the matter. Once you confirm, the next call from the same contact about the same case is attributed automatically.
Final thoughts
The phone is where the highest-stakes conversations happen, and where the smallest fragments of time disappear. A fifteen-minute call almost never costs you fifteen minutes of work. By the time you've prepped, dialed, hung up, written the follow-up email, and forwarded the doc you promised, you're closer to an hour. The call itself is usually the smallest piece.
Ajax catches that whole arc because the desktop sees everything the call touched. If you want to see what a week of your own VXT calls looks like as time entries, start a trial for $100 or book a demo.
