Ticket system features
Lightweight support for quick client questions and requests.
Tickets are for quick queries: "Can you update the footer link?" or "What's the login for our ad account?" Keep them out of your project board.
Every ticket gets a number, a type (bug, feature request, support, technical or general) and a priority (low, medium, high or urgent). Filter by status, priority, type, assignee, client or SLA status.
Replies stay in one thread on the ticket, and clients reply from their portal. Each reply sends an email notification, and the status can change automatically depending on who replied.
When auto-assignment is enabled, new tickets are distributed round-robin across the team. Reassign at any time; both the old and new assignee are notified.
Answer common questions with saved reply templates, edit them before sending, and leave internal notes the client never sees. Resolved tickets can auto-close after a set number of days.
Set response and resolution targets by priority, track first-response and resolution time, and get notified when a ticket is at risk of missing its target.
Why separate tickets from projects
When every minor question becomes a project task, your boards get noisy and priority gets lost. Tickets give small queries their own lane.
Clean Workflows
Tickets for questions, projects for work
How it works
Clients open a ticket from their portal with a title, description, type and attachments. Your team can also create tickets on their behalf.
The ticket is assigned round-robin if auto-assignment is on, or triaged by a team lead who sets the owner and priority.
The assigned team member replies inline. Clients see the response in their portal and can follow up.
Mark the ticket resolved, or convert it into a request if it turns out to be real work. Track first-response and resolution times.
Who uses it
Handle "how do I" questions, access requests and quick fixes without cluttering your project board.
Clients report issues as bug tickets. Triage, fix and close, or convert the ticket into a request if the fix is bigger than expected.
Access changes and billing questions go through tickets, with assignment history tracked on each one.
Small requests such as updating a link or swapping an image stay in tickets instead of becoming project requests.
Frequently asked questions
Tickets are for quick, simple queries that can be resolved in one or two responses. Project requests are for deliverables that require planning, assignments, and tracking. Keeping them separate prevents your project board from filling up with noise.
Yes. Clients go to Tickets in their portal, click Create Ticket, choose a type, set a priority if you allow it, and add attachments. They get a confirmation email and can track the status in the portal.
Yes. Team members with the convert permission can turn a ticket into a request when it turns out to be a bigger piece of work, so it moves onto your project board.
Yes, if you turn on SLA management. Targets are set per priority for first response and resolution (for example, 2 hours to respond to an urgent ticket). You can filter tickets by SLA status and get notified when one is at risk.
Tickets are on Pro ($79/mo), Plus ($149/mo) and Enterprise. Each plan includes one seat; extra seats are $20/mo on Pro and $30/mo on Plus.
Explore more features
Project management
Full project tracking for larger deliverables.
SLA tracking
Track response and resolution times against targets.
Client portal
Branded portal where clients submit tickets and view projects.
For how tickets fit alongside portal messages, request comments and email piping, see client communication for agencies.