Naateq
  1. Home
  2. Learning Centre
  3. Getting started
  4. Your first week in Naateq — what to look at

Your first week in Naateq — what to look at

Four numbers at the top of the dashboard carry your first week: automated resolution rate, escalation rate, first-reply time and pipeline value.

Getting started · 5 min read

The Naateq dashboard: automated resolution rate, escalation rate, first-reply time and pipeline value in SAR, with the week's conversation curve beneath them.
The figures in the image are demo data. What matters is their direction across the week, not their value on a day.

Open this screen in demo mode

The first time you open the dashboard you will see four numbers along the top and a curve beneath them. These four are not dashboard decoration — each answers a question you ask yourself in your first week, and three of them move fast.

This lesson tells you what to look at, when the numbers start to mean something, and which single number is worth acting on from day one.

The rule in two lines

In the first week do not chase the resolution rate — chase the reasons for escalation. The first is an outcome; the second is what you can fix today.

The four numbers

What each one is telling you

The dashboard's headline numbers and what they mean
NumberAnswers the questionWhen to worry
Automated resolution rateHow many conversations closed without you?Not early on — it needs a sample
Escalation rateHow often did the system come up short and call you?When it stays high after two weeks
First-reply timeHow long did the customer wait for a first word?When it exceeds a few seconds
Pipeline valueHow many riyals sit in quotes not yet closed?When it does not move for a full week

And the escalation rate is the only one directly fixable — the lesson that explains it is escalation rules.

The first week

Four steps that order your start

  1. 1
    Read ten whole conversations.

    Not the numbers — the conversations themselves. Ten are enough to see with your own eyes where the system answers well and where it stumbles.

  2. 2
    Write down every question the system escalated.

    That is your to-do list. Every line in it is a missing knowledge entry, not a fault in the system.

  3. 3
    Add the entries, then wait two days.

    A change does not show its effect immediately — it shows only in the conversations that follow it.

  4. 4
    Compare week to week, not day to day.

    A day is a small sample that swings on one conversation, so the system looks erratic when it is steady.

Warning

The number that deceives you

A very high resolution rate on day one is not good news.

Usually it means conversations are few and their questions easy, or that the system is answering questions it should have escalated. A system that «always answers» is more dangerous than one that hands over a lot — because the second annoys you, and the first annoys your customer without you knowing.

And once the picture settles, the next step is building the knowledge base — it is what moves all four of these numbers the most.

Frequently asked

Which number matters most in the first week?

The escalation rate. It tells you how often the system came up short and handed over to you — and it being high in the first week is normal: it means the knowledge base is incomplete, not that the system is broken. Every escalation is a question worth adding.

When do the numbers start to mean something?

After roughly a hundred real conversations. Before that the sample is too small to decide on — a figure drawn from ten conversations swings ten percent on a single one.

Next lesson

All Learning Centre lessons