Tracking Time Spent Texting Clients (SMS and RCS)

Ten years ago, a client who wanted an answer called you or sent an email. Today, a growing share of them send a text. They text to confirm a meeting, to ask whether the contract language covers a scenario, to forward a question from their business partner, and to check on status at nine in the evening. You answer, because responsiveness is part of the service, and because a two-line reply feels easier than scheduling a call.

Then almost none of it reaches an invoice. Of all the ways billable time leaks out of a professional's day, cataloged in our guide to capturing every billable hour, texting is the most complete leak. Calls at least have a start, an end, and a log you can check later. Email at least leaves a sent folder to reconstruct from. Texting leaves a thread you scroll past and a vague sense that you were "just answering a quick question." This post explains why text time is genuinely billable, why manual timers structurally fail to catch it, and how TrackTime captures it automatically on Android. We will also be plain about the current boundaries of that capture: TrackTime supports SMS conversations and incoming RCS messages in Google Messages, and only Google Messages, today.

Texting is real client work

Start with the premise, because some professionals still hesitate over it. When a client texts you a question and you apply professional judgment to answer it, that is the same work you would have billed if it had arrived by phone or email. The medium does not change the value. A lawyer who confirms a filing deadline by text has given legal advice. A consultant who reviews a screenshot and replies with a recommendation has delivered consulting. An accountant who answers a quarterly-payment question in three messages during tax season has done accounting.

The arithmetic is what makes this worth fixing. Most professionals who bill by the hour round each task up to a minimum increment, and in legal practice the common convention is six-minute increments, meaning tenths of an hour. Under that convention, a four-minute text exchange bills as 0.1 hours. Three or four such exchanges in a day, which is unremarkable for anyone whose clients text, add up to hundreds of billable increments over a year. This time is not marginal. It is a recurring, legitimate line item that simply never gets written down.

Why manual timers never catch it

The failure is structural, not a matter of discipline. A manual timer assumes work that has a beginning you notice and an end you notice, with enough duration in between to justify the ceremony of starting and stopping a clock. Texting violates every part of that assumption.

• The sessions are tiny. A text exchange might take ninety seconds. Nobody opens a timer app, finds the client, and starts a timer for ninety seconds of work. The overhead feels larger than the task.
• The sessions are fragmented. A single conversation often plays out as five short bursts across two hours. Even a diligent tracker cannot sensibly stop and restart a timer five times, and merging it into one block from memory afterward produces a guess.
• The work is interrupt-driven. Texts arrive while you are doing something else, frequently something you are already timing for a different client. Handling the interruption correctly would mean pausing one timer, starting another, and then reversing both, which nobody does.
• The work happens off hours. The evening and weekend replies are the least likely to be logged, because you are furthest from your timesheet and least in a working mindset when they happen.

End-of-week reconstruction does not rescue this. You can scroll a thread and see the messages, but the thread does not tell you how long you spent reading, thinking, and composing, and memory reliably shrinks small tasks toward zero. If any category of work needs contemporaneous, automatic capture, it is this one. Our post on where billable time leaks covers the same pattern across calls and email.

How TrackTime captures texting time

TrackTime's Android app captures texting activity automatically, with your explicit permission, and turns it into reviewable time entries, applying the same automatic time tracking approach it uses for calls and email. Conceptually, the capture works in three steps.

1. Detection. With the permissions you grant during setup, the app observes messaging activity in Google Messages on your phone. It notes that a message event happened, when it happened, and which phone number was involved. That is all the information it needs.
2. Session building. When you open a conversation from a client's notification, TrackTime measures the time you actually spend in that conversation and records it as a single entry with a start, an end, and a duration, noting how many messages were exchanged. Messages you handle without opening the conversation, such as reading them from the notification shade or sending a quick reply, are recorded as individual short entries that you can merge or adjust during review.
3. Client matching. The phone number is matched against your client list, so the session arrives in your dashboard already attributed. A conversation with a number you have not associated with any client is simply not billable work in progress, and you can handle it accordingly during review.

