DEV Community: John Builds

Does Replying Boost Your Reach on X? The Reply Boost Mechanism Explained

John Builds — Tue, 02 Jun 2026 21:02:33 +0000

Replying to tweets is the most underrated growth tactic on X. It is not just about starting conversations — the X algorithm treats replies as a high-signal engagement action and rewards active repliers with increased distribution on their own posts. Here is how the reply boost works and how to use it.

What is the reply boost on X?

The reply boost is the reach amplification effect that comes from replying to popular posts on X. When you leave a substantive reply on a tweet with high engagement, two things happen:

Direct exposure. Your reply is visible to everyone who reads the original thread — including followers of the original poster who have never heard of you.
Algorithmic signal. The X algorithm interprets active reply behaviour as a sign of a healthy, engaged account. Users who reply frequently tend to see improved distribution on their own posts over time.

This is not a hack. It is how Twitter and X have always functioned: replies are public, threaded, and discoverable. The difference is that most users treat replies as a side channel rather than a primary growth tool.

How the X algorithm weights replies vs. other actions

Not all engagement actions are equal. Based on X's published open-source ranking model (released in 2023), replies carry significantly more weight than likes in terms of algorithmic amplification. A reply signals deeper intent — the user read the post, processed it, and invested time in a response.

From highest to lowest algorithmic weight: replies > quote tweets > reposts > likes > profile clicks. When your goal is reach, spending time replying generates more return than spending the same time liking posts.

How to use the reply boost to grow on X

The reply boost compounds when you are consistent and targeted. Here is the approach that works:

Target accounts with 5k–100k followers in your niche. Large enough for exposure, small enough that your reply is not buried under hundreds of others.
Reply within the first 30 minutes of a post going live. Early replies get the most visibility as engagement on the original post climbs.
Add a distinct point of view, not just agreement. "Great point!" adds nothing. A contrarian take, a data point, or a related story gets likes on your reply — which further boosts your visibility in the thread.
Reply every day. The compounding effect comes from consistency. 10–20 quality replies per day over 90 days produces measurable follower growth.

The fastest way to scale replies without losing your voice

The main constraint on the reply strategy is time. Writing 15 thoughtful replies per day on top of your existing content schedule is unsustainable for most founders and creators. This is exactly what XreplyAI is built for: it generates reply drafts trained on how you actually write, so you can review, edit, and post in seconds rather than minutes.

The goal is not to automate replies — it is to remove the blank-page friction so you can post more of them, faster, without sounding like everyone else using AI.

Frequently Asked Questions

Does replying to tweets boost your reach on X?

Yes. Replying to tweets is one of the highest-leverage actions on X for reach growth. When you reply to a large account, your reply is visible to their entire audience in the thread. The X algorithm also signals that you are an active, engaged user — which can boost distribution of your own posts.

What is the reply boost on X?

The reply boost refers to the algorithmic and social amplification that comes from replying to popular posts. Your reply sits under a high-traffic post and gets seen by followers of the original poster — giving you exposure to audiences that would not have found you otherwise.

How many replies should I post per day to grow on X?

Most practitioners who grow through replies post 10–20 substantive replies per day. Quality matters more than quantity — a well-considered reply to a post with 1,000 likes will outperform ten generic replies on low-traffic posts.

Does the X algorithm reward replying?

Yes. Based on X's published ranking model, replies carry more algorithmic weight than likes or reposts. The algorithm interprets active reply behaviour as a signal of a high-quality, engaged account.

Originally published at xreplyai.com.

I built an MCP server for my SaaS — here's what I learned shipping it as a distribution channel

John Builds — Mon, 01 Jun 2026 19:35:22 +0000

When I added an MCP server to XreplyAI (a social media scheduling tool), I wasn't just adding a feature — I was betting that the people most likely to care about consistent social presence are the same people already living in Claude Code or Cursor.

So far that bet feels right.

Here's what the setup looks like:

{
  "mcpServers": {
    "xreplyai": {
      "command": "npx",
      "args": ["-y", "@xreplyai/mcp@latest"]
    }
  }
}

After that, Claude Code has tools to create drafts, schedule posts, and publish across 8 platforms — X, LinkedIn, Instagram, Threads, YouTube, Pinterest, Bluesky, TikTok — without leaving the editor.

What I learned building it

The MCP TypeScript SDK is well-designed and the protocol is cleaner than I expected for something this new. The trickier parts were:

1. Remote MCP over HTTP — I deployed to Cloudflare Workers with OAuth 2.1. The spec exists but examples are sparse. Durable Objects handle session state cleanly.

