> ## Documentation Index
> Fetch the complete documentation index at: https://help.semji.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Proactive agents in Slack: get your SEO opportunities delivered into your channels

> The Content Opportunities agent, already available in Microsoft Teams, comes to Slack to push prioritized recommendations, powered by your Intelligence Hub data, directly into a team channel.

## At a glance

* **What you can do**: automatically receive a prioritized list of content opportunities (new content and optimizations) in a Slack channel, interact with the agent in the thread, and add topics to your editorial planning in one click.
* **Who it's for**: content managers, SEO project leads, marketing directors.
* **Why it matters**: your SEO insights arrive where your team already works, no need to open Semji.

## What changes for you

**Before**: accessing your content opportunities required logging into Semji, navigating to the Intelligence Hub, and manually cross-referencing position data, search volumes, and competitor rankings.

**Now**: the Content Opportunities agent, already available in Microsoft Teams, automatically publishes its recommendations in a Slack channel, at the frequency you choose, and lets your team react without opening Semji.

<Info>
  This feature requires the "AI Agents" add-on and an active Intelligence Hub on your workspace, as well as a Slack integration connected by an administrator.
</Info>

## What you will get

At each scheduled run, the agent posts a structured message (Block Kit) in the configured Slack channel with content creation opportunities (Content Gaps) and pages to optimize, each with an **Add to Planning** button. The agent then opens a thread to walk through the opportunity, where your team can reply to refine the analysis, ask a question, or switch to a different topic. The agent keeps the conversation context throughout the thread.

<Note>
  This first version only covers scheduled pushes to a channel: the agent starts the conversation, your team replies. Mentioning `@SemjiBot` or using a command like `/semji` to invoke the agent on demand is not available yet. Slack Connect channels, shared with external organizations, are excluded by default.
</Note>

## How to use it

<Steps>
  <Step title="Connect the Slack integration in Semji">
    In Semji, navigate to **Settings**, then **Integrations**, under the **Collaboration** tab. Next to **Slack**, click **Connect**, then authorize access from your Slack workspace.

    <Warning>
      This step must be completed by an administrator of your Slack workspace. Arrange this account before starting setup.
    </Warning>
  </Step>

  <Step title="Choose a dedicated Slack channel">
    Once the integration is connected, choose a channel dedicated to the agent rather than your team's general channel.

    <Warning>
      Slack Connect channels, shared with external organizations, are not available as a destination.
    </Warning>
  </Step>

  <Step title="Create and configure the agent in Agent Hub">
    Open **Agent Hub** in Semji, go to the **Agents** tab, and find the **Workspace agents** section. Select the **Content Opportunities** agent and configure:

    * **Destination Slack channel**: the channel chosen in the previous step
    * **Execution frequency**: weekly, monthly, or a custom schedule
    * **Filtering criteria**: topic clusters, page types

    A manual test validates the message format before you enable the schedule.

    <Tip>
      Always run this manual test before enabling the schedule, to check the format and relevance of recommendations in your channel.
    </Tip>
  </Step>

  <Step title="Interact with the agent from the Slack thread">
    At each run, the agent opens a thread in the configured channel. Reply in that thread to refine the search, ask a question, or switch to a different topic. The agent keeps the conversation context.
  </Step>
</Steps>

## Usage tips

**Match the frequency to your editorial rhythm.** A weekly run suits operational follow up, a monthly run suits a strategic review in a leadership meeting.

**Prefer a dedicated channel over the general one.** The history of recommendations stays readable, and the agent's messages don't get mixed into day to day conversation.

**Set topic clusters and page types from the first configuration.** Unfiltered recommendations quickly turn into noise. The narrower the scope, the more actionable each opportunity pushed to Slack stays.

## Going further

The same Content Opportunities agent exists for Microsoft Teams, with identical behavior. From Semji's editorial planning, find every topic added via Slack and assign them to your writers.

<Warning>
  Each scheduled execution consumes AI credits, and so does each agent response in the thread. Without an active Intelligence Hub on the workspace, the agent has no data to analyze.
</Warning>

<Columns cols={2}>
  <Card title="Proactive agents in Teams" href="/en/ai-agents/semji-teams-agent">
    The same Content Opportunities agent, for teams that work in Microsoft Teams.
  </Card>

  <Card title="Tutorial: create and configure a custom agent" href="/en/ai-agents/create-and-configure-your-custom-ai-agent">
    To build an agent that answers a need specific to your organization.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.