Zendesk Tasks
Set a ticket type to Task and a due date appears. Zendesk tasks turn a helpdesk into a passable to-do list, up to a point.
Zendesk tasks and the field they unlock
Zendesk's ticket Type field has four values: Question, Incident, Problem and Task. Three of them describe support work. Task is the odd one out, and it is the only one that changes what the form shows.
Pick Task and a due date field appears on the ticket. That's the entire mechanical difference. No subtasks, no dependencies, no checklist, just a date on a ticket that everything else in Zendesk can now read.
It sounds thin. It's more useful than it sounds, because a date that triggers, views and automations can all see is exactly the hook the rest of the platform needs.
What the due date lets you build
What the due date does not do is drive SLA policies. Those measure response and resolution against their own targets. A task with a due date next Thursday isn't an SLA-managed ticket, and mixing the two concepts confuses everybody.
What tasks are genuinely good at
Anything shaped like one person owing one deliverable by one date.
Follow-ups, first of all. "Check back with this customer after the release ships" is a perfect task, and it stops a promise from living in somebody's memory. Internal request queues work well too: facilities, IT hardware, a document that needs signing.
Onboarding steps are the other common one, especially where a customer-facing project has a handful of dated milestones and each one is genuinely somebody's job.
The other thing tasks handle well is anything you'd otherwise drop into a personal calendar reminder. If the work should be visible to a team rather than to one person, a ticket wins every time, because a reminder can't be picked up by a colleague when you're off sick.
The common thread is independence. Tasks that don't need to know about each other work beautifully here.
When it belongs in a project tool
The moment tasks depend on each other, Zendesk stops being the right home. There's no way to express that task B waits on task A, no timeline view, and no capacity planning across weeks. You can approximate all of it with tags and a heroic view. Six months later you have a mediocre project tool bolted to a confusing helpdesk.
The line I would draw: if you can hand somebody the list and they can work it in any order, tasks are fine. If the order matters and the dates move together, use Asana, Linear, Jira or a spreadsheet. There is more on that trade-off in Zendesk for project management.
The best pattern is usually both. Keep the customer conversation in Zendesk, push the delivery work into the project tool, and link them.
Tasks versus side conversations versus child tickets
These three get confused constantly, and the distinction is simple once you say it out loud.
A side conversation is asking somebody a question without leaving the ticket. It has no due date and no separate ownership. Use it when you need an answer, not a deliverable.
A task ticket is a discrete piece of work with an owner and a date. Use it when somebody owes something.
A child ticket splits work off a parent while keeping the link. Use it when the work is substantial enough to have its own conversation and its own status.
Pick one convention per team and put it in writing. Teams that use all three interchangeably lose things in the gaps between them.
Frequently asked questions
Is this real task management?
Lightweight. Zendesk task management means a ticket type with a due date, which handles a personal to-do list and nothing with dependencies.
How do I add a due date to a Zendesk ticket?
Set the ticket Type field to Task. The due date field appears on the form once you do, and it disappears again if you change the type back.
Can Zendesk tasks have subtasks?
Not in a project sense. You can create separate tickets and link them, and there is no parent-child work breakdown with rolled-up progress.
Do SLA policies apply to due dates?
No. SLA targets measure response and resolution times independently of the due date field. Treat them as two separate clocks.
Should internal requests be tasks or normal tickets?
Tasks if they have a deadline somebody is accountable for. If it is a request that gets answered rather than delivered, an ordinary ticket is simpler.
Keep the queue honest
Whatever you track as a task, a slice of your ordinary tickets is the same request arriving more than once. Ticket Merger clears those out.
Start free trial14-day free trial. No credit card required.