Captured sessions appear in the TrackTime web dashboard alongside your captured calls and email time. Nothing goes to an invoice automatically. You review each entry, adjust the duration or description where needed, decide what is billable, and generate the invoice from the same dashboard, since invoicing is built in.

What is supported today, stated plainly

Precision matters more than breadth here, so here is the exact scope of TrackTime's texting capture as it stands today.

• SMS conversations are captured. Ordinary text message exchanges, in both directions, are detected, grouped into sessions, and matched to clients.
• Incoming RCS messages in Google Messages are captured. RCS is the richer messaging standard that Google Messages uses between modern Android phones and, increasingly, with iPhones. TrackTime captures incoming RCS messages and includes them in conversation sessions.
• Google Messages is the only supported messaging app. If your client texting happens in Google Messages, which is the default messaging app on most modern Android phones, you are covered. Conversations in other messaging apps are not captured today.

We state the boundaries this bluntly because the alternative, a vague claim that "your texts are tracked," is exactly the kind of overpromise this category suffers from. If your client communication lives primarily in a chat app we do not support, TrackTime's texting capture will not see it, and you should know that before you subscribe rather than after.

It is also worth repeating the platform reality. This capture is possible because Android lets a user deliberately grant an app visibility into messaging activity. iOS does not allow any third-party app to observe notifications or messages from other apps, which is why no iPhone app can do this and why TrackTime does not offer an iOS app. We wrote a full explainer on the blog about those platform differences.

Privacy: metadata only, by design

An app that observes messaging activity should be held to a strict standard, and ours is described in full in our post on metadata-only time capture. TrackTime stores metadata only: who the conversation was with, when it happened, and how long it lasted. The contents of your messages are never stored on our servers. There is no transcript, no message body, and no archive of what was said, because none of that is needed to bill the time.

For lawyers this distinction is not cosmetic. Privileged communication stays privileged, because the substance of the exchange never leaves the conversation. Your invoice line says that you exchanged messages with the client for twelve minutes about their matter, which is precisely what a contemporaneous manual entry would have said, except that the duration is measured instead of guessed.

From captured session to invoice line

A texting entry follows the same review workflow as every other captured entry. It lands in the dashboard attributed to the client with a measured duration. During review, you confirm it is billable, apply your rounding convention, and give it a description a client will accept, such as "Text correspondence with client regarding closing timeline." Because the capture is contemporaneous, the record shows the exchange happened on the date and at the time it actually happened, which is a far stronger position in any billing conversation than an entry reconstructed at month's end. Then it goes onto the invoice with everything else, from the same tool, with no export step.

Frequently asked questions

Which messaging apps does TrackTime support?

Google Messages only, today. Within Google Messages, TrackTime captures SMS conversations and incoming RCS messages. Conversations that happen in other messaging apps are not captured, and we would rather say so plainly than let you assume otherwise.

Does TrackTime read or store my text messages?

No. TrackTime stores metadata only, meaning the contact, the time, and the duration of the conversation session. Message contents are never stored on our servers, and email subject lines are never stored either. The capture exists to measure the time, not to archive the communication.

Can I bill clients for text messages ethically?

If answering the message required your professional judgment, it is work, and work is billable under an hourly engagement. The same conventions that govern calls apply: round to your stated increment, describe the work specifically, and review every entry before it reaches an invoice. Clients dispute vague entries and surprise entries, not accurate ones, so it also helps to tell clients up front that substantive text exchanges are billed like any other correspondence.

Can an iPhone app track texting time this way?

No. iOS does not allow third-party apps to observe notifications or messaging activity from other apps, so genuine automatic capture of texting time is not possible on an iPhone. This capture works on Android because the user can explicitly grant that visibility. There is no TrackTime iOS app for exactly that reason.

Find out what your threads are worth

You do not have to estimate how much texting time you are losing. You can measure it. Start a free 7-day TrackTime trial, grant the messaging permissions on your Android phone, and let a normal week happen. The dashboard will show you every client conversation you would never have written down. You can read more about how the capture works on the Android app page.