Skip to main content
Tickets are the working records for customer support issues. Each ticket keeps the customer relationship, issue description, responsibility and support history together. Open Support > Tickets to use the list or Kanban surface. Desktop provides richer table and board controls, while mobile uses compact cards and mobile filters.

​
What belongs on a ticket

The create flow can include the company or customer, a related deal, type, category, title, detailed description, impact, priority and assignee. A related deal can only be selected from deals belonging to the selected company. That keeps support history connected to the correct commercial relationship.

​
Ownership and status

Assign the ticket to the person responsible for the next action. Users may need ticket.assign permission to change ownership. Update status as the work changes. A resolved or closed state should represent a genuine support outcome, not simply an attempt to remove the ticket from the queue.

​
SLA and automation

Where SLA features are enabled, Lynka can track first response and resolution timing. Automation can surface unassigned tickets, idle work, repeated reopening and SLA risk or breach.

Create a support ticket

Capture the customer issue and ownership correctly.

Assign and manage tickets

Keep responsibility and history clear.

Understand ticket SLA

Learn how response and resolution timing differ.

Support resolution workflow

Follow a ticket from creation to resolution.

Create a support ticket

Create a customer support ticket with company, related deal, type, category, title, description, impact, priority, assignee, and status context.

Assign and manage support tickets

Assign ticket ownership, move status, use list or Kanban views, and understand the automation signals that keep support work from going stale.

Last modified on September 7, 2026