Help Center / How-to guides and use cases /
Using task boards as support queues
Task boards handle support queues when columns represent ticket statuses and inbound emails create task cards automatically. Each email becomes a card, gets assigned to a team member, and moves through resolution stages. Here's how to configure the setup.
- Create a support board. From the Tasks section, create a new task board or project dedicated to support. The board serves as the queue where all incoming tickets are managed.
- Set up status columns. Configure columns to match your support workflow: New, In Progress, Waiting (for client response), and Resolved. Additional columns can be added for Escalated, On Hold, or any stages your team uses. Each column represents a ticket status.
- Enable inbound email-to-task. Configure email forwarding so that inbound emails from clients create task cards automatically. Each email becomes a new card in the "New" column, with the email subject as the task title and the email body in the description. The sender's email is captured in the card details.
- Assign cards to team members. New cards in the "New" column are assigned to team members manually or through automations. An automation can assign tickets based on conditions like task group, status, custom field values, or any other criteria you define. The assigned team member receives a notification and picks up the ticket.
- Track resolution. As work progresses, cards move between columns by dragging. A card in "Waiting" signals that a client response is needed. Moving a card to "Resolved" closes the ticket. The board view shows every open ticket's status at a glance.
- Add custom fields for SLA tracking. Custom date fields can track when a ticket was received and when a resolution is needed. A "Due by" field based on your SLA terms creates a visible deadline on each card. Overdue cards can be highlighted or filtered to prioritise urgent tickets.
Delegation and response workflows
Cards can be reassigned between team members by changing the assignee. Comments on the card keep internal notes visible to the team without exposing them to the client. When a response needs to go back to the client, conversations linked to the card connect the ticket to the email thread, so the full history stays in one place.
Because inbound emails create task cards automatically, every client email enters the queue without manual ticket creation, and the board tracks each ticket from arrival to resolution.