Help desk automation you can read in one line
Route each request to the right person, chase the ones going quiet, close the ones nobody answered, and tell the channel when something urgent lands. Plain rules, not a flowchart to maintain.
Get Started Free See PricingFree plan No credit card Setup in minutes
In short: Vertask automates a help desk in four layers. Request categories route new tickets to an agent or group (Free) or round-robin them across a group (Pro). Up to 25 rules act on events — a new ticket, a client reply, a status change — or on time, such as no reply for N days (Pro). Signed webhooks push events to your own systems, and Slack or Microsoft Teams channels can get a post for new tickets and updates (Pro).
Updated
The predictable work eats the day
Most of what happens to a ticket is the same every time: who gets it, how urgent it is, when to chase, when to close. Doing that by hand is where the hours go.
Assigning is someone’s whole morning
Every new request waits until a person reads it and decides who should have it.
Tickets go quiet
Waiting on the requester for a week, then nobody remembers to chase or close it. The queue fills with tickets that are not really open.
Urgent requests are found late
A “server down” email sits behind thirty password resets until someone scrolls far enough to see it.
What you can automate
Routing and round-robin
- Each request category goes to an agent or an agent group
- Round-robin across a group, skipping anyone marked away (Pro)
- A default priority for each category
- Separate intake addresses can route to their own team
Rules: when, if, then (Pro)
- Triggers: new ticket, client reply, agent reply, status change
- Timers: on hold with no reply for N days, unassigned for N hours, resolved N days ago
- Conditions on category, channel, priority, status, tags, words in the title or message, the requester’s email domain and custom fields
- Up to 25 rules, each with a 30-day run log
Actions that do the work
- Assign an agent or group, set the priority or status, add a tag
- Reply with a saved response, or add an internal note
- Notify the assignees, followers, admins or one agent
- Set a custom field
Webhooks (Pro)
- Up to 10 HTTPS endpoints
- Ticket, reply, client, asset and contract-expiring events
- Signed with HMAC, retried automatically, with a delivery log
- Alongside a 200+ endpoint REST API
Slack and Microsoft Teams posts (Pro)
- Post new tickets, replies and status changes to a channel
- Only High priority and above, if you prefer a quiet channel
- Teams posts arrive as an Adaptive Card
- No Zapier step in between
Scheduled and recurring
- Recurring tasks for the checks you run every week or month
- Any report emailed on a schedule (Pro)
- A weekly summary email for every agent
- Remind-me and snooze on any ticket
An urgent request, handled by rules
A request arrives
By email or the portal. Its category routes it to a group and the SLA clock starts.
A rule checks it
The message mentions “outage”, so a rule raises it to Critical and notifies the on-call agent.
The channel hears
Because it is High priority or above, it posts to the IT channel in Teams or Slack.
Nothing goes stale
If it later sits on hold with no reply for five days, a rule chases the requester, then closes it with a note.
Who it’s for
Small IT teams
Hand the sorting, chasing and closing to rules, and keep people on the work that needs them.
Team leads
Share work evenly with round-robin, and see every rule’s runs in its log.
Admins who integrate
Push events to your own systems with signed webhooks, or read anything through the REST API.
What’s included
Frequently asked questions
What is help desk automation?
Letting the help desk handle the predictable parts of a request on its own — assigning it, setting its priority, chasing replies, closing stale tickets and telling people — so agents spend their time on the parts that need judgement.
Is automation on the free plan?
Category routing to an agent or agent group is free, and so is the weekly summary email. Round-robin, rules, webhooks, Slack and Teams posts and scheduled report emails are Pro, at $12 per agent per month.
Can a rule loop or fire twice?
No. Rules nest at most three deep, never run twice on the same ticket in one go, and each timer rule runs once per ticket. Switching a timer rule on never sweeps your old backlog either: it only acts on tickets that reach that state afterwards.
Does an automatic reply count as our first response?
No. An automatic reply lets the requester know they were heard, but the SLA first-response clock keeps running until a person answers.
Can people create tickets from Slack or Teams?
Not from inside them. Vertask posts into Slack and Teams channels; tickets come in by email, the portal, the REST API or Zapier.
Do we need Zapier for any of this?
No. Routing, rules, webhooks and Slack and Teams posts are built in. Zapier (Pro) is still useful for connecting tools Vertask has no direct integration with.