Panda CRM

The response time is written in the contract; whose screen shows the countdown, nobody knows

The SLA Management module counts the response and resolution time promised to each customer ticket by ticket, warns you about tickets nearing their deadline and runs the escalation rule. Performance is reported by customer and team.

SLA management
In short

SLA Management is the Panda ERP CRM module that counts the response and resolution time promised to the customer on every support ticket and runs warnings and escalation for tickets nearing or past their deadline. A customer with a special agreement gets a different time; SLA performance indicators are reported by customer, team and category. It uses the same ticket record as the Help Desk and After-Sales modules.

How is this work done today?

  • The time in the contract is not in the system

    Each customer's maintenance contract has a different response time; the support team looks in the contract folder to see how many hours were promised to which customer.

    1 support specialist × 20 minutes / ticket
  • A missed deadline is noticed when the customer complains

    The ticket stays open, nobody watches the clock; the breach is discovered through a penalty clause or a lost customer.

    1 manager × 1 hour / week
  • The SLA report is prepared by hand

    For the performance report to send to the customer at month end, the ticket list is dumped into Excel and the times are calculated by hand.

    1 person × 3 hours / month

How does SLA management work?

  1. 1

    The SLA is defined

    Response time, resolution time and working hours are defined by customer group or contract. A customer with a special agreement gets a different time.

  2. 2

    The clock starts when the ticket opens

    A ticket opened in the Help Desk is matched to the SLA rule; the remaining time shows in color on the ticket card and in the list, and hours outside working time are not counted.

  3. 3

    Warning and escalation

    A notification goes to the owner as the deadline nears and to the manager when it is missed; by the defined rule the ticket is handed to a higher level.

  4. 4

    Performance is reported

    SLA compliance rate, average response and resolution time are reported by customer, team and category; a period report goes to the customer as a PDF.

See how SLA management would work in your business

Tell us briefly about your process and we will walk through the screens with your own example.

  • Reply the same business day
  • 15+ years of experience
  • 90 client businesses

SLA management features

SLA management: Customer-based SLA
  • Customer-based SLA

    SLA levels such as standard, priority and special agreement; the time from the contract is written to the customer card.

  • Response and resolution time

    Separate clocks for first response and resolution; different times by priority and category, working calendar and holiday definitions.

  • Automatic warning

    Email and mobile notification to the owner as the deadline nears; you set the warning threshold as remaining time.

SLA management: Escalation rule
  • Escalation rule

    A ticket past its deadline is handed to the team lead and then the manager; person and waiting time are defined for each level.

  • Pause

    The clock stops while information is awaited from the customer; the waiting reason and duration are kept in the record and shown separately in the report.

  • SLA indicators

    SLA compliance rate, average response and resolution time, breach count; by customer, team and category on screen.

  • Customer report

    The SLA performance report by period goes to the customer as a PDF, in the format of the contract annex, and is also visible in the portal.

  • Module link

    The same ticket record as the Help Desk, After-Sales Services and Service modules; time definition from the Contract module.

What does Panda AI add to SLA management?

The Customer Service Agent is the Panda AI agent that answers order, shipping and invoice questions 24/7 on WhatsApp and e-mail and hands over what it cannot solve to the right person.

  1. Today A rep looks in the ERP to check an order’s status With the agent Order and shipping status answered 24/7
  2. Today Out-of-hours messages wait until morning With the agent Hands over what it cannot solve to the right person
  3. Today Complaints can get lost before they are logged With the agent Every request is logged and reported

Jobs it takes on

  • Order, shipping and invoice queries
  • 24/7 answers on WhatsApp and e-mail
  • Logging requests and handing them to the right person
  • Starting return and complaint processes
  • Frequently asked questions knowledge base
  • Request and satisfaction reports

The agent prepares, a person approves. Anything that posts a record or sends something outside the company goes through your approval.

Explore Panda AI agents

Frequently asked questions about SLA management

What is an SLA and which businesses need one?

An SLA is a service level agreement: the commitment on how fast the customer gets a response and how fast the problem is resolved. It is needed by any business with maintenance contracts, such as software, service, medical devices and technical support. Even without a commitment, it is used as an internal target.

Can a different time be defined for each customer?

Yes. The default SLA comes by customer group; for a customer with a special agreement the time in the contract is entered separately. Different times can also be defined by priority and category: short for an urgent fault, long for an information request. The definition shows on the customer card and the ticket screen.

Does the clock run outside working hours?

A working calendar is defined; hours outside working time and holidays are deducted from the clock. For a team that gives round-the-clock support, an SLA without a calendar can be defined. While information is awaited from the customer, the clock is paused; the waiting time is shown separately in the report and the pause reason stays in the record.

How does escalation work?

A warning goes to the owner as the deadline nears. When it is missed, the ticket is handed to the team lead and then the manager by the defined rule; the person and waiting time at each level are your definition. Escalation is written to the audit log; a person explains the situation to the customer.

Can SLA be used without the Help Desk?

The SLA module works on the ticket record; the ticket comes from the Help Desk, After-Sales Services or Service module. At least one of these modules must be on. If the Contract module is on, the SLA time comes from the contract on its own and is not typed in.

How is the SLA report given to the customer?

At the end of the period, an SLA compliance rate, ticket count and average response and resolution time per customer are prepared as a PDF report and are also visible in the customer portal. The report template is arranged to match the contract annex. The support manager approves the sending.

Which indicators are tracked?

SLA compliance rate, breach count, average first response time, average resolution time, pause time and escalation count. Indicators are reported by customer, team, specialist and category by date range; they appear as a dashboard in the Dashboard module.

What does the agent do in SLA management?

The remaining time of open tickets is watched continuously; a ticket nearing its deadline goes to the person concerned and the manager, and tickets at risk of a breach are listed in the morning. A person makes the escalation decision and explains it to the customer; the agent promises the customer no times.

See SLA management with your own data

Describe your process in a few sentences and we will show you the modules that fit.

  • 15+ years of enterprise software experience
  • In the cloud or on your own server
  • Processes compliant with KVKK (Turkey's data protection law)

Last reviewed: · Panda Yazılım product team