X direct-message guide
Build permission-aware X direct-message workflows
Define the recipient's intent, write a useful template, pace delivery, stop on reply, and keep an auditable history.
Quick answer
Start with explicit recipient intent. Select a permitted trigger, document why the person expects a DM, provide an opt-out, write the message for that context, add a delay and daily cap, prevent duplicate contact, and stop any sequence when the person replies.
Workflow overview
Permission
Confirm the recipient asked for or clearly indicated intent to receive a DM.
Template
Write the message, placeholders, link, and opt-out for that context.
Pace
Set the delay, daily ceiling, run window, and run days.
Stop
Never message twice when disabled, and stop a sequence on reply.
Trace
Review recipient-level delivery history and failures.
A technical ability to receive a DM is not consent
X's automation rules say automated DMs may be sent only after recipients have requested or clearly indicated an intent to be contacted by DM, with a clear opt-out that is promptly honored. Following an account, enabling open DMs, or having an old conversation does not necessarily establish that intent.
Choose triggers and lists that carry evidence of permission. A reply to an owned post may indicate context, but the post and CTA should make the expected follow-up clear. Do not use a purchased list, a scraped audience, or a broad follower list for unsolicited automated messages.
Write one useful message for one clear context
A template should explain why the recipient is receiving it, deliver the promised information quickly, and make the sender recognizable. Personalization placeholders such as a name or handle do not make an irrelevant message personal.
If a workflow has more than one permitted trigger, keep a separate template per trigger. Preview the resolved message, verify every link, and avoid asking for sensitive information inside the DM.
- State the context for the message.
- Keep the first message useful without requiring a click.
- Include a clear opt-out for an automated sequence.
- Never place confidential payment or identity data in the template.
Make stopping behavior part of the design
Twifly's DM tools include trigger-based Auto DM, a defined-list outreach workflow, multi-step sequences, per-day limits, schedules, a never-message-twice option, and delivery history. A DM sequence should stop as soon as a recipient replies; an opt-out must stop it sooner.
Add delays between steps and use a small daily ceiling. A backlog should resume gradually rather than firing in a burst. Pause the workflow when delivery failures or recipient complaints indicate that the source or message is wrong.
Keep recipient-level delivery history
For each recipient, record the trigger, template, delivery state, timestamp, and whether the person replied or opted out. That history prevents duplicate contact and makes a support question answerable without reconstructing the sequence from memory.
Monthly allowance and daily volume are operational constraints, not permission signals. Review the recipient source and message quality even when the workflow remains below both values.
Questions
Frequently asked questions
Does a new follower automatically consent to an automated DM?
No. X states that following an account is not, by itself, sufficient indication that the person expects an automated DM.
When should a DM sequence stop?
Stop immediately when the recipient replies or opts out. Also pause the campaign when delivery failures or complaints indicate a problem with the source or template.
What should DM delivery history record?
Record the recipient, permission context or trigger, template, delivery state, timestamp, reply state, and opt-out state.
Sources and review date
Product facts can change. These official sources were checked on the dates shown.