Skip to main content
All CollectionsForecastingTicket groups
Setting your Average Conversation Time (ACT) in queues
Setting your Average Conversation Time (ACT) in queues

How to find the right ACT for your queue

Jack Stewart avatar
Written by Jack Stewart
Updated this week

What's this number for?

As well as mapping the relevant tickets and calls you want to track, you'll also be required to enter some additional information about your agent's productivity and your targets. This is used to translate your forecasted contact volumes into a staffing requirement.

What's average conversation time (ACT)?

Average Conversation Time (ACT), is Dialpad WFM's version of Average Handle Time (AHT):

  • AHT (the industry standard) measures the time elapsed from open to close

  • ACT measures the total amount of dedicated time an agent spent on the contact, removing waiting or idle time. Learn more here

ACT is available for Aircall, Dialpad, Dixa, Intercom, Helpscout, Salesforce and Zendesk
Dialpad WFM will produce a ACT metric as soon as your customer service or CRM platforms are connected and your team are onboard and using schedules.


What number should I enter in my queue?

It's important to use the right number, based in the reality of how your team works, in order to accurately forecast your staffing and create efficient schedules.

For onboarding teams:

There are a few options available while you're getting started:

  1. Use the AHT from your customer service or CRM platform
    If your system offers this metric, then this is the easiest option.
    We recommend that you take an average for the last 30-120 days.
    Jump to our guides for finding this data in Dialpad, Dixa and Intercom.

  2. For voice: Manually calculate AHT using data in your customer service or CRM platform
    If your system does not offer AHT, then you can do a simple calculation using the data available. Take the total talk time and divide it by the total calls handled.

  3. Use an estimated number as a temporary measure
    If you do not have actual data to hand, then an estimation can suffice until the system starts providing you with your actual ACT. You can ask your team for an estimation of the time spent per contact or use some of our examples:

    1. Simple queries, e.g. Tier 1: around 300s (5m)

    2. Technical queries, e.g. Tier 2: around 600s (10m)

    3. Specialist queries, e.g. Tier 3: around 1200s (20m)

For live teams:

You can use the ACT metric for the relevant activity found in the performance page:

  • Go to your performance page and select all your teams, or the teams that work on this queue.

  • Select 'week' view

  • Select 'by activity' in the breakdown table and filter to the relevant activities linked to this queue.

  • Take note of the ACT across the last 4 - 12 weeks, depending on your preference.

  • Create an average of these numbers and enter that in the relevant queue.


Finding your AHT in your customer service platform or CRM

Dialpad

First navigate to the relevant Voice Contact Center in your Dialpad app.

Click the analytics button in the top-right corner.

You'll be taken to the analytics tab in the Dialpad Admin App. The report should be filtered to the corresponding Voice Contact Center. Ensure the report is showing 'Past 30 days'. Now, identify the 'average handle time' number below the chart.

This is the number to use in the queue for this Voice Contact Center.

Dixa

In Dixa, the average handle time (AHT) is referred to as "Assignment time".

  1. Go to the Dixa > Analytics

  2. Filter or find the relevant channel or queue you're using in your queue

  3. Find the Assignment time module and note down the assignment time for the entire conversation

  4. Go to Forecasts > Queues and go to the queue you're setting up

  5. Under channel type, select 'real-time' - this means we'll use the whole conversation to forecast with

  6. Now, enter the assignment time you identified Dixa and enter it into the average handle time field. (Note: this needs to be measured in seconds)


Intercom

  1. Go to the Intercom > Reports > Effectiveness

  2. Filter or find the relevant channel or queue you're using in your queue

  3. Find the Avg time from first assignment to close module and note down this number

  4. Go to Forecast > Queues and go to the queue you're setting up

  5. Under channel type, select 'real-time' - this means we'll use the whole conversation to forecast with

  6. Now, enter the assignment time you identified in Intercom and enter it into the average handle time field. (Note: this needs to be measured in seconds)

Did this answer your question?