Hourwell
Deadlines for the work between your teams. Hourwell counts working time on any ticket condition you choose: a group, a status or custom status, an empty assignee, a ticket field value, a tag. When the clock nears or passes its goal, Hourwell has Zendesk warn people, move the ticket, change its priority or tag it. Agents see a live countdown in the ticket, and leads see every running timer in one list. Hourwell is for internal deadlines (operational level agreements between teams, pickup times, time with engineering, time on hold) that your customer SLA policies do not measure. It works on every Zendesk plan, including Team, which has no SLA policies or business-hours schedules. Hourwell is built by Great Work LLC. It is not made or endorsed by Zendesk. Timers on anything on the ticket Runs while any mix of conditions holds: group, status, custom ticket status, assignee set or not, priority, type, form, brand, tags and ticket fields (drop-down, checkbox, text, number). Pauses while another condition holds, for example while the ticket waits on the customer. Per stint or cumulative: start over each time a ticket comes back to a team, or add up all the time it spends there. Up to 20 timers, each with its own goal and warning time. Templates get you started. Business hours that match how you work Calendars with any time zone and daylight saving, split shifts (9:00-12:00 and 13:00-17:30), and one-off or yearly holidays. Each timer picks its calendar. On Team, Hourwell brings business-hours counting your plan does not have. On Growth and Professional, which allow one schedule, you can keep a calendar per team or region. Warnings and breaches that act Email the assignee, the ticket's group, another group or an agent; move the ticket to a group or agent; set priority, status or a field; add or remove tags. The actions run as Zendesk triggers that Hourwell creates in your account, so they behave like any other trigger and show in the ticket's history. Every overdue ticket lands in the "Hourwell: overdue timers" view, and finished stints that went over keep a tag so you can filter on them. Answers to what timer users ask for No cap on timers. Every plan counts every timer: there is no monthly allowance per agent. Exact clocks. Each clock is rebuilt from the ticket's own history, so time in a status is right even if it changed while nobody had Zendesk open. When warnings and breaches fire Within a minute of the deadline while the ticket's assignee (or, for an unassigned ticket, someone in its group) has Zendesk open, and within about 4 minutes when anyone else with Hourwell does. With nobody signed in, Zendesk's own hourly automations take over. They never act early: usually within an hour or two after the deadline, and within a few hours for deadlines more than half a day out. Timers on business hours rarely reach a deadline while your team is away, because their clock stops too. Plan (billed monthly by Zendesk) Standard: $3 per agent per month. Every feature, every timer. 14-day trial; Zendesk asks for a card at install and billing starts when the trial ends unless you uninstall. Your data Hourwell runs entirely in your browser inside Zendesk. There is no Great Work server, no account to create and no API token to paste. Timer definitions are stored in the app's settings in your Zendesk; each ticket's clock snapshot is stored on the ticket, in an Hourwell ticket field. Hourwell reads ticket history only to compute clocks, sends nothing to Great Work or anyone else (not even usage statistics), keeps no copies of your tickets and uses no AI. Details are in the data access section and our privacy policy. Support Email hello@greatwork.company. We reply within one business day.
Linked Ticket
The Zendesk Support Linked Ticket app enables you to create a child ticket from an existing parent ticket and link the two tickets together. This is particularly useful when you need to have two separate conversations around the same issue. For example, a customer reaches out to you about an issue and you need to loop in a third party to resolve the issue. With the Linked Ticket app, you can create a child ticket from the ticket your customer submitted to start a conversation with the third party. This way the third party will not have access to your customer's information but both tickets are linked in the agent's view. By enabling this app, you agree to the Built by Zendesk Terms of Use.