Incident response time your client can see.
A timer for incident response hours that runs in Microsoft Teams or Slack. Your client watches it run, and every hour is billed the way their contract says.
From the first minute to the invoice.
- 01
Started from the chat
Incident response time starts from Teams or Slack, the moment it begins.
- 02
Visible to your client
Your client sees the clock start and stop, and approves it where the contract asks.
- 03
Nothing forgotten
SOC Tally makes sure no timer is left running.
- 04
Billed automatically
Every hour lands on the client’s invoice, the way their contract is written.
The hours your client saw, on the invoice.
Every session goes straight onto the client’s invoice, with nothing to add up by hand.
You decide when incident response is done.
- 01
Only the people you allow
You decide who runs the clock.
- 02
Corrections on record
Hours can be corrected, and every change is on record.
- 03
With or without a shared channel
Every client can follow the clock.
Questions we get asked.
Who can start and stop the clock?
Only the people you allow.
What if a client isn’t in a shared Teams or Slack channel?
They can still follow the clock, by email or from a status link.
What happens when a block of hours runs out?
Hours over the block are billed at the rate the contract sets.
Can hours be corrected afterwards?
Yes. Hours can be corrected, and every change is on record.
Simplify next month’s SOC billing.
Join the waitlist, and we’ll show you SOC Tally on contracts like yours.