2. Guardrails matter — "publish a post" is a destructive tool. I added a draft-first flow so nothing goes live without an explicit publish call.

3. Voice is what makes it non-trivial — XreplyAI trains on your tweet archive, so when you ask Claude to "write a post about what I just shipped," it generates in your style, not a template. That's what separates it from just calling a REST API from a prompt.

The distribution angle

MCP tools feel like a new surface for early SaaS adoption. Low install friction, high-intent audience (developers deep in AI workflows), zero cold outreach needed. Worth thinking about if you're building a tool that developers would actually use.

Try it free: https://xreplyai.com?utm_source=devto&utm_medium=social&utm_campaign=feature-2026-06-01

Does Reposting Your Own Tweet Help? What the X Algorithm Actually Does

John Builds — Fri, 29 May 2026 15:24:34 +0000

Short answer: sometimes. Reposting your own tweet on X can squeeze a little extra reach out of a post that performed well — but it is far from a growth strategy. Here is what actually happens when you hit repost on your own content, and what to do instead.

What happens when you repost your own tweet

When you repost your own tweet, X re-distributes it to your followers' timelines — but not necessarily the For You feed of people who don't follow you. The algorithm treats self-reposts as a signal that you want more eyes on a post, not as new content. That distinction matters.

Original posts and replies get evaluated fresh: the algorithm watches the early engagement rate (likes, replies, bookmarks per impression) and decides whether to amplify. Reposts skip that evaluation window. They rely on the original post's existing score.

So if your original tweet had strong engagement, reposting it at a different time of day can help latecomers see it. If the original had weak engagement, reposting it just moves a low-signal post around your own feed.

When reposting your own tweet actually helps

Timezone arbitrage. You posted at 9 AM EST and most of your audience is in Europe. Reposting at 2 PM UTC can double the effective reach for a time-sensitive announcement.
Evergreen content. Tips, frameworks, and how-tos have a long shelf life. Reposting them months later (not days) to a larger audience makes sense.
After a follower spike. If you just went viral on a different post and gained 500 new followers, reposting your best older content introduces it to people who never saw it.

What works better than a plain repost

The X algorithm weights different actions very differently. Replies — especially to larger accounts — carry the most reach-amplification value because they expose you to the original poster's audience. A quote tweet with added commentary performs better than a plain repost because it creates new content with its own engagement loop.

If you want to resurface old content, a quote tweet with "this still applies because..." gets more traction than a silent repost. The new text gives the algorithm something fresh to evaluate.

The highest-leverage habit on X is consistent, substantive replies to posts in your niche. Each reply is a mini-post visible to the original poster's followers. Over time, that compounds into follower growth that no amount of self-reposting can match.

The bottom line

Reposting your own tweet helps marginally in specific situations. It is not a growth lever. If you find yourself reposting old tweets because you have nothing new to say, the real fix is a more consistent posting habit — not recycling content. Use reposts sparingly, prefer quote tweets with commentary, and spend the rest of your time in other people's reply sections.

Frequently Asked Questions

Does reposting your own tweet help?

Yes, in limited cases. Reposting your own tweet can re-expose it to followers who missed it the first time, especially if you post at a different time of day. However, the X algorithm treats self-reposts differently from original content — they carry less algorithmic weight and rarely go viral on their own.

Does X penalise you for reposting your own tweet?

X does not explicitly penalise self-reposts, but the algorithm deprioritises content that gets low engagement relative to impressions. If your repost gets ignored, it can signal low-quality content and reduce future reach.

What works better than reposting your own tweet?

Replies are the highest-leverage action on X. They carry far more algorithmic weight than reposts and expose you to new audiences through the original poster's followers. Adding a quote tweet with fresh commentary also outperforms a plain repost.

How often should you repost your own tweets?

Sparingly. For evergreen content, once every few months is reasonable. For time-sensitive posts, once after 12–24 hours to catch a different timezone is acceptable. More than that risks training your followers to ignore reposts.

Originally published at xreplyai.com.

How to persist landing page attribution across OAuth redirects (30 lines of middleware)

John Builds — Thu, 28 May 2026 15:00:27 +0000

Landing page attribution breaks the moment a user hits an OAuth flow.

Here's the scenario: you're running ads to multiple landing pages — one angle about speed, one about voice matching, one generic. All getting clicks. But by the time a visitor completes signup through Google OAuth or Twitter OAuth, the original URL params are gone. You see a new user in your database. You have no idea which LP or which copy variant sent them.

