> For the complete documentation index, see [llms.txt](https://doc.autoreach.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.autoreach.tech/engagement-engine/engagement.md).

# Engagement Automation

While your account posts content, the Engagement Engine simultaneously interacts with relevant posts in your niche - liking, commenting, and following to build visibility.

## Engagement Types

### Likes

Target posts matching your niche keywords on X and LinkedIn.

### Comments and Replies

AI-generated contextual responses that reference the original post and add value to the conversation - not generic responses like "great post." These run as comments on LinkedIn and Instagram, and as replies to tweets on X. Comments and replies can be auto-approved (the Auto-comment / Auto-reply toggle) or held for your review in the approval queue.

### Follows / Connection Requests

Follow relevant accounts in your niche on X and Instagram, or send connection requests on LinkedIn.

## Keyword-Based Targeting

Engagement uses keywords derived from your offer and content pillars to find relevant content. Only posts matching your niche keywords are candidates for engagement. This keeps interactions focused and relevant rather than indiscriminate.

## Smart Targeting

The Engagement Engine prioritizes accounts where your interaction is most likely to be noticed and reciprocated, optimizing for visibility and response rate.

## Engagement and Outreach Are Independent

Engagement Engine activity and outreach sequences run simultaneously and independently. The Engagement Engine builds your account presence while sequences handle direct lead outreach. Neither blocks the other.

***

## Daily Action Allocation

The Engagement Engine generates a randomized mix of actions each day. Counts vary daily to mimic natural human behavior.

### Daily Activity

Each day, the Engagement Engine performs a mix of actions across your connected platforms:

**X (Twitter):** Likes, follows, replies, and tweets - with daily variation in counts.

**LinkedIn:** Likes, connection requests, comments, and posts - with daily variation in counts.

**Instagram:** Likes, comments, follows, and story views - with daily variation in counts. (No standalone posts.)

Some days have reduced or zero activity for certain action types, and occasional skip days with minimal activity simulate natural human behavior. Outreach sequences are **not affected** by skip days - only Engagement Engine activity pauses.

### Action Scheduling

Actions are distributed into natural sessions within your activity window, with randomized timing between actions to avoid patterns.

### Account Safety

The Engagement Engine automatically reduces activity if account errors occur, protecting your accounts from platform detection. If errors persist, activity scales down progressively until the issue resolves.

## Next Steps

* [**Content Strategy and Pillars**](/engagement-engine/content-strategy.md): How pillars guide engagement targeting
* [**Content Generation and Approvals**](/engagement-engine/content-generation.md): How content is created and reviewed


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.autoreach.tech/engagement-engine/engagement.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.