> 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/overview.md).

# Overview

The Engagement Engine builds a credible social presence on your accounts before you start outreach. It automatically posts content, engages with relevant posts, and grows your visibility so that when leads receive your messages, they see an active account with genuine engagement history.

## When to Run It

The Engagement Engine matters most in two situations:

* **Before you launch sequences on a new or inactive account.** Cold DMs from an empty account get ignored or flagged. Run the Engagement Engine for **at least 1-2 weeks** on a fresh account to build a posting history before you start sending outreach. Skipping this step is one of the most common reasons reply rates stay disappointingly low.
* **Continuously, alongside your outreach.** Even on established accounts, ongoing engagement keeps you visible in your prospects' feeds. When a lead sees your account commenting on a post they care about, then receives a DM from you, the message lands as a follow-up to existing presence rather than as a cold outreach.

You can run sequences without the Engagement Engine (it's not a hard requirement), but reply rates are typically meaningfully higher when you do.

## What the Engagement Engine Does

The Engagement Engine automatically:

* **Posts content** aligned with your offer and content pillars (X tweets and LinkedIn posts)
* **Engages with relevant posts** in your niche (likes, comments, follows/connections)
* **Maintains human-like patterns** with randomized timing, skip days, and natural variation

## How It Works

The system runs continuously throughout your activity window, distributing actions into natural sessions with randomized timing.

## Available Platforms

| Platform      | Action Types                                |
| ------------- | ------------------------------------------- |
| **X**         | Tweets, likes, follows, replies             |
| **LinkedIn**  | Posts, likes, connection requests, comments |
| **Instagram** | Likes, comments, follows, story views       |

You can run the Engagement Engine on multiple accounts simultaneously.

Instagram engagement targets are discovered from niche-relevant hashtags generated from your offer and refreshed on a rolling basis. The same human-like timing, skip days, and natural variation apply across every platform.

## Account Persona

When setting up the Engagement Engine, you can optionally define a persona to make generated content sound like a real person rather than a brand account:

* **Full name and role** - e.g. "Sarah Chen, Growth Lead"
* **Location** - e.g. "Los Angeles, CA"
* **Voice and personality** - 1-2 sentences describing tone, e.g. "Direct and data-driven, shares real numbers and builder insights."

All three fields are optional. If provided, the AI uses them to shape the voice and perspective of generated posts and engagement comments.

## Daily Activity

The Engagement Engine generates a randomized mix of actions each day. Action counts vary daily to mimic natural human behavior, including occasional skip days with minimal activity.

See [**Engagement Automation and Daily Actions**](https://doc.autoreach.tech/engagement-engine/engagement.md) for more details on daily activity patterns.

## Content Approval

All generated content enters an approval queue by default. You can:

* **Approve**: post as-is at the scheduled time
* **Discard**: permanently remove the content
* **Regenerate**: replace with a new AI-generated version
* **Edit**: modify the text before approving

Enable **auto-post** to skip manual review and post content automatically. A separate toggle controls whether engagement comments (and X replies) are auto-approved; it is labeled **Auto-comment** on LinkedIn and Instagram, and **Auto-reply** on X. Pending approvals expire if not reviewed. (Instagram has no auto-post toggle, since the Engagement Engine does not publish standalone Instagram posts.)

## Next Steps

* [**Content Strategy & Pillars**](https://doc.autoreach.tech/engagement-engine/content-strategy.md): How content themes are organized
* [**Engagement Automation**](https://doc.autoreach.tech/engagement-engine/engagement.md): Daily activity patterns and engagement targeting
* [**Content Generation & Approvals**](https://doc.autoreach.tech/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