The fix: cookie before redirect

The solution is straightforward once you see it:

On first page load, write the landing page path + A/B variant to a cookie — before any auth redirect happens
On account creation (server-side), read that cookie back and persist both fields on the user record
The cookie survives OAuth round-trips regardless of which auth method they use

// middleware.ts — runs on first page load
if (request.nextUrl.pathname.startsWith('/lp/')) {
  response.cookies.set('signup_landing_page', request.nextUrl.pathname, { maxAge: 3600 })
  response.cookies.set('ab_variant', getVariantFromCookie(request), { maxAge: 3600 })
}

# users_controller.rb — on account creation
user.signup_landing_page = cookies[:signup_landing_page]
user.ab_variant = cookies[:ab_variant]

Why not just use GA4?

GA4 session attribution and database-level user attribution tell different stories when auth redirects are involved. GA4 may correctly attribute the session to the landing page — but if you want to segment your actual converted users by which LP they came from (to measure LTV, churn rate, or feature adoption by cohort), you need it on the user record.

Now every new signup in XreplyAI carries signup_landing_page and ab_variant. First week of data is already changing where ad spend goes.

About 30 lines of middleware total. Worth the afternoon.

Built for XreplyAI — AI social media tool for solo founders.

The building-in-public system that actually stuck (after failing every just be consistent framework)

John Builds — Tue, 26 May 2026 15:56:53 +0000

The building-in-public system that actually stuck (after failing every "just be consistent" framework)

I spent the first year of my product treating social media like something I'd get to eventually. Posted sporadically, disappeared during crunch, felt guilty about it constantly.

Here's the system that finally stuck — and it works because it makes content a byproduct of building, not a separate job:

1. Keep a decision log

Every real product decision gets one sentence: why did I do this. Not a post. Just a log. 30 seconds. This becomes the content backlog.

2. One post per week from the log

Pick the decision that felt most uncertain at the time. Those are always the most honest posts. Honest posts outperform polished ones in every community I've tried.

3. Replies are reactions, not performances

Stop trying to write the perfect reply. React genuinely, add one observation the person might not have considered, move on. 30 seconds per reply. It compounds.

The last piece was fixing the AI problem. Generic prompts made everything sound the same. Switched to training on my own tweet archive — replies actually sound like me now. I built this into XreplyAI as a BYOK tool — you connect your own Gemini or OpenAI key and pay the provider directly (usually under $5/mo).

Curious what systems other solo builders have landed on. Especially anything that makes replies less of a time sink.

How we trained a voice profile to make AI LinkedIn posts sound less like AI

John Builds — Tue, 19 May 2026 15:54:34 +0000

Most AI writing tools have a tell. The hook is too clean. The structure is too predictable. LinkedIn audiences in particular have gotten good at spotting it.

The root problem: AI generates from a blank slate. It doesn't know your cadence, your typical opening, the way you end a thought.

For XreplyAI, we took a different approach. Before generating anything, we build a voice profile from the user's own tweet archive — embedding similarity to find characteristic patterns, then injecting those as a style layer into the prompt. The result isn't perfect, but it's personal. It sounds like the person, not like a template.

We just shipped LinkedIn scheduling support. BYOK model — users supply their own Gemini, OpenAI, or Claude key.

If you're building something in the AI writing or scheduling space, happy to trade notes on the voice training approach.

https://xreplyai.com?utm_source=devto&utm_medium=social&utm_campaign=feature-2026-05-19

From GTM migration to missing UTM columns: getting ad attribution right as a solo founder

John Builds — Mon, 18 May 2026 18:45:54 +0000

Last month I migrated XreplyAI from hardcoded gtag snippets to Google Tag Manager.

One container. All pixels managed in one place. No code deploys to add or change tags. I thought that was the hard part of getting ad attribution right.

It wasn't.

This morning I finished wiring Google Ads conversion tracking — trial_start firing server-side via the GA4 Measurement Protocol, conversion imported into Google Ads, bidding optimized for trials.

Then a new user signed up. And I had no idea where they came from.

Not because GA4 didn't know. GA4 knew — "google / cpc." But our users table has no UTM columns. So I can't:

Calculate LTV by acquisition channel
Know whether Google Ads or X Ads drove a signup
Filter subscribers by source when making budget decisions

The fix is obvious in hindsight: store utm_source, utm_medium, utm_campaign, utm_content, and gclid on the user record at signup. Capture them from the URL on landing, pass them to the backend at magic link / signup time, persist once, never overwrite on subsequent logins.

