Choose your signal agents

Agents are the part of Embers that goes and looks. Four of them are available, they all run on the same 24 hour cadence, and they all feed the same ranked queue.

The four agents

1. Post engagement

   Watches the posts published by a profile you added with the Own role and collects the people who reacted to or commented on them. This is the default signal for anyone who posts regularly, and it is the one the onboarding preview uses.

2. Comment engagement

   Watches the comments an Own profile leaves on other people’s posts, and collects the people who replied to or reacted to those comments. It is the agent that pays off when you get more reach commenting under big accounts than posting yourself.

3. Watchlist

   Watches any public profile and collects the people who engage with it. When you add a profile you pick a role: own, competitor, influencer, investor, teammate, advisor, client founder, or other. An Own entry spawns the post and comment agents above and is excluded from leads. Every other role rides along as a label on the resulting leads and lets you filter the analytics, and it does not change what public data is collected.

   A watched profile can be a LinkedIn profile or a company page URL.

4. Keyword tracking

   Watches for people publicly posting about the phrases you care about. The agent takes a list of keywords rather than a single phrase. The modal suggests three kinds that work: pain points you solve, your category or competitor names, and buying intent phrases such as “looking for a CRM”.

Adding one

Open AI Agents (/agents), headed “Monitor and manage your AI agents”, and use Add Agent. If no profile is on the watchlist yet, the modal asks for one first, with a role chip. Post and comment agents exist once per Own profile and disappear from the picker after you add them, and the watchlist option is hidden once you are at your plan limit.

Each agent card then shows its status, a live banner while a scan is running, the result of the last scan, how many leads it has produced, and an expandable scan history of up to ten runs. Pause and resume are on the card.

The 24 hour cadence

Agents scan on a 24 hour cadence rather than continuously. Two consequences are worth planning around:

• Once a day is the right rhythm. Checking Embers hourly will not surface anything new. Working the priority queue once a day will.
• A new agent has a first run to do. Adding a watched profile kicks off a scan of that profile’s public history, and the dashboard shows the progress of that backfill while it runs.

Which agents need a paid plan

Free is enough to see the product work on one watched profile. It is not enough to run the signal sources on a schedule, because the limits that feed them are zero or one. Caps are per workspace, and every self-serve plan is one workspace:

In practice that means keyword tracking and a real watchlist are Solo and above. Post engagement and comment engagement are the two to turn on first if you post, because they read activity you already generate. If you do not post, skip your own profile and start with a watched competitor or influencer.

Choosing between them

• You post consistently. Start with post engagement, and nothing else, for a week.
• You comment more than you post. Comment engagement will out-produce post engagement, and the comments screen shows which threads and which authors pull the most ICP engagers back to you.
• Your buyers cluster around someone else. Put that person on the watchlist with the role that describes them honestly.
• Your buyers announce the problem in public. Keyword tracking, with phrases a buyer would type, not phrases a vendor would.

Most accounts do not need all four. Two well chosen agents produce a queue you can actually work.

Related