Customer Support Template

A support desk board: tickets come in by form, get triaged, worked and resolved with the customer.

A customer support ticket board is a kanban board where each customer issue is a card that moves from new to resolved, so a support team can see every open ticket, who is handling it and which ones are waiting on the customer.

Sign in with your Edesy account, then click Use template in the preview to create the board, with its sample cards, in your workspace.

Category

Operations & SupportTicket Tracking

Ideal for

Customer Support & Success Teams

Columns

New → Triaged → In progress → Waiting on customer → Resolved

Sample cards

6

Custom fields

Requester email, Channel

Request form

Creates cards in New

Updated

2026-11-19

Columns and sample cards

The 5 columns of this board with its 6 sample cards, labels and fields, as they open in Edesy Boards. Copy the template to move cards and edit it.

  1. New

    2
    • Cannot reset passwordPriority: highAccess
      Channel:
      Email
    • How do I export invoices?Priority: mediumQuestion
      Channel:
      Chat
      Checklist 0/4: Acknowledge, Reproduce, Resolve, Confirm with requester
  2. Triaged

    1
    • App crashes on Android 14Priority: urgentBug
      Channel:
      Phone
      Checklist 0/3: Reproduce, Logs, Escalate to dev
  3. In progress

    1 / 8
    • VIP: bulk discount not appliedPriority: lowVIP
      Channel:
      Phone
  4. Waiting on customer

    1
    • Waiting for screenshot from customerPriority: urgent
      Channel:
      Email
      Checklist 3/3: Reset access, Verify, Close
  5. Resolved

    1 · done stage
    • Barcode scanner not pairingHardware
      Channel:
      Chat

Labels

Bug, Question, Access, Hardware, VIP

Custom fields

Requester email (Email), Channel (Single select, on card)

Request form: Open a support ticket · Customer Support

Tell us what you need; it lands on the “New” column of this board. Asks for Title, Description, Priority, Requester email, Labels, Attachments; each submission becomes a card in New.

Card templates

Incident

Why each column and card is there

New and Triaged

New is the inbox: every form submission and every ticket added by hand starts there. Triaged means someone has read it, set a priority and label and assigned an owner, so nothing sits unread while the team works older tickets.

In progress with a WIP limit of 8

The limit shows when the team has taken on more tickets than it can handle at once. Exceeding it is a signal to finish or hand off work before pulling in more from Triaged.

Waiting on customer

Tickets that need a screenshot, an order number or a reply from the customer move here, so they do not count against the team's active work and are easy to chase in one place.

Resolved (done stage)

Resolved completes the card, so the insights view shows how many tickets the team closes each week and how many are overdue.

Channel and Requester email fields

Channel shows on the card front, so you can see whether problems come mostly by email, chat or phone and staff those channels accordingly. Requester email stays inside the card so the agent knows whom to reply to.

Bug, Question, Access, Hardware and VIP labels

Labels separate product bugs that need developers from how-to questions and login problems that support can close alone. VIP flags important accounts for faster handling.

Open a support ticket form and Incident card template

The form asks for a title, description, priority, requester email, labels and attachments, so tickets arrive complete. The Incident template sets up outages and urgent problems the same way each time.

About the Customer Support Template template

This customer support template turns a board into a simple help desk. It has five columns: New, Triaged, In progress, Waiting on customer and Resolved. In progress has a work-in-progress limit of 8, so the team finishes tickets before picking up more, and Resolved is the done stage. Each ticket shows the Channel it came in on (the samples use Email, Chat and Phone) and keeps the Requester email inside the card. Five labels classify the issue: Bug, Question, Access, Hardware and VIP. The sample tickets look like those of a business software or retail tech company: a customer who cannot reset a password, a question about exporting invoices with an acknowledge, reproduce, resolve and confirm checklist, an app crash on Android 14 to reproduce, collect logs and escalate to development, a VIP whose bulk discount was not applied, a ticket waiting for a screenshot and a resolved barcode scanner pairing problem. An Open a support ticket form lets customers or colleagues raise tickets that land in New, and an Incident card template is ready for urgent issues.

Who it is for

It suits small support teams, customer success staff and founders who answer customers themselves and need more structure than a shared inbox. D2C brands, SaaS companies, IT service providers and businesses selling devices in India can use it for customer issues, and internal IT or admin teams can use the same board for employee requests. It works best for tens to a few hundred tickets a month.

How to use it

  1. 1

    Click Use this template, sign in with your Edesy account, then click Use template in the preview to create the board with its sample tickets.

  2. 2

    Edit the Channel options and labels to match how customers reach you, for example add WhatsApp as a channel, and delete the sample tickets.

  3. 3

    Share the Open a support ticket form on your help page or in auto-replies; each request becomes a card in New with the description, priority, requester email, labels and attachments.

  4. 4

    Triage new tickets daily: set the priority and label, assign an owner and move the card to Triaged; use swimlanes by priority so urgent issues sit at the top.

  5. 5

    Move a ticket to Waiting on customer whenever you need a reply, and to Resolved once the customer confirms the fix.

Connected templates in other Edesy apps

Customer Support Template: frequently asked questions

Yes. The Open a support ticket form is a public link. Anyone with it can submit a ticket, and each submission becomes a card in New with their answers and attachments.

Yes. An automation can act when a card gets a label such as VIP or Bug, or when a ticket is overdue: it can raise the priority, assign a senior agent, move the card, post to a Slack channel or notify people in the app inbox.

No. The board tracks tickets; you reply to the customer by email, chat or phone as you do today and record what happened in the card comments.

The insights view shows cards by stage, assignee and label, overdue cards and throughput over time. For deeper reporting, export the board to CSV.

Yes. Filter by the Bug label, or have an automation create a card on your development board when a ticket gets the Bug label, so developers keep their own workflow.

It is designed for a small team handling tens to a few hundred tickets a month. Archive resolved tickets regularly to keep the board fast and readable.

About the app

Yes, through the board request form. Share its public link; each submission becomes a card in the chosen column, with the answers in the card fields. Viewers of a shared read-only board link can see the board without an account.

Yes. Board automations run when a card is created, moved, assigned, labelled, completed, due soon or overdue, when a form is submitted or on a schedule, and can move, assign, label or archive the card, add a checklist or comment, create another card, call a webhook or post to Slack.

Related templates