It's a 2-hour task. I opened a GitHub issue this morning.

The lesson: GTM solves "where do my tags live." UTM columns on users solve "where did this specific person come from." You need both. Most founders running paid traffic have neither.

Fix it before you spend another dollar on ads.

Building XreplyAI in public — an AI social media tool for solo founders. BYOK model, voice-matched content across 8 platforms. xreplyai.com

Why we moved from hardcoded gtag snippets to Google Tag Manager in our Next.js app

John Builds — Thu, 14 May 2026 15:28:44 +0000

For the first year of building XreplyAI, our tracking setup was the standard mess: gtag scripts in _app.tsx, conversion events scattered across components, and a tacit rule that any tracking change needed a full deploy cycle.

It worked, but it had a real cost: we consistently under-instrumented. Adding a conversion event for a new experiment didn't feel worth a PR when you're moving fast solo.

The switch to GTM

The migration was about 2 hours. The short version:

Replace inline gtag calls with window.dataLayer.push() calls
Move all tag configs (Google Ads, GA4, any new pixels) into a GTM container
Publish the container — done

What actually changed

No deploys for tracking changes. New pixel, new conversion event, tweaked trigger — all done in GTM in minutes. This sounds minor until you ship 3 new conversion events in a week without opening your codebase once.

Preview mode is a real debugger. GTM shows every tag, trigger, and variable state as you click through your app in real time. We caught two misfiring conversion events we didn't know existed.

Explicit load order. Async gtag snippets fire whenever the browser gets around to them. GTM lets you sequence tags so dependencies are guaranteed to load before dependents run.

One place to audit everything. One dashboard instead of grepping through _app.tsx and a dozen component files.

Worth it at early stage?

Yes — especially if you're running any paid acquisition. The ops overhead of tracking living in your codebase compounds as you add channels. Moving it out early is much easier than untangling it later.

We're building XreplyAI — AI social media tool for solo founders. Happy to share the full GTM container structure in the comments if useful.

The real reason solo founders go quiet on social (and the system that fixes it)

John Builds — Wed, 13 May 2026 19:06:41 +0000

The solo founders who stay visible on social aren't more disciplined than everyone else. They just stopped making the content decision from scratch every day.

Here's the pattern I keep seeing:

The founders who go quiet are making three decisions every time they sit down to post: what topic, what format, what tone. By the time you've worked through that on a Tuesday morning with a backlog of customer emails, posting feels optional. So it gets skipped. Every busy week.

The founders who stay consistent solved a different problem. They made those decisions once — not weekly, not daily. Once.

The system that actually works

1. Pick your topics and leave them alone

Choose 3–5 areas you genuinely know and care about. Not what you think you should post about — what you'd talk about at a dinner with a founder you respect. Write those down. Don't revisit them every week.

2. Lock in a voice style

"Professional" and "casual" aren't voice styles — they're vibes. Get more specific. Are you direct and punchy? Do you explain things step by step? Do you use analogies? Pick one pattern that matches how you actually write when you're not overthinking it.

3. Review content, don't create it from zero

Once your topics and voice are set, your job is curation and approval — not blank-page creation. This is a completely different cognitive task. It takes 10 minutes instead of an hour.

Why most AI tools don't fix this

The problem with most AI writing tools is that they ask you the same questions every time: What do you want to write about? What tone? Who's the audience? You're still making the decision fresh. The tool just types faster.

The fix is a system where the decisions are made once, upstream, and the AI works within those guardrails automatically.

I built XreplyAI around this model. You set your topics and voice during onboarding — and now the generated posts show you exactly which voice preset and topics shaped each draft, so you can trust what you're approving rather than second-guessing whether it sounds like you.

Then it generates a rolling week of posts. You review, tweak if needed, approve.

Consistency stops being a motivation problem. It becomes a 10-minute-a-week workflow.

If you keep going quiet on social during busy stretches — the bottleneck probably isn't time. It's the decision overhead. Solve that first.

→ xreplyai.com

We A/B tested value-first onboarding (generate before subscribe) — here is what happened

John Builds — Tue, 12 May 2026 13:23:12 +0000

We've been running an A/B test on our onboarding flow and the early results are interesting enough to write up.

The old sequence

Voice setup → connect account → subscribe → generate posts. Classic SaaS — get commitment early, then show value.

The problem: users were dropping at the subscribe step having never seen a single piece of output. They were being asked to pay for something they'd only read about.

