# Measure: know the score: The Book

> Counting visits, questions, actions and failed tasks, and linking them to outcomes the business cares about.

Source: https://agentrelations.org/learn/book/measure

Part II: The six domainsChapter summary

What gets measured gets managed, and almost nobody measures agents. Web analytics count people and filter bots; server logs count requests without knowing who sent them. The result is that most organizations cannot say how many agents visited last month, what they wanted or whether they succeeded.

The Framework proposes a small set of numbers, counted the same way everywhere so organizations can compare themselves. Agent visits, counted per agent and per task rather than per page. Questions asked of the organization’s endpoints. Actions taken: bookings, purchases, applications. Agent-referred outcomes: the revenue or results those actions produced.

**Figure 9.** From visit to outcome. Failed tasks leave the funnel at every stage, and each one names a fix.

The most useful number, though, is the failed agent task: a task an agent tried to complete and could not. A blocked request, a missing fact, a form that needed a human, a checkout that timed out. Each failure names its cause and, usually, its fix. A weekly list of failed tasks is the best to-do list an Agent Relations team can have.

Measurement closes the loop. It shows which domain is weakest, whether last quarter’s work changed anything and where the next investment should go. It also turns Agent Relations from an act of faith into a line in the business review.

## Read the whole chapter

This is a summary. The full chapter is in the book, which is coming soon. One email when it is published.

Email

Email me when the book is published. Nothing else; ask us to remove you at any time.
