Does Ajax Integrate with Teams Chat? How to Get Started with Teams Chat on Ajax
A growing share of a lawyer's billable conversations now happens in Teams. A four-line DM to a partner about case strategy, a channel exchange clarifying a hearing time, a back-and-forth with a client in their own Teams channel about whether to push back on a deadline. None of it feels worth stopping to log, and almost none of it ends up on a time entry.
We built Ajax's Teams chat capture to close that gap. Ajax watches the conversation as it happens, drafts a time entry in your voice, attributes it to the right matter, and pushes it into 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 work in, including Teams.
Ajax's privacy architecture is built for the sensitivity of legal work, including the privileged client conversations and partner-strategy threads that move through Teams. Screen content is processed, used to generate a draft time entry, and then automatically 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 Teams chat?
Yes, and the way we do it is worth understanding before you start.
There is no Teams app to install inside Microsoft Teams, and Ajax captures the chat content itself by reading what's on your screen rather than through a chat-side Graph API. Teams in general does have a lightweight API connection that your Microsoft admin approves once during onboarding (it's the same one that supplements call metadata for Teams Phone and Teams Video), but for chat the heavy lifting happens at the screen layer.
That's a deliberate choice. Most tools that advertise a "Teams integration" log that you were active in Teams, or at best pull message metadata (sender, channel name, timestamp). Ajax reads the conversation itself: the question your client just asked, the strategy line you typed to a partner in DM, the comment you dropped into the meeting chat panel mid-call. That difference shows up in the time entry, where the narrative reads like a lawyer's billing note describing the work you actually did.
A few practical implications of capturing Teams chat this way:
It works in Teams desktop, Teams in the browser, channel chat, DMs, and the meeting chat panel
It captures the chat together with the document you opened mid-thread, the call that followed, and the email that came in about the same matter, so the entry reads as one coherent piece of work
It captures threads you scan and close, draft messages you type and delete, and the side mentions that never make it into the billing system on their own
How Ajax captures your Teams chat work, step by step
Four things happen between the moment a Teams conversation starts and the moment a time entry shows up for your review.
Ajax sees what's on your screen
While you read, type, and reply in Teams, Ajax is reading the same content you're reading. Pixel by pixel, in real time. It picks up the participants in a DM, the channel name, the messages above and below yours, the file someone dropped into the thread, and the comment you posted in the meeting chat panel. It picks up the words you type as you compose them.
A draft entry lands in your voice
About 45 seconds after you finish an action, 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 "Conferred with co-counsel re: motion strategy," that's what your Ajax-drafted entries look like. If you usually write "T/c w/ OC re depo," that's what they look like.
Ajax attributes the chat to a matter
A lot of matter context lives in DMs and channel mentions that never make it into a CRM. Opposing counsel's paralegal posts a question in a shared channel. A partner DMs you about a witness you haven't formally added to the case file. A client mentions a property address in passing.
Ajax builds matter attribution from the content of the conversation itself. When it can't confidently attribute a message to a matter, it flags the draft entry for you to assign, then it learns from the correction. From there, the next chat involving the same client or the same opposing counsel gets attributed automatically.
Related work gets grouped into one entry
A single piece of billable Teams work is usually three messages in the morning, a meeting at two with five comments in the chat panel, and four follow-ups at four in the afternoon. Add the document you opened mid-thread and the email that came in about the same matter and you have eighteen line items for what was one piece of work.
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 Teams chat 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.
Teams chat normally lives outside the billing system. The conversation evidence sits in Microsoft 365 and the billable record sits empty. Ajax closes that loop by writing the work into the PMS as it happens, with a narrative that ties the chat to the matter and the matter to the invoice.
How to get started with Teams chat 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 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 quick 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 work with firms that handle cases for six of the eight money center banks.
Pricing starts with a flat $100 trial fee, and ongoing pricing depends on firm size. 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 capture is worth it for your firm is to run a pilot against a real week of conversations.
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 Teams chat 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 in their chat history when they look closely.
The real numbers our users report tend to land above that worked example. Nikki at Peakstone Law added 50 billable hours a month after switching to Ajax, without working any longer days. Amy Robinson added more than 60 billable hours a month, and her clients reported being happier with her communication on top of it. Both stories track with the chat-specific share, because individual messages feel too small to bother logging until you see a week of them stacked up.
One honest caveat here is that these projections assume the recovered time is billable and gets collected, which won't always be the case. Even at a 50% collection rate on what Ajax surfaces, the math still works for most firms.
Common questions about Ajax and Teams chat
Does Ajax read my personal Teams chats?
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 conversation. Screen content is processed and then deleted on a rolling basis.
Does Ajax work with Teams on mobile?
Ajax is a desktop application, so mobile screens aren't captured unless they're mirrored to your laptop. A quick DM from the courthouse doesn't get logged unless you also worked on it from your desk.
What about the spoken part of a Teams call?
Ajax reads what's on your screen. Spoken audio in a Teams call isn't transcribed from audio. If the meeting has a chat panel, a live transcript, or a shared screen with notes, that on-screen content is captured, but the voices themselves are outside what Ajax processes.
Does our Microsoft 365 admin need to approve anything?
There's nothing to install inside the Teams tenant itself. The Microsoft 365 API connection Ajax uses to supplement call metadata for Teams Phone and Teams Video is the only piece your admin approves, and it's a one-time consent during onboarding. For chat capture specifically, the work happens at the desktop screen layer on each lawyer's machine.
What doesn't Ajax capture?
Anything that never touches a screen. That includes the handwritten notes you took during a Teams call, in-person side conversations after the call ended, and threads in a channel you never opened. Pen-and-paper work is a blind spot for any screen-based tool, ours included.
Final thoughts
Most billable Teams chat is short. A three-line strategy DM, a four-message channel exchange before a hearing, a quick clarification with a client between meetings. That's exactly why it leaks. Nobody stops to log a two-minute conversation, and by the end of the week, the two-minute conversations have added up to half a day nobody got paid for.
Ajax catches that work because the desktop is always reading the content of your screen, and because the matter context comes from the conversation itself, with no channel-tagging required on your end. If you want to see what a week of your own Teams chat looks like as time entries,start a trial for $100 orbook a demo.
