Industries / Support

Ticket tracking for customer support teams

Customers open their requests in their own portal and see only their own. First-response and resolution targets are counted in working days, and a ticket about to miss its target is marked in the list.

The problem

Requests are scattered and nobody knows which one is late

Requests arrive by e-mail, by phone and in chat. Who will answer, how long the customer has been waiting and whether the promised time has passed only come out when the customer calls again.

  • Two people answer the same request, or nobody does.
  • What was written to the customer and what the team discussed get mixed up in one e-mail thread.
  • Customers have to call to find out where their request stands.

How Neoli solves it

The ticket about to miss its target stands out

Set first-response and resolution targets on the project, in working days. The list shows each ticket's SLA state; at-risk and breached tickets are marked, so you know what to take first.

A list of support tickets with their SLA states, at risk and breached

The reply to the customer and the internal note on one ticket

Write the reply to the customer and the team's own note on the same ticket; the customer never sees the internal note. The ticket's whole history, files and linked items stay in one place.

A support ticket with a reply to the customer and the team's internal note

Customers in their own portal

Customers open requests in the portal, read the replies there and see only their own tickets. They no longer need to call to ask how things stand.

The customer portal: a customer's own requests and their states

What comes set up

States

  1. New
  2. In progress
  3. Waiting for customer
  4. Resolved
  5. Closed

Item types

  • Ticket
  • Request

Also ready

  • Incident and request templates
  • First-response and resolution targets in working days, from the work calendar
  • Ready views: by phase, my open work, due this week, overdue, board by owner

Where do these setups come from?

Each setup is a starting point drawn from how that kind of work commonly runs: the state names, item types and steps come from the words those teams use. It does not know your process, so everything in it is yours to change. Tell us what is missing at destek@neoli.app and we improve the setups.

Frequently asked questions

How do customers file a request?

People you invite as customers file requests in the portal and see only their own; requests e-mailed to the project can become tickets too.

How are SLA times counted?

You set first response and resolution targets by priority in the project's settings; the clock runs in the work calendar's hours and stops in waiting states such as "Waiting for customer".

Can a reply and an internal note get mixed up?

No. Your reply goes to the customer; a comment you write as an internal note is never shown to them.

Other industries

Your kind of work is not listed?

Start with the General setup: it comes with phases, tasks and milestones; you add your own states, item types and fields. When it fits, keep the project as a template.

Start with the General setup

Bring your team's plan into one place

Open your workspace in a minute and invite your team.

Start free