Deliver a requested resource on X by clearly explaining the keyword, the resource and that delivery happens by DM before someone replies. Inbox Rules on X (Premium, opt-in) send a message you wrote to people who reply to your X post with a keyword you chose. Honor opt-outs and keep delivery within the request.
Key takeaways
- Explain what the reader requests and how the message will arrive before asking for a keyword reply.
- A follow, open DMs or a generic reply does not establish permission for an automated message.
- Write the delivery message yourself and keep its contents aligned with the promised resource.
- Provide a clear way to stop further messages and promptly honor requests.
- Test the specific rule, monitor it and pause it when the offer or destination changes.
What is a keyword resource-delivery workflow?
Keyword resource delivery is a workflow in which a reader requests a named resource by replying with a specified word, then receives the promised material through the stated channel. The public invitation should make that exchange understandable before the reader acts.
For example, a founder might offer a blank product-review checklist. The post explains what the checklist contains and asks readers to reply with a distinctive keyword if they want a DM containing the link. The requested message delivers that checklist, with no surprise sales sequence attached.
This works only when the request is clear. “Comment below” does not explain whether a reader will receive a private message. “Reply CHECKLIST for a DM with the blank product-review checklist” gives the action, delivery channel and resource together.
X's automation rules, updated April 2026 and checked in October 2026, require prior requested contact or a clear indication that the recipient wants the DM. They also require a clear, easy opt-out that is promptly honored.
A technical match is not the same as a meaningful request. Someone might use your keyword while disagreeing with a post or discussing an unrelated point. Design the invitation and matching scope to reduce that ambiguity, then monitor what the rule actually encounters.
What does an opt-in resource request need to say?
An opt-in invitation should identify the resource, the action and the delivery channel. It should also set a reasonable expectation about what happens afterward. A reader should not need to infer that a short public reply initiates private contact.
Use plain wording before the keyword instruction. Explain who the resource helps and what it contains. If it is a blank template rather than an analysis of the reader's business, say that. If access requires an account or email submission, disclose that before the request.
X says that being technically able to receive a DM does not necessarily mean someone requested or expects an automated message. The policy's examples include following an account, accepting DMs from anyone and having an existing conversation.
Provide an easy stopping route that you can actually honor. If you tell readers they can reply with a request to stop, someone must monitor those replies and prevent further contact. Do not imply that writing “STOP” in a template creates suppression behavior in software.
For a one-resource offer, keep the follow-up boundary narrow. X says not to send additional follow-up DMs after a user-initiated interaction ends without permission. A request for a worksheet does not establish consent to an ongoing sales conversation or another campaign.
How should you write the message that delivers the resource?
Write a short message that identifies the request and delivers the resource. Include enough context that the recipient recognizes why the message arrived. Keep the link destination transparent, and avoid extra steps that were not disclosed in the original offer.
An illustrative message could read: “Here is the product-review checklist you requested on our post: [resource link]. It covers the decision, evidence and next test. If you do not want further messages about this resource, reply and tell us to stop.”
Use that stopping instruction only with a monitored process that honors it. If you cannot reliably receive and act on requests, pause the workflow until you can. A sentence promising control is useful only when the operator can provide that control.
Test the destination as a recipient. Confirm that the resource is available, the page title matches the offer and the link does not lead to a different promotion. Check mobile readability and permissions on shared documents before inviting public requests.
X's authenticity policy, checked in October 2026, prohibits spam and describes unwanted, repetitive and misleading activity. A keyword mechanism does not create an exemption from those broader rules. Keep the offer relevant and avoid repeatedly pressing people to request it.
Do not ask for sensitive information merely to deliver a general resource. X's automation rules advise requesting only information needed for the service. A blank checklist usually does not require a recipient's phone number, client details or internal business documents.
If a recipient voluntarily shares private context, handle it separately and carefully. X's private-information policy prohibits sharing private information without authorization. A useful customer response is not permission to publish a screenshot as a testimonial.
How do Reepl Inbox Rules fit this workflow?
Reepl is an AI writing platform that puts your social media on autopilot in your own voice: it finds what to post about, drafts your posts, and keeps your calendar full, with you choosing what it does without asking.
Inbox Rules on X (Premium, opt-in) send a message you wrote to people who reply to your X post with a keyword you chose. Keep that scope attached to the feature: your post, your chosen keyword, your written message and an opt-in request.
For the English settings interface, configure the rule in this order. Confirm the available controls in your Premium workspace and prepare the public opt-in wording before activating delivery. Keep your written message and resource link ready for review.
- Open settings, choose Inbox Rules, then Create Rule.
- Under Which posts to watch, choose Specific post for a resource tied to one announcement. Use Select post to choose that post.
- Enter the Trigger keyword and select the intended match: Exact, Whole word or Contains. Broader matching can capture unrelated wording, so test carefully.
- Write the promised resource message in DM to send, including a stopping route you can monitor. Select Create Rule to save it.
- Check the rule card's switch. If paused, use Activate rule only when the invitation and monitoring process are ready. Use Pause rule when delivery should stop.
The rule should deliver the message you prepared, rather than become a reason to send unrelated messages later. Review the destination whenever the resource changes. Pause the rule when the offer expires, the resource is withdrawn or you cannot monitor requests appropriately.
Feature availability and an active account connection do not establish that every message will arrive. X's DM help explains recipient settings and message requests. The delivery environment includes the recipient's account choices as well as your configured workflow.
Use Inbox Rules only in the specific X context described here. A resource request on another platform has its own rules and workflow. This feature description does not extend to automated comments, connections or messages on LinkedIn®.
What does a complete resource offer look like in practice?
Consider an illustrative consultant sharing a blank meeting-review worksheet. The worksheet helps a team record the decision, evidence, owner and next check. The consultant wants readers who ask for it to receive a useful link without manually repeating the same delivery text.
The first draft says, “Want better meetings? Comment below.” That invitation is too vague for this workflow. It does not name the worksheet or explain private delivery. A reader could respond with an opinion without asking to receive a message.
The consultant rewrites the post: “We made a blank meeting-review worksheet covering the decision, evidence, owner and next check. Reply WORKSHEET to this post if you want a DM with the link. You can use it without signing up.”
The final access sentence must be true. If the consultant later puts the worksheet behind an email form, the original offer no longer accurately describes the destination. The consultant should pause the rule and update the offer before inviting more requests.
The delivery message names the worksheet, links directly to it and explains how to request no further messages. The consultant assigns someone to monitor requests and review the rule, rather than assuming every recipient response is handled by the configuration itself.
A practical planning record looks like this:
| Field | Example entry |
|---|---|
| Resource | Blank meeting-review worksheet |
| Reader task | Record a decision and its next check |
| Public action | Reply WORKSHEET to the named post |
| Delivery | A DM containing the resource link |
| Access condition | No registration, if that remains true |
| Message owner | The person responsible for the written message |
| Opt-out handling | Monitored requests, promptly honored |
| Review trigger | Changed resource, expired offer or reported problem |
This example is a proposed process, not a customer result. It makes no claim about conversion rates or how many requests a post will attract. Its purpose is to keep the offer, request and delivery consistent enough for a reader to understand.
If the worksheet is already explained fully in the public post, linking it publicly may be simpler. Choose private delivery because it serves a legitimate reader need, not because every useful resource must be placed behind a keyword interaction.
How should you test and monitor a resource-delivery rule?
Test with a willing participant who understands the invitation and agrees to receive the message. Check the full experience, including the public wording, matching behavior, message contents and destination. A successful save in settings does not establish successful recipient delivery.
Use a small checklist before inviting wider participation:
- Open the resource with the access level a recipient will have.
- Read the public offer and confirm that DM delivery is explicit.
- Check the selected post, keyword and intended matching behavior.
- Review the exact message, including its stopping instructions.
- Test a genuine request with a consenting participant.
- Confirm the message and link from the recipient's perspective.
- Assign monitoring responsibility and a reason to pause the rule.
Also test ambiguous wording when practical. A keyword inside an unrelated sentence should prompt you to reconsider broad matching. The objective is not to capture every possible reply; it is to deliver a resource to people who clearly requested it.
Review connected-app permissions when troubleshooting. X's third-party access guide explains how to inspect and revoke access. Use the account's normal authorization controls, and do not interpret a permission issue as a reason to bypass recipient preferences.
If a reader reports no message, check the observed state before retrying. The message may be in requests, the recipient may have settings that affect delivery, or the operation may have failed. Ask for only the information needed to understand the problem.
Keep a basic record of the offer and the message version. That helps explain what a reader requested if the resource changes later. Do not build a larger collection of personal information than the workflow needs, and restrict access to any private correspondence.
What should you avoid promising about this workflow?
Do not promise guaranteed delivery, account safety or platform approval. The relevant policies, recipient settings and actual campaign behavior all matter. A narrowly described feature can support a process, but it cannot settle every condition that applies to an account or campaign.
X's automation rules include additional requirements for certain campaign types and AI-generated automated replies. This article describes delivering a message you wrote in response to a clear resource request. Do not expand it into a claim that arbitrary automated conversations or campaigns are approved.
Avoid presenting keyword requests as a universal growth tactic. A helpful worksheet may receive few requests because the audience already has a solution or does not need the resource. The useful question is whether requesting readers received what they expected.
Track practical problems first: unclear requests, inaccessible links, mistaken matches and unhandled opt-outs. Those observations tell you what to repair. A count of triggered actions alone does not establish successful delivery, meaningful interest or permission for subsequent outreach.
If you need a better resource before setting up delivery, start with the underlying explanation. Our guides to founder post ideas and content repurposing can help identify useful material from actual work while keeping the eventual X delivery workflow separate.
Continue with our guides to planning an X post and measuring requested-resource delivery.
Put your next idea into words
Draft in your voice, review the details, and choose what to publish.