The value-first sequence

Pick topics → generate 5 posts in your voice → review them → THEN connect and subscribe.

By the time they hit the paywall, they've already seen their content calendar for next week. Drop-off on the subscribe step is lower. Makes sense — it's a lot easier to say yes to a tool when you're already holding the output.

Why it works

The subscribe step isn't a commitment to something abstract anymore. It's "do you want to keep the posts you just made?" That's a very different ask.

The implementation details

A few things worth noting if you're building something similar:

We run the sequence via a PostHog feature flag (onboarding-v2, variant value-first) — easy to roll back or adjust the split without a deploy
The full-tab onboarding (not a popup) was intentional — popups close if you click away, which kills any flow that involves a file upload or multi-step form
Preferences sync locally first (chrome.storage), then backend — so the extension is usable even if the API is temporarily unreachable

Full breakdown of both sequences and the design decisions behind each step: https://xreplyai.com/blog/xreplyai-onboarding-wizard?utm_source=devto&utm_medium=social&utm_campaign=blog-2026-05-12

Best AI Tools for Social Media in 2026 (Ranked and Reviewed)

John Builds — Mon, 11 May 2026 19:56:15 +0000

AI has changed how people manage social media — but not all tools are doing it the same way. Some generate generic templates. Some are X-only. Some charge $99/mo for features you can get elsewhere for $19. This is an honest breakdown of the best AI social media tools in 2026, ranked by use case.

What to look for in an AI social media tool

Before comparing tools, it helps to know what actually matters. Most AI social media tools do one or more of these things:

Draft content — generate posts from a topic or prompt
Schedule and publish — queue posts across platforms on a calendar
Generate replies — draft responses to comments and mentions
Voice matching — learn your tone so content sounds like you, not a template
Analytics — track what performs and why

No single tool does all of these equally well. The right choice depends on which combination matters most for your situation.

The best AI social media tools in 2026

#1 XreplyAI — Best for solo founders and creators who want AI that sounds like them

Platforms: X, LinkedIn, Instagram, Threads, YouTube, Pinterest, Bluesky, TikTok

Pricing: Pro $49.99/mo · BYOK from $19/mo · 7-day free trial

Pros:

Voice profile trained on your own posts — drafts sound like you wrote them
BYOK plan: pay your AI provider directly, no markup
AI reply generation + scheduling in one tool
8 platforms with per-platform formatting
MCP integration for power users

Cons:

Newer product — smaller community than legacy tools
No native analytics dashboard yet

Best for: Solo founders building in public, creators who post on multiple platforms, anyone tired of generic AI content

#2 Typefully — Best for X/Twitter and LinkedIn writers who want a clean writing experience

Platforms: X, LinkedIn

Pricing: Free plan available · Pro from $29/mo

Pros:

Best-in-class thread composer for X
Clean, distraction-free writing UI
AI writing assist built in
Good LinkedIn scheduling

Cons:

Only 2 platforms (X and LinkedIn)
No voice matching or training on your past posts
No reply generation

Best for: Writers and thought leaders focused on X and LinkedIn

#3 Hypefury — Best for X-focused creators who want automation and engagement tools

Platforms: X (primary), Instagram

Pricing: From $65/mo

Pros:

Auto-retweet, auto-plug, auto-DM features
Engagement automation built in
Strong X-native feature set
Good inspiration feed

Cons:

Expensive at $65/mo
Primarily X-focused — limited multi-platform support
AI content is template-based, not voice-trained

Best for: X power users who want engagement automation

#4 Tweet Hunter — Best for X creators who want analytics and a content library

Platforms: X

Pricing: From $49/mo

Pros:

Large library of high-performing tweet examples
Good tweet analytics
AI tweet generation with examples
Engagement features

Cons:

X-only
Expensive for what you get vs newer alternatives
No voice matching

Best for: X creators focused on growth with data-driven content decisions

#5 Buffer — Best for teams and agencies who need simple multi-platform scheduling

Platforms: X, LinkedIn, Instagram, Facebook, Pinterest, TikTok, YouTube, Mastodon

Pricing: Free plan · Essentials from $6/mo per channel

Pros:

Free plan available
Excellent multi-platform scheduling
Clean team collaboration tools
AI assistant for post drafting

Cons:

AI is generic — no voice training
No reply generation
Per-channel pricing adds up for many platforms

Best for: Teams and agencies who need reliable scheduling across many platforms

#6 Taplio — Best for LinkedIn-only creators who want AI content and CRM features

