Monitor the progress of Revenue agent

Created by Aneta Dolezelova, Modified on Fri, 13 Mar at 6:11 PM by Aye Myat

Objective

The purpose of this article is to provide Outreach users with an overview of how to monitor Revenue Agent activity. The Agent Overview feature helps users track progress by offering a summary of the Agent’s actions and a detailed log of both its activities and any changes made to the Agent itself, such as activation, updates, or deactivation.

Monitor the Agent's activity

You can monitor the Agent’s activity by selecting the Agent and navigating to the Overview tab. The page includes the following sections:

Activity summary

The Activity summary provides a high-level overview of the Agent’s progress from its start to the present day. All items are clickable and open a list view of the specific accounts or prospects being reported. These views help you explore details and resolve any issues that may be blocking the Agent’s progress.

Example of how this view supports corrective action: The Activity Summary lists all reasons why the Agent skipped certain accounts. For example, if multiple accounts were skipped because they are missing a domain, you can click the corresponding row to open a pre-filtered list of those accounts. From there, you can use standard account list actions — for instance, export the accounts, add the missing domains, and re-import them. Once corrected, the Agent will automatically pick them up again.

Activity alerts

This section highlights issues related to agent setup. At present, it only reports enrichment-related problems. If enrichment is disabled, you’ll see an alert here.

Activity

This section is the Agent’s activity feed, providing a detailed view of its processing. It shows what the Agent did and when, as well as any actions performed on the Agent itself, such as creation, activation, updates, or inactivation. You can use filters to narrow the view by event type or time frame. Some events are clickable and open a modal with additional details.

Agent Activity feed: What’s stored and since when

The activity feed stores the Agent’s activity for the past 30 days. Activities that occurred outside this timeframe will not be displayed.

What activity is captured in the Activity feed

Filter	Event name	Details
EVENTS RELATED TO AGENT PROCESSING
Accounts added to agent	Agent picked up [SUM] targeted accounts for the first time and queued them for processing.	This event is fired when an account is newly added to the agent.
Accounts processed	Agent processed [SUM] targeted accounts and is now targeting prospects within them.	The event occurs after an account is first added to the agent, or later if the agent reprocesses the account for prospect identification.
Accounts skipped by agent	Agent skipped [SUM] accounts. Reason: Accounts had 0 existing prospects matching targeting criteria	This will show accounts that were skipped because no prospects matched the Agent’s targeting criteria. Note: The Agent activity log does not include accounts that were skipped before processing, such as: Accounts with 0 prospects (empty accounts). Accounts that couldn’t be enriched when enrichment is required to obtain targeting signals (e.g., no domain, enrichment failed, or not matched in the data provider). Accounts that can’t be matched in the data provider when matching is required to create new prospects (e.g., no domain or not found in the data provider). You can find information about these excluded accounts in the Activity Summary.
Accounts marked for enrichment	[Variant 1] Agent marked [SUM] accounts for enrichment. [Variant 2] Agent marked [SUM] accounts for enrichment to find accounts with selected targeting signals	[Variant 1] This event is triggered when NO targeting signals are used for account targeting. [Variant 2] This event is triggered when targeting signals are used for account targeting. In this case, it is one of the first events the Agent triggers. The Agent marks larger batch for accounts for enrichment to obtain signals from the third-party data provider, then adds the accounts that match those signals to the Agent, respecting the daily account quota.
Accounts targeting complete	Agent reached the end of the target account list and will now reprocess it to find newly matching accounts and additional prospects from those already added.	The Agent has processed the full list of accounts: eligible accounts were added, and ineligible accounts were skipped. Once the Agent reaches the end of the list, it continues to search for prospects within the accounts already added. It also keeps looking for other accounts that match the targeting criteria. How often is this event triggered? This event is triggered each time the Agent processes the full list of accounts. However, to avoid clutter in the Activity timeline, it is displayed only once per day, even though the Agent may check for new accounts multiple times throughout the day. If the event occurs immediately after the Agent is launched, it indicates that the daily account quota set in the throughput settings is lower than the actual number of accounts the Agent can target. If the event triggers every day without any prospect events occurring in between, it means the Agent can no longer identify prospects, signaling that it may be time to deactivate the Agent.
Existing prospects added	Agent added [SUM] existing prospects based on targeting criteria	Existing prospects were added to the Agent.
Existing prospects marked for enrichment	Agent marked [SUM] existing prospects for enrichment	Agent mark existing prospects for enrichment.
New prospects created by agent	Agent found and added [SUM] new prospects and marked them for enrichment	Agent created new prospects (name surname) and marked them for enrichment to get relevant data.
Prospects added to sequence	Agent added [SUM] prospects to the sequence	Agent added prospects to sequence.
Prospects failed to be sequenced possibility to filter per single failure reason	Agent couldn’t add [SUM] prospects to the sequence	This event is shown in case there are legit reasons, why prospects could not be added to the sequence. Upon clicking on the event, you can see the specific reason why the Agent couldn’t the prospect to the sequence. Filtering by specific failure reasons: When filtering by specific failure reasons, detailed logs are shown for each prospect. When all failure reasons are selected, the Agent shows aggregated counts of prospects per batch, reflecting how it attempted to add them to the sequence. Technical detail: To reduce log noise, certain failure reasons are recorded only once per day, even if they occur repeatedly throughout the day. The events that are surfaced once per day are related to waiting for enrichment: Pending prospect enrichment attempt Pending account enrichment attempt Pending successful prospect enrichment Prospect email missing – for new prospects, this is recorded once per day while waiting for enrichment. For existing prospects, the event is repeated every time the failure occurs.
EVENTS RELATED TO AGENT SET UP
Agent created	[Variant 1] Agent was created and saved as draft [Variant 2] Agent was created and activated
Agent activated	[Variant 1] Agent was created and activated [Variant 2] Agent was updated and activated	[Variant 1] Surfaces when agent was newly created and activated right away. [Variant 2] Surfaces when Agent was already existing and it got activated. (activation is counted as update)
Agent updated	[Variant 1] Agent was updated [Variant 2] Agent was updated and activated	Each update may include information about whether it affects the account processing order: If the update changes the targeting criteria, the Agent restarts processing the entire account list to reflect the new criteria. If the update does not involve targeting criteria, the Agent continues processing from where it left off without restarting. Note: At this time, specific updates to the Agent are not being tracked. This capability is planned for a future update.
Agent deactivated	Agent was deactivated