# Use Analytics to decide what to do next

Read the numbers in context, spot work waiting for you, and find where your outreach is getting stuck.

By Salman · 2026-07-06 · tutorials

Canonical: https://reacherx.com/blog/read-your-reacherx-analytics

A dashboard is useful when it changes what you do next. If it only tells you △ Agent has been busy, it hasn't told you enough.

Open Analytics in ReacherX and start with the active workspace and date range. A hiring workspace and a customer workspace have different goals. Last week's activity and today's activity are different sets of work.

## Check whether people are getting through

The overview includes new people found, response rate, pending approvals, and outreach issues. It also shows processing states such as pending, qualified, ready, and disqualified.

* **Pending**: found, but not yet checked for fit.
* **Qualified**: passed the system's fit checks for your audience. It doesn't mean they have agreed to talk, buy, or join.
* **Ready**: qualified, with background gathered, so a plan can be prepared.
* **Disqualified**: didn't pass the fit checks and has been ruled out.

Read the count under a rate. One reply from two people and fifty replies from a hundred people can produce the same percentage, but give you very different amounts of evidence.

Interactive demo: Read a workspace’s analytics. See who replied and which outreach led to a conversation.

## Find the next useful action

| What you see                          | What to check next                                  |
| ------------------------------------- | --------------------------------------------------- |
| Many new people, few relevant matches | Read examples and revisit the audience requirements |
| Good matches, many pending approvals  | Review the plans or messages waiting for you        |
| Outreach issues rising                | Open the affected work and read the failure reason  |
| Conversations start but go nowhere    | Read the replies and reconsider the invitation      |

A count alone doesn't tell you the cause. Too few qualified people could mean the audience is too narrow, the searches are poor, or the available information isn't enough. Read a few actual results before changing your whole setup.

## Compare like with like

Use the same workspace and a comparable time range when checking progress. Reporting uses the workspace's time zone, so day boundaries may differ from a teammate's local clock.

Some cards describe activity during a period; others describe the current state of people found in that period. Read the labels. Don't add different cards together and assume they are consecutive steps taken by exactly the same people.

Keep progress stages accurate when you learn something from a conversation. The app can only report the events and states it has recorded. A phone conversation outside ReacherX won't explain itself to the dashboard.

## Look behind the numbers when needed

Analytics helps answer “What is happening with my work?” [Agent observability](/blog/understand-agent-observability) helps answer “What has △ Agent been doing?”

Use it when you want to inspect searches, evaluated lessons, or a particular processing event. It gives you a way to investigate instead of repeatedly changing your prompt without knowing what went wrong.

Try one change at a time: improve an audience requirement, clear waiting approvals, or make your invitation clearer. Then review actual people and conversations alongside the numbers. A busier △ Agent is only useful if it is helping with the job you came to do.