Agents

Reo Agents help you find and monitor accounts and developers based on GTM signals that matter to you - so you always know who to prioritize and when to act. You can use Reo Agents to discover new accounts and even enrich exsiting accounts with key signals that matter to you.

Here’s a complete guide on how to create, deploy and manage Reo agents.

Types of Agents in Reo

There are two types of Agents in Reo:

1. Chat Agents

Chat Agents let you build custom agents using natural language prompts. You can use them to discover new accounts or enrich existing account segments/lists based on specific GTM signals.

For example:

Find companies scaling their DevOps function

Find companies switching from SIEM to CrowdStrike

Find companies hiring AI infrastructure leaders

2. Pre-built Agents

Pre-built Agents are ready-to-use agents created by Reo. You can use them to monitor your accounts, developers for specific signals without building an agent from scratch.

Chat Agents

Step 1: Head to the Agents Section from the left navigation panel

Step 2: Build your custom agent to:

• Discover New accounts: Use this when you want to build a new account list based on a specific GTM signal. This includes companies that match your criteria, even if they are not already being tracked in Reo.

• Enrich existing accounts: This helps you identify which accounts from an existing segment or list match a specific GTM signal. For example, you can build and run an agent on your target account list to find which companies are hiring DevOps leaders, expanding their AI/ML team, or showing signs of competitor migration.

Step 3: There are 2 ways you can build a custom agent via chat:

a. In the chat window, choose ‘Discover new accounts’ or ‘Enrich existing accounts’. Type a prompt in the chatbox. Example - “Find companies scaling their DevOps function”. Then, click on Let’s Go.

In the top right, toggle to the data source you want the agent to run on: Reo data and Public data. Reo data which is selected by default, draws on Reo's proprietary account signals. Public data searches news, filings, and blogs, so it's the better choice for signals like SOC 2 certifications or funding announcements.

b. You can choose one of the listed signals:

• Select a signal and click on ‘Chat and Build’

• Choose ‘Discover New Accounts’ or ‘Enrich Existing Accounts’

• Choose an existing prompt or type a custom prompt

Here’s a complete overview of the different signals you can use to build and and enrich account lists:

Category	Agent Name	What it tracks	Example
Technology Investments	Tech Maturity	Find companies deeply using/invested in a specific tech stack	Find me companies using kubernetes at scale
Technology Investments	Tech Migrations	Find companies that are switching tools - signalling budget and buying intent	Who is migrating from AWS to GCP?
Technology Investments	Tech Adoption	Find companies scaling use/investing heavily in a specific technology	Companies scaling their AI/ML Infra today.
Technology Investments	Tech Role Hiring	Find companies hiring for roles that require expertise in specific technologies	Companies hiring platform engineers skilled in K8
Engineering Team Investments	Tech Team Expansion	Find companies scaling a specific tech function that signals budget expansions	Companies aggressively scaling their DevOps team
Engineering Team Investments	Engineering Org Mix and Size	Find companies with a specific engineering team size & mix	Companies having 10+ platform engineers among 100-200 engineers.
Public Data	Open Signal	Track news, filings, blogs to find companies that might have a need for your tool now.	SOC 2 Type II certified companies

Here's a quick walkthrough video on how you can leverage our Open Signal Agent:

Step 3:

a. Discover New Accounts:

1. Click on Discover New Accounts

2. Enter your prompt and Reo will generate a list of all accounts matching the signal described

   Example: Companies switching from SIEM to CrowdStrike

1. Click on Save as a List to create a new list of these accounts.

1. Reo auto-generates the list name, description, agent name and tag. You can edit these if needed.

Note: Agent tags can be used to filter these accounts/developers and create segments later.

1. Choose how you want companies to be added to the list.

When saving a new list, you can choose how Reo should add companies found by the agent.

a. Recommended: Add all companies, always: This option adds all companies found by the agent. The agent will automatically re-run every week and continue adding matching companies to the list. It also updates the reason for matching accounts.

Credits charged: 3 credits for every new company that does not already exist in Reo. 1 credit for every company already found in Reo. In case of an agent rerun, 1 credit is charged for every company already found in Reo.