Platforms: LinkedIn only

Pricing: From $49/mo

Pros:

LinkedIn-native AI content generation
Built-in LinkedIn CRM and lead tracking
Good content inspiration from viral posts
Carousel and document post support

Cons:

LinkedIn only
Expensive for a single-platform tool
No voice matching

Best for: LinkedIn-focused B2B founders and consultants

The BYOK difference

One thing worth understanding before you pick a tool: most AI social media tools are charging you a markup on AI. You pay $49–99/mo, and part of that covers their Gemini or ChatGPT API costs. The tool bundles the AI in so you don't have to think about it — but you also can't see what you're actually paying for AI vs the software.

XreplyAI is the only major tool with a BYOK (Bring Your Own Key) plan. You connect your own Gemini or ChatGPT API key, pay the AI provider directly, and the actual AI cost for most solo founders is $1–5/mo. The tool costs $19/mo. Total: roughly $20–24/mo vs $49–99/mo elsewhere.

Whether that matters depends on how much you use AI generation. If you're generating a lot of content daily, the savings compound quickly. If you use the AI occasionally, the difference is smaller.

How to choose

If you want...	Use
AI that sounds like you across 8 platforms	XreplyAI
Best X/Twitter thread writing experience	Typefully
X engagement automation (auto-RT, auto-DM)	Hypefury
Data-driven X growth with content library	Tweet Hunter
Team scheduling across many platforms	Buffer
LinkedIn-only content + CRM	Taplio

FAQ

What is the best AI tool for social media in 2026?

It depends on your use case. For solo founders and creators who want voice-matched content across multiple platforms, XreplyAI is the strongest option. For pure scheduling, Buffer. For LinkedIn, Taplio. For X-focused growth, Hypefury or Tweet Hunter.

What is BYOK and why does it matter?

BYOK (Bring Your Own Key) means you connect your own AI API key instead of paying the tool's markup. With BYOK, you pay the AI provider directly — often $1–5/mo in actual usage — instead of $49–99/mo to the tool. XreplyAI is the only major social media tool with a BYOK plan.

Can AI social media tools write in my voice?

Most generate generic content from a prompt. XreplyAI trains on your own past posts to learn your tone, vocabulary, and sentence structure so drafts sound like you, not a template.

Which AI social media tools work for multiple platforms?

XreplyAI supports 8 platforms. Buffer supports most major platforms. Typefully covers X and LinkedIn. Hypefury is X-focused. Taplio is LinkedIn-only.

Are there free AI social media tools?

Most offer free trials rather than permanent free tiers. XreplyAI has a 7-day free trial and a BYOK plan from $19/mo. Buffer has a free plan with limited scheduling. Most others are paid-only with trials.

Originally published at xreplyai.com.

Auto-DM new Twitter/X followers: how we built it, and the API wall blocking Instagram and LinkedIn

John Builds — Fri, 08 May 2026 14:53:26 +0000

I shipped Auto DM replies in XreplyAI this week. Here's how it works under the hood, and why bringing it to Instagram and LinkedIn is a much harder problem.

The X implementation

The core loop is straightforward: poll for new followers, diff against a snapshot, send DMs to net-new ones. The details that matter:

First run snapshots up to 1,000 existing followers so you don't blast your whole audience on day one
Each subsequent cycle polls the 100 most recent followers and compares against the snapshot
Rate-limited to 15 DMs per cycle — Twitter's DM rate limits are easy to hit if you're not careful
Template supports a {name} placeholder; everything else is plain text (500 char limit)
All sends logged with status: pending / sent / failed

The tricky edge: if a user has 50,000 followers, the snapshot only captures 1,000. Anyone outside that window who was already following before first run could theoretically get a DM. We flag this in the UI and let the user decide.

Why Instagram and LinkedIn are a different problem

Instagram DMs require instagram_manage_messages — a permission that goes through manual Meta app review. The review checks your automation use case against their policy. Outcome isn't guaranteed, timeline is weeks, and the reviewer feedback loop is slow.

LinkedIn is the real wall. Automated DMs to followers or post engagers requires the Community Management API. It's invite-only, no public application, and requires a LinkedIn partnership contact to even get into the queue. I've been trying to find the right entry point for weeks.

If you've navigated either of these — especially LinkedIn's partnership process — I'd genuinely love to compare notes in the comments.

X Auto DM is live now on Pro and BYOK plans: https://xreplyai.com?utm_source=devto&utm_medium=social&utm_campaign=feature-2026-05-08