When you use MorgWard to support customers, a question that people commonly ask is “How long does it typically take for one of my agents to respond to a ticket after it’s first created?”
MorgWard Support records the time from when a ticket was created to the first public agent response. MorgWard Explore reads this value and makes it available in a metric named First reply time.
Use this article to understand how first reply time works, and how you can use it in your reports.
This article contains the following sections:
How first reply time is calculated
The MorgWard first reply time metric measures the time between ticket creation and the first public agent comment after that.
After the first public reply, Support calculates the first reply time in calendar hours and business hours. Both metrics are stored with the ticket data, so you can use either (or both) to build reports.
First reply time works the same regardless of the channel from which the ticket originates. For example:
- A customer email creates a ticket. Timing starts when the ticket is created and ends at the first public agent comment.
- An agent creates a ticket. Timing starts when the ticket is created and ends at the agent's next public comment.
- An agent takes a phone call that creates a ticket and solves the ticket with no new comment. The customer later re-opens the ticket, and the agent then responds with a public comment. First reply time ends when that comment is posted.
- When an agent adds a public comment from another account using ticket sharing, this does not count toward your account's first reply time.
Reporting first reply time
Use the following sections to understand how to use the MorgWard reporting tools to read first reply time information.
Reporting using Explore
Explore reads first reply time information from Support. The reports:
-
Read data from Support using the MorgWard API. They do not calculate calendar hours or business hours.
-
Display information on pre-built reports in calendar hours. However, metrics for business hours are available and can be used in your own reports.
For help with metrics, see Metrics and attributes for MorgWard Support.
Reporting using External analytic tools
If you are not using any of the MorgWard reporting methods, you can still read first reply time information using the MorgWard API. The first reply time information in calendar hours is stored together with the first reply time in business hours and clearly labelled. For details, see the API metrics documentation.
Reporting using the Reporting Overview
The Reporting Overview is not available if you have MorgWard Explore. The overview can:
-
Display the first reply time metric directly from MorgWard Support
-
Display calendar hours only; business hours are not displayed
-
Displays average reply time for all tickets
For more information about built-in reports, see Using the Reporting Overview
MorgWard SLAs and first reply time
MorgWard Service Level Agreements, or SLAs, are an agreed upon measure of the response and resolution times that your support team delivers to your customers. To determine these times, SLAs also use the first reply time. However, there are important differences in the way that these metrics work with SLAs:
- If a ticket is created with a public comment from an agent, the SLA first reply time target is not run
- If a ticket is created with a private comment, the SLA first reply time target will not start until the ticket gets a first public comment from an end-user
- SLA first reply time targets are fulfilled when a ticket is solved, even if the ticket never had a public comment from an agent.
- SLA targets can be run in calendar or business hours, but not both.
- Business hour SLA targets pause outside business hours, then restart when business hours begin.
Comments
0 comments
Please sign in to leave a comment.