# Customer support escalation kanban template

> Most tickets close in your help desk. The hard ones need engineering, billing or a manager. Track those on a board so nobody forgets the customer.

Source: https://cbse.club/templates/customer-support · Updated 2026-11-03

## Who this board is for

Support teams who already use an inbox or help desk and need a shared place for escalations that involve other teams.

## Columns

- **Maybe?**: every new card lands here first, to be triaged.
- **Investigating**: Support is digging in.
- **Waiting on customer**: We asked a question.
- **Waiting on team**: Escalated to engineering, billing or product.
- **Done**: finished cards, with history kept.
- **Not Now**: cards untouched for the auto-postpone period move here automatically.

## How to run it

1. Create a card for each escalation with a link to the original ticket. Avoid copying personal data you do not need.
2. Assign an owner who will update the customer.
3. Mention the engineer or teammate who needs to act.
4. Close when the customer has their answer.

## Suggested tags

- #billing, bug, account, question: type
- #vip: key account

## Tips

- Use a 7-day auto-postpone. If an escalation is untouched for a week, the customer has noticed.
- Send “card published” events to your support Slack channel with a webhook.

Use this template free: https://cbse.club/templates/customer-support/use

## Frequently asked questions

### Should support use kanban?

Kanban works well for escalations and follow-ups because work arrives unpredictably and passes between teams. Day-to-day tickets are usually better in a help desk.
