Can one meeting tracker cover all my clients?

Most freelancers and consultants want the same few tables for every client: where each piece of work stands, which change requests are open, what was decided. This answer is for people with several clients on Google Meet and Microsoft Teams who would rather define that table once than six times. Trackers are described in full on trackers.

How does a tracker across all clients work?

You define it once, with its columns, their types and their rules, and choose "all your clients" as the meetings that feed it. TrackHeros then keeps a separate table for each client, filled only from that client's meetings.

On the Trackers page the tables appear together, with the client's name on every row, so "every open change request" is one screen rather than six. A client you add later gets its table automatically. Meetings in your private "No client" space are not included.

The definition is shared, so changing the columns, archiving the tracker or deleting it applies to every client's table at once. Meetings attached to one client's table stay with that client.

Why are two clients' rows never merged?

Because each client's table lives in that client's sealed workspace. If Client A and Client B both have a row called "Login API", those are two rows in two tables, with two histories, and nothing ever combines them.

That holds even where merging would look tidier. Inside one client, a row that looks like an existing one is flagged for you to decide; across clients the question never comes up, because the tables are separate from the start. How each workspace is sealed is on client isolation.

When is a one-client tracker better?

When the columns only make sense for one client, or only some of its meetings should feed the table. A one-client tracker can read every meeting of that client, or only those whose title contains certain words, such as "interview" or "standup".

It can also follow chosen recurring meetings, such as the Monday standup with one client, or be attached to specific meetings before they happen. Meetings plainly unrelated to the tracker's subject are skipped, so a tracker on every meeting of a client does not fill up with noise. Any finished meeting can also be sent to a tracker by hand, by the tracker's creator or an admin.

Can I ask about every client's trackers at once?

Yes. The assistant reads trackers, so a question such as "which change requests are still waiting for a decision?" is answered from the tables, naming the meeting each value came from.

In the read-only All my clients chat, every answer keeps its client label and two clients are never blended into one story. The same rule governs search; see can I search every client's meetings at once?

Which plans include trackers across all clients?

The pricing page says which plans include them, along with how many trackers each plan allows. The figures live there only, so they cannot go stale here.

The status table most people build first is walked through in project status across all clients. Connecting each client's Google and Microsoft calendars, so that every client's meetings reach its table, is on multi-account.