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

# Outreach best practices

> Who to message, how to write DMs people reply to, when to send, and how to stay within platform rules.

<Note>Available on Pro. See [Plans](/get-started/plans).</Note>

Reply rate tracks how relevant and respectful you are, not how many messages you send. Most weak campaigns fail on targeting and copy, not tooling.

## Fix the profile first

People open the DM, then check who you are.

| Element | What to aim for |
| - | - |
| Photo | Clear face or recognizable mark — avoid a logo-only brand avatar when possible |
| Bio | Who you help and how, in plain language |
| Activity | Recent posts that show a real person |
| Verification | Strongly preferred on X — X often filters messages from unverified accounts into requests or blocks them |

Personal accounts usually outperform brand accounts for cold outreach. People reply to people.

## Choose who to message

Define your ideal customer on each platform:

* Keywords and phrases that show up in bios
* Creators, communities, or accounts they engage with
* Locations, roles, or niches that convert for you
* Signals they're open to DMs, such as active posting and public conversation

Prefer warm context over pure cold:

| Source | Why it works | How to treat it |
| - | - | - |
| People who already follow or engage with you | They took a step toward you | Reference shared content; softer ask |
| Replies or likes on relevant posts | Fresh context | Mention the post; keep it short |
| Lists, followers of niche accounts, CSV imports | Scalable, but colder | Stronger personalization |
| Prior conversations | Highest trust | Don't re-pitch blindly — continue the thread |

Segment lists by source and intent so the opener can match — [Lead lists, tags, and filters](/help/sales/lead-lists). Build lists only from imports and research you have rights to use, and exclude **Contacted** when you don't want repeats — [Sending pace and duplicates](/help/sales/pacing). Skip purchased engagement and scraped dumps of unrelated users.

## Write DMs people finish reading

* Keep the first message to a few sentences
* Open with a specific detail (bio, recent post, shared niche), not a pitch
* Ask one easy question, or offer one useful observation
* Skip links in the first message unless the prospect asked, or you're sharing a post or resource they expect
* Avoid walls of text and identical copy — vary messages across segments
* Use [variables](/help/sales/sequences#personalize-with-variables) for name or company, and add a human detail by hand

| Pattern | Example shape |
| - | - |
| Context + question | “Saw your note on {topic} — are you still exploring {problem}?” |
| Soft value | “We put together a short checklist for {ICP} dealing with {pain}. Want it?” |
| Warm follow-up | Reference their reply or post before asking for time |

Hard sells and “book a demo” openers usually tank reply rates.

## Sequence without nagging

One strong first message beats a noisy sequence. Add steps only after a one-message campaign already gets replies — [Sequences](/help/sales/sequences).

1. Intro + specific context
2. Soft follow-up a few days later
3. Final note with a clear ask or resource, then stop

Space steps by days, not hours, and keep it to two or three follow-ups.

## When to send

* Schedule for the prospect's local daytime — [Scheduling](/help/sales/sequences#schedule-across-time-zones)
* Weekday mornings and early business hours usually beat late nights and weekends for B2B
* If you can, engage lightly on public posts before a cold DM

## When to stop

Stop when they reply (positive or not), ignore the full sequence, ask not to be contacted, or delivery keeps failing. Persistence past a clear “no” is how outreach turns into harassment.

## Reply like a human

* Answer quickly while the thread is warm
* Keep the same tone you used in the opener
* Move to a call or link only after they engage
* If they're not interested, thank them and exit

## Stay within platform rules

Follow each platform's rules — on X, [X's rules](https://help.x.com/en/rules-and-policies) and the [platform manipulation and spam](https://help.x.com/en/rules-and-policies/platform-manipulation) policy. Inboxapp paces sending for you; you're still responsible for how you message people.

<Warning>
  Don't try to bypass platform limits, blast identical copy at scale, buy
  engagement, or scrape data outside authorized channels. Those patterns get
  accounts restricted.
</Warning>

| Do | Don't |
| - | - |
| Authentic accounts with a clear identity | Fake, disposable, or misleading accounts |
| Relevant, non-duplicative DMs | Bulk identical or unsolicited spam |
| Automation that stays within allowed product limits | Unauthorized scripts or aggressive bot behavior |
| Follow-ups that stop when ignored | Harassment, relentless chasing, or scam tactics |

* You're responsible for third-party apps you authorize on your accounts. Don't stack multiple senders to force volume.
* Don't buy followers, likes, or engagement. One authentic presence beats a farm of lookalike accounts.
* If messages show as undelivered or failed, pause and fix the account before resuming — [Undelivered](/help/platforms/x/message-icons) · [Failed to send](/help/platforms/x/message-icons).

## Measure and iterate

Track reply rate and conversation quality before volume — [Campaign stages and results](/help/sales/campaign-results). If replies are low, fix list fit and copy before you scale.

1. Segment a tight list for one ideal customer
2. Write one short opener only that segment would believe
3. Add a 2–3 step sequence once the first message works
4. Iterate on list and copy, then scale

## Related

* [Create your first campaign](/help/campaigns/build/create-your-first-campaign)
* [Sequences, personalization, and scheduling](/help/sales/sequences)
* [Sending pace and duplicates](/help/sales/pacing)

Still stuck? Contact support from the app.


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