Ticket Timer
A timer in the ticket sidebar that counts only the time an agent actually spends on the ticket in front of them, keeps counting across page refreshes, and saves each agent's time when the ticket is submitted.
Getting started
- Install Ticket Timer from the Zendesk Marketplace and choose which agents and groups may use it.
- Run Set up as an admin. Open Ticket Timer in the left navigation bar and click Run set up. It creates the custom object
time_entrieswith its fields and two decimal ticket fields, Time spent total (min) and Time spent last entry (min), then offers Save ids to the app settings. - Give light agents and custom agent roles access. Zendesk gives light agents, contributors and custom roles no access to a new custom object. In Admin Center, go to Objects and rules, Custom objects, Time entries, Permissions and grant View and Add to light agents and to each custom agent role that uses Ticket Timer. Until then their time is not saved, and the sidebar says why. Give View on all records: Zendesk also offers its default access rule Created by, and with it those agents see only their own time in the ticket totals and the report.
- Add the two ticket fields to your ticket forms (Admin Center, Objects and rules, Tickets, Forms) if agents should see the totals on the ticket. Explore reports can use them either way.
- Open a ticket, or start a new one. The timer starts (or waits for Start if auto-start is off). Submit the ticket as usual; the time is saved with it.
What counts as time
| Situation | What the timer does |
|---|---|
| The ticket is open in front of the agent | Counts. |
| The agent switches to another ticket tab in Zendesk | Pauses this ticket at once and resumes when the agent comes back. Only the ticket in front counts, so two open tickets never count twice. |
| The browser tab is hidden for a short while (a look at the knowledge base or another tool) | Counts, up to the idle threshold. |
| The browser tab is hidden, or the computer is locked or asleep, for longer than the idle threshold | That time is not counted. The sidebar says how long the agent was away and offers Count it to add it back. |
| The page is refreshed or Zendesk is reopened | The timer continues from where it was: its state is kept per ticket and agent in the browser and written every few seconds. |
| The same ticket is open in two browser tabs | Both tabs share one timer; once one tab saves the time, the other picks that up and does not save it again. |
| The agent clicks Pause | Stops until Resume. |
Correcting time
Use +5m, +15m and −5m, or Edit to type the total: 1:30, 1:30:00, 90 (minutes), 45m, 1.5h or 1h 30m. The timer keeps running from the new value. Each entry can carry a note (up to 500 characters) and a billable flag.
What happens on submit
- If the timer shows less than a second, nothing is written (unless Block saving a ticket with zero time is on, which stops the save with a message). If it shows less than the minimum entry (60 seconds by default), nothing is written either; the time stays on the timer and is added to the next save. Rounding is applied only after this check, so a quick follow-up update never becomes a 15-minute entry.
- For agents who may edit tickets, the two ticket fields are set in the same update: the total becomes the sum of every agent's saved entries on the ticket plus this one, the last-entry field gets this entry's minutes. The total is always rebuilt from the entries, so two agents saving close together, or an empty field, cannot lose time.
- Once Zendesk has accepted the update, the time is rounded up to the rounding setting and written as one record in the custom object: ticket id, agent id and name, seconds, started at, ended at, billable, note, source, and an entry key (agent, ticket and timer start) that stops the same time being written twice.
- That time is taken off the timer, which keeps running. The sidebar lists the time each agent has saved on the ticket.
If Zendesk refuses the update, nothing is recorded and the timer keeps its time. If writing the record fails, the ticket is still saved, the timer keeps its time and the sidebar says why; a missing permission is named with the setting the admin must change, other errors are retried with the next update, and a write that did go through is recognised by its entry key rather than written again. On a new ticket the record is written as soon as Zendesk has given the ticket its number.
Light agents
Light agents need View and Add on the Time entries custom object (Getting started, step 3). Light agents cannot change ticket fields in Zendesk, so for them Ticket Timer writes the time entry only and says so in the sidebar. Their time is in the time log and the report; the total field includes it the next time a full agent saves time on the ticket, because the total is rebuilt from all entries.
Time report
The Ticket Timer page in the left navigation bar lists entries for today, this week, last week, this month, last month or a custom range, grouped by agent, by ticket or by day, or as single entries, with total, billable time, entry count and ticket count. Billable only filters the list. Copy CSV copies the entries in view (ticket id, agent, seconds, minutes, start, end, billable, source, note) for a spreadsheet; cells that start with a formula character are made safe. Days follow the agent's Zendesk time zone. The report searches the entries created in the chosen period, up to 10,000 per period.
Settings
| Setting | Default | Meaning |
|---|---|---|
| Custom object key | time_entries | Where entries are written. Set up creates it. |
| Total time field id, Last entry field id | empty | Decimal ticket fields that receive minutes. Set up fills them in; leave empty to write entries only. |
| Rounding (minutes) | 0 | 0 (exact seconds), 6 or 15. Entries are rounded up. |
| Idle after (minutes) | 5 | Time away longer than this is not counted. |
| Minimum entry (seconds) | 60 | Shorter time is not saved but stays on the timer for the next save. Checked before rounding. |
| Start the timer when a ticket opens | on | Off: the agent clicks Start. |
| Entries are billable by default | on | The starting value of the Billable box. |
| Block saving a ticket with zero time | off | On: a ticket cannot be submitted with an empty timer. |
Where the data is
Entries are custom object records in your own Zendesk; totals are ticket fields in your own Zendesk. The running timer is kept in the agent's browser (local storage, per Zendesk account, agent and ticket) and dropped after a week without activity; old timers are cleared when the app starts. Ticket Timer has no server and sends nothing to Aldorock.
Frequently asked
Can I bring over entries from Zendesk's Time Tracking app?
Not in this version. Its totals live in its own ticket fields; you can point Total time field id at the same field if it holds minutes, and new time adds to it.
Which plans does it need?
Custom objects are available on Zendesk Suite and Support plans that include them; set up tells you if the account cannot create one.
Changelog
- 1.0 (November 2026): first release.
