Does Ajax Integrate with Teams Phone? How to Get Started with Teams Phone on Ajax
Phone work is the hardest billable activity for a lawyer to capture. A timer needs something to attach to, and a phone call usually has no paper trail until you sit down at the end of the day and try to reconstruct it. A four-minute clarification with a client, a quick conference call about a hearing date, a five-minute negotiation by phone before lunch. None of it makes the bill unless you stop and write it down.
We built Ajax's Teams Phone capture to close that gap. Ajax reads what's happening on your screen during the call, supplements that with Teams metadata for duration and contact, drafts a time entry in your voice, and pushes it to your practice management system. You don't start a timer, and you don't reconstruct anything later.
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, supplemented by light integrations with the tools you already have, including Microsoft Teams.
Privacy is one of the strongest parts of Ajax's architecture. 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 Teams Phone?
Yes, and the way we do it is worth understanding before you start.
There is no Teams Phone plugin to install on a per-user basis. Ajax captures Teams Phone the same way it captures every other application on your desktop, by reading what's on your screen during the call, and we supplement that with Teams call metadata (the duration and contact tied to the call) through a lightweight API connection that your Microsoft admin approves once during onboarding.
We do not record your call audio. We do not transcribe what was said. What we capture is what's visible while you're on the call: the contract you opened to reference, the matter file you typed a note into, the contact card in the Teams call window, the email thread you pulled up for context. Combined with Teams metadata for the call itself, that produces a time entry that reflects the actual work, without anyone listening to your client conversations.
A few practical implications of capturing Teams Phone this way:
It works whether you use Teams Phone in the desktop client or the browser
It works if you take the call on a desk handset paired with Teams
It captures the call together with the documents, emails, and notes attached to the same matter, so the entry reads as one coherent piece of work
It doesn't add a new system for your IT team to vet beyond the Ajax desktop install
How Ajax captures your Teams Phone work, step by step
Five things happen between the moment a call starts and the moment a time entry shows up for your review.
Ajax sees the work around the call
While the call is happening, Ajax is reading what's on your screen, pixel by pixel, in real time. It picks up the Teams call window, the contract or pleading you opened to reference, the matter file you typed a note into mid-call, and the email thread you scrolled back through to remind yourself what your client said last week.
Teams metadata fills in the call itself
Through the Teams API, Ajax pulls duration, participants, and timestamp from the call. So even if you took the call on a headset and never touched a key, the call still appears in your draft entries with the right length and the right contact attached.
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 "Phone call with client re: settlement strategy," that's what your Ajax-drafted entries look like. If you usually write "TC w/ client re settlement," that's what they look like.
Ajax attributes the call to a matter
Attribution comes from two signals at once. The Teams contact (the person you called) tells Ajax who. The on-screen content (the contract you had open, the matter folder you typed into) tells Ajax which case. When the contact alone is ambiguous (opposing counsel who appears in three of your active matters, a paralegal who works across a whole portfolio), the on-screen context disambiguates. Ajax builds matter attribution from these combined signals. When it can't confidently attribute the call, it flags the draft entry for you to assign, then it learns from the correction.
Related work gets grouped into one entry
A single piece of billable phone work is usually the prep email you sent that morning, plus the call itself, plus the contract you reviewed during the call, plus the summary note you typed afterward. As individual line items, that's four entries to wade through. As one piece of work, it's a single entry of about an hour. 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 secondary flow worth knowing about. If a follow-up email or document came out of the call, Ajax can file that email or document into the right matter folder in your PMS or document management system, the same way it handles email filing. So the entry shows up where you bill, and the related artifacts show up where the case lives, with no dragging or copy-paste in between.
How to get started with Teams Phone on Ajax
There's nothing for you to install inside Teams. 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 authorize the Teams metadata supplementation
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. About 97% of firms that pilot Ajax move into a subscription afterward. The fastest way to see whether Teams 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 30 minutes a day of previously unlogged call-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 when they look at a week of their own call logs against what made it onto the bill.
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 Teams Phone
Does Ajax record or transcribe my call audio?
No. We capture what's on your screen during the call (notes, documents, the Teams contact card in the call window) and we use Teams metadata for duration and contact. The audio of the call itself is not touched, stored, or transcribed.
Does Ajax read my personal Teams calls?
Your Ajax is yours. Nobody at the firm can see your activity, not even managing partners, and there's a pause button if you switch to a personal task. Screen content is processed and then deleted on a rolling basis.
Does Ajax work with Teams Phone on mobile?
Ajax is a desktop application, so mobile screens aren't captured unless they're mirrored to your laptop. Teams metadata for the call (duration, contact) still flows in, so the call won't disappear from your entries, but the work around the call only gets captured if it happened on your desktop.
Will Ajax replace Teams Phone or my practice management system?
No. Ajax sits between them. You keep using Teams Phone the way you already do. The drafted entries go into your PMS for billing.
What about a call I take with no screen activity at all?
The capture surface is thinner, but the call doesn't disappear. Teams metadata still gives Ajax duration and contact, so the call shows up in your entries with the right length. If you typed a quick post-call note into the matter file or sent a follow-up email, Ajax pulls the substance from there.
What doesn't Ajax capture?
Anything that never touches a screen. That includes calls where you took only handwritten notes, in-person conversations, and hallway chats with a partner. Pen-and-paper work is a blind spot for any screen-based tool, ours included.
Final thoughts
Most billable phone work is small and scattered. A four-minute clarification, a quick scheduling call, a five-minute negotiation before lunch. 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 a half-day nobody got paid for.
Ajax catches that work because the desktop is always watching what's on your screen during and after the call, and because Teams metadata fills in the call itself without anyone touching the audio. If you want to see what a week of your own Teams Phone work looks like as time entries, start a trial for $100 or book a demo.
