Attribute engineer time across every client account
An MSP engineer touches six accounts before lunch. The billing question is not how long they worked — it is which client each stretch belonged to, and whether the contract covered it. Reconstructing that from ticket notes loses the gaps between tickets, which is where a surprising share of the month goes. ActivityPulse attributes time continuously, so the account split is observed rather than estimated.
What goes wrong today
If none of these are familiar, this probably is not your problem.
- Engineer time split across many accounts and reconstructed from ticket notes after the fact.
- Work between tickets — investigation, monitoring, the call that prevented an incident — unattributed.
- Contracted hours consumed without visibility until the account is already over.
- Client-by-client profitability that cannot be answered with confidence.
What changes
With privacy-by-default metadata tracking.
- Continuous attribution of engineer time to the client account it was spent on.
- The work between tickets represented alongside the tickets themselves.
- Per-account consumption visible during the period, with exports finance can reconcile.
- Each client's captured data isolated in its own database rather than filtered out of a shared one.
What the design guarantees
- per-org-database
- Each organisation's captured activity lives in its own database, so isolation is structural rather than a filter someone has to remember to apply.
- two-devices-one-hour
- One person working on two machines is credited with one hour, not two — overlapping time is resolved before it reaches a report.
- audited-config
- Every change to what an organisation captures is written to an audit log with who changed it and when.
Questions from teams like yours
Can one engineer's time be split across several client accounts?
Yes. Time is attributed to the project or task in context, and an engineer switches project from the desktop agent as they move between accounts.
How is one client's data kept separate from another's?
Each organisation's captured activity lives in its own database. Isolation is structural rather than a filter that has to be applied correctly on every query.
Can we show a client what their hours were spent on?
Reports break time down by project, task and application for the period, and can be exported. What a given viewer may see is bounded by their role and scope.
Does it work for engineers on customer sites without connectivity?
Yes. Capture continues offline and syncs on reconnect, with no lost hours and no double counting.
See where the hours actually went
Free for up to three people. Windows and macOS. No keystroke content on any plan, and screenshots off unless an administrator turns them on.