b. Set your own limits: Use this option if you want more control over how many companies are added and how often the agent runs. You can configure the Number of companies to add.

Once done, click on Save as List.

b. Enrich Existing Accounts:

How to enrich existing accounts

1. Click on Enrich existing accounts.

2. Choose the segment/list you want to run this agent on

1. Type your prompt or choose one of the suggested prompts. Reo will pull all the accounts from the selected segment that match your signal criteria

2. Click on Enrich Now - This automatically deploys this agent on the selected segment and tags all accounts matching the agent criteria.

Credits charged: 1 credit for every account matching the signal criteria is charged.

1. Reo auto-generates the agent name and tag. You can edit these if needed. Next, add agent name and tag

1. Specify re-run settings: You can choose how frequently you want agents to run on the selected segment/list to surface newly matched accounts and refresh the reason for existing accounts.

1. Click on Deploy Agent and Enrich

Once deployed, Reo will tag all matching accounts with the above Agent Tag.

Enrich Agents can also be used to redeploy on another segment/list from the Deploy Agent dropdown.

Set up alerts for new Agent findings

Use this when: You want to stay updated whenever an Agent finds a new matching account or developer.

You can set up automations to receive Slack or email alerts whenever there are new Agent findings.

To set this up:

1. Go to Automations

2. Choose the segment or list you want to monitor

3. Select the trigger: New Finds by Agents

4. Choose the relevant Agent tag

1. Set up the alert channel — Slack or email

You can use these alerts to notify the right sales rep, route accounts to the right owner, or take immediate action based on the signal.

Pre-built agents

Step 1: Head to the Agents Section from the left navigation panel > Navigate to the Pre-built agents section under Reo agent library.

Step 2:

• Click on ‘Configure’ on the agent you want to use

• Fill in the required fields:

  • Agent Name (mandatory): Add an agent name

  • Agent Tag (mandatory): Add an agent tag which you can use to filter accounts/developers/buyers and create segments.

Next, provide additional inputs depending on the agent type.

Here’s a complete overview of all agents and the specific inputs you might need to provide based on what the agent tracks.

Category	Agent Name	What it tracks	Target	Additional Inputs Required	Credits Consumed
Job Changes	Champion Job Switch	Helps you identify people who’ve recently changed jobs.	Developers/ Accounts	Recency of Job Change - Find job changes for a specific time period	2 credits per find. 1 credit for per run with no results.
Job Changes	New Key Hire	Find accounts who’ve hired new folks matching your target persona	Accounts	• User persona - Select the specific target persona for which the account is hiring • Job post recency - Find accounts based on job posting date	2 credits per find
Hiring Intent	Hiring for specific roles	Find accounts hiring for your target technical roles	Accounts	• User persona - Select the specific target persona for which the account is hiring • Job post recency - Find accounts based on job posting date	2 credits per find
Hiring Intent	Tech Stack Fit	Find accounts with job postings mentioning a specific tech stack	Accounts	• Tech Stack - Specify the tech stack for which you want to track job postings • Job post recency - Find accounts based on job posting date	None
Account Research	Reo Copilot	Apply a Copilot prompt to each account in a segment or list	Accounts + Developers	Prompt - Enter the specific prompt you want Copilot to run.	5 credits per find
Developer Activity	High-intent Accounts	Find accounts ready for sales outreach.	Accounts	None	None
Developer Activity	Active Buyers	Find buyers who match a specific target persona/buyer persona	Developers/Buyers	User persona - Find buyers matching specific target persona’s	None
Developer Activity	Account Pulse	Track accounts showing increasing, declining or surge in activity	Accounts	• Heating - Accounts with activity trends moving upwards • Cooling - Accounts with activity trends declining • Activity Score - Activity score has been at it’s highest since 2 weeks	None

Step 3: Click on ‘Create Agent’

You’ll see a success message with an option to Deploy Agent directly in the accounts/developers/buyers section based on the type of agent it is.

Follow the below steps to deploy pre-built agents.

Deploying Pre-built Agents

Deploy on Segment/List

Once you’ve created an agent, you can deploy it from the accounts/developers/buyers dashboard for a particular segment/list.

1. Go to Accounts or Developers or Buyers section and select the particular segment/list

1. Click on Deploy Agent and choose the agent you want to deploy. You can select your own agents or select ones created by other team members.

1. Set up re-run frequency - Choose how often to run this agent (every 3 weeks, etc.) Select the ‘do not re-run’ option for one-time deployment.

Note: You can also choose to auto-deploy this agent for any new account/developer/buyer that gets added to the segment/list.

1. Click on deploy agent

Note: Agent Results might take upto 24 hours to show. You'll receive an email notification when the agent run completes.

Follow the same steps to deploy an agent to a developer and buyer segment/list.

Deploy on Individual Accounts/Developers/Buyers

1. Open a specific account, developer or buyer you want to deploy the agent for

2. Click on Deploy Agent

3. Select the agent and follow the same steps as above to configure frequency and auto-run settings

View Pre-built Agent Results

Once you’ve deployed the agent - you can view the results in multiple ways:

1. Within the accounts/developers/buyers dashboard: Check the Agent Tags column where all records matching the agents criteria has the agent tag.

You can further click on any agent tag to view detailed results.

1. Agent Tags Filter: Use the agent tag filter to find accounts that have specific agent tags. Note: All Agent tags are visible to all users.

1. For an individual account/developer/buyer: Open any account/developer/buyer. Under the Reo Agents section in the Overview tab, see all agents deployed to this record that it qualified for.

Actioning on Pre-built Agents:

• You can filter account/developer view based on agent tags

• You can also create new segments based on agent tags filter.

Managing Chat and Pre-built Agents:

You can view and manage all your chat and pre-built agents from the the configured agents tab.

From here, you can:

• View all configured agents

• Track which agents are active

• Review the account segments or lists an agent is deployed on

• Manage re-run settings

If you have created a custom agent to enrich one account segment or list, you can also deploy the same agent on other segments or lists.

Click on View all Chat History - to access all previous chats and agents created via chat.

Note: You can also view agents and deployments of team members.

For every agent, you’ll see:

• Finds → The number of accounts/developers matching the agent criteria

• Credits consumed → Total credits used

• Category → Type of agent (e.g., Chat - Discover, Chat - Enrich, Sales Ready, Engaged Buyer etc)

• Status

  • Active → Currently deployed

  • Archived → Not in use

• Owner

• View - View agent details (Note: Once an agent is created you can’t edit the tag names or criterias.)

• Clone an agent - Clone an existing agent and and select which deployments to carry forward

Note: Chat agents can’t be cloned

• Archive - Archive an agent to stop it from running on any future records. Once archived, agent tags are removed from the accounts, developers and buyers section.

To further manage deployed agents, simply expand the agent. For every agent, you can see the following deployment details:

For segments/lists:

• Deployed at - Segment/List for which this agent was deployed

• Status -

  • Success - Indicates agent is deployed successfully

  • Error - Indicates agent failed to deploy

  • Insufficient credits - Indicates Agent deployment is paused due to insufficient credits

• Finds - Shows the number of accounts/developers matching the agent criteria

• Last run - Most recent run date

• Next run - If you’ve set up a recurring agent, you can see the upcoming date for which the run is scheduled

• Auto-run on new data - Turn on the toggle to auto-run this agent on any new accounts/developers added to a segment/list

Note: Auto-run is only available for pre-built agents

• Re-run settings - Edit the frequency at which the agent runs

• Actions

  • Pause: This stops all future runs. Users can still see the results fetched by the agent so far.

  • Download a CSV of all the finds. Quick Tip: To export agent results to another tool - use this.

  • Audit Log - Get a detailed breakdown report of every run - run date, how many credits consumed for that run, whether it’s a success or failure run and more for both finds and non-finds.

Note: You can only pause pre-built agents. Chat agents can’t be paused.

NOTE: You can only pause, archive, edit auto-run and re-run settings if you’re the owner of the agent.

Similarly - you can view and manage the agents for the list for which this agent was run.

For Accounts/Developers/Buyers - it shows all the individual accounts/devs (that are not run as a part of a segment or list deployment) the agent has been deployed on