An automated DM should deliver a response someone requested, not start unsolicited sales conversations. Use a tool only after checking its current X permissions, the platform rules and a clear stop path.

Write exactly which action asks for a message and what message will follow. A new follow or the ability to receive a DM does not itself establish consent to an automated campaign. Do not use a generic interaction as permission for unrelated follow-up messages.

Read X’s automation rules for the actual use case. Account authorization and recipient consent are separate requirements.

Design a small workflow

  1. Show a clear request: for example, “Send this account a DM asking for the worksheet.”
  2. Respond with the requested resource and identify automation where useful.
  3. Provide an easy way to stop additional automated messages.
  4. Store only the minimum data needed for delivery and consent.
  5. Route questions and failures to a person.

Sample response: “Here is the worksheet you requested:[link]. This is an automated delivery message. Reply STOP if you do not want further automated messages.” This is a template, not proof that a tool implements STOP correctly.

Check the tool and test safely

Confirm the supported API workflow, required permissions, recipient opt-out, duplicate prevention and logs. A vendor’s “compliant” label is not certification. Do not use a browser script to bypass X access limits.

Test with accounts you control and consent from participants. Verify one request leads to the intended delivery, duplicate requests do not create a loop, and opt-out actually stops later sends. Leave ambiguous or failed sends for manual review rather than replaying them blindly.

Measure delivery rather than promised uplift

Keep counts of requests, deliveries, failures, opt-outs and useful responses. There is no verified 3-5 xconversion gain or universal safe daily volume here. Tweet Archivist is an archive/analytics product, not the DM automation engine described by this workflow.

For a wider selection checklist, see automation tool boundaries.