Support manager
- Desks, teams and queues in one place
- SLA report by desk and period
- Surveys on resolved tickets
Run support desks with queues, SLAs and knowledge, and handle incidents, problems and changes in the same system as the rest of your business.
From the first message to a resolved ticket, with SLAs and an audit trail at every step.
Managers, agents and IT teams work the same tickets.
Real screens from Fynd ERP, shown with demo data for a fictional company.
Every ticket with its type, queue, priority, status and assignee in one list. Open one to see its incident details, SLA timers and the conversation.
Follow one ticket from the first message to the fix. Each step happens in Fynd ERP.
A message from a connected channel becomes a ticket on the right desk.
Rules set the type, priority and queue, and SLA timers start against business hours.
The agent sees the customer and their recent orders on the ticket.
The ticket is raised as an incident, and it is linked to a problem opened for the root cause.
The customer gets the reply and a satisfaction survey.
The parts of a service desk support teams ask about most.
Set first response and resolution targets for each desk, measured against its business hours. Timers show on every ticket and the SLA report shows where targets were met or missed.
Declare a major incident from a ticket when many people are affected. Link incidents to a problem to track the root cause, so the same issue does not keep coming back.
Plan changes and see them on a shared change calendar before they go ahead. Link each change to the problem or work item it fixes.
Publish articles your agents and customers can use to solve common issues. Agents answer faster with articles and canned replies close at hand.
Agents see the customer's orders and history, and fixes reach the teams that own them.
Tickets, queues, desks, teams, channels, SLAs, business hours, rules, canned replies, a knowledge base, surveys, reports, AI assistance and incident, problem and change handling.
Yes. Each desk has its own teams, queues, ticket types and SLAs.
Yes. You can manage incidents, problems and changes, and plan changes on a shared calendar.
Response and resolution targets run against each desk's business hours, and the SLA report shows where targets were met or missed.
Yes. Tickets link to the customer and their orders, which sit in the same system.