Authorize
Connect the creator-controlled X account through the official OAuth flow.
X inbox automation
Automate requested X DMs without turning your account into a bot
Loresta helps creators respond to routine inbound X messages in their own voice while collaborations, personal requests, and uncertain conversations stay with the owner.
Start with requested DMs, never unsolicited outreach
An X DM auto reply should respond only after a person has contacted the creator. Loresta does not send cold DMs, automate follower outreach, or manufacture engagement. This inbound-only boundary is both a product rule and a better customer experience.
X says automated Direct Messages must follow its automation rules, including requirements around user requests, opt-in, and spam. Anyone operating automation remains responsible for the connected account and the messages it sends.
- No cold DM campaigns
- No follower-based mass messaging
- No engagement manipulation
- Creator can pause the connection
Answer the question that was actually asked
A useful X reply uses the current thread, the creator’s approved facts, and a clear destination. It should not paste the same sales sentence into every DM. If a fan asks what the creator shares, the reply can give a short, specific answer before suggesting the next step.
Loresta can learn phrasing from up to 100 recent creator-authored replies after the creator opts in. It stores a compact editable voice summary rather than using the raw message history as a permanent persona archive. Learn more in the AI DM assistant guide.
Treat business and personal messages as owner work
X is often where collaborations, paid promotions, and direct business conversations begin. Those messages should not receive a generic automatic response. Loresta identifies business intent, alerts the creator, and leaves the thread unanswered.
The same rule applies to payments, personal requests, safety concerns, legal topics, or anything the system cannot answer confidently from approved information. See the two-path workflow on How it works.
- Collaboration and sponsorship inquiries
- Payment or account concerns
- Personal or custom requests
- Any uncertain intent
Budget for X API usage and customer reply capacity
X uses pay-per-usage API pricing. Its current documentation lists metered endpoint charges and account-level controls, so an operator should monitor reads, sends, and monthly caps against the current X API pricing documentation.
Loresta tracks provider usage separately from customer reply allowance. On customer plans, only a safe reply drafted or sent by Loresta counts. Optional overage can be disabled, allowing replies to pause at the plan limit. Review included replies and overage on pricing.
Launch with a reversible test
Connect the creator-controlled X account, confirm the callback and permissions, teach a small set of approved facts, and test realistic inbound questions. Begin with conservative handoffs. A week of observed traffic will show which questions repeat and which should remain entirely human.
Do not judge the system by how many replies it sends. Judge it by whether routine interest receives a useful answer, high-value conversations reach the creator, and the account stays within provider and customer limits.
A practical workflow
Keep the automation narrow, observable, and easy to pause.
Constrain
Add approved answers, destinations, forbidden claims, and handoff rules.
Simulate
Test routine interest, follow-ups, collaborations, and uncertain messages.
Observe
Watch useful replies, handoffs, API usage, and plan capacity.
Before you turn on automatic replies
Use this launch check to protect the creator’s voice and keep sensitive conversations human.
- The automation only responds to inbound DMs
- The creator approved the voice profile
- Business inquiries trigger owner alerts
- Provider usage limits are configured
- Plan overage is enabled or disabled intentionally
- The account owner knows how to pause the connection
Frequently asked questions
Direct answers for creators and operators comparing DM automation.
Can I auto reply to X DMs?
Automated replies must follow X rules and should be limited to people who requested or opted into the conversation. Loresta is designed for inbound DMs, not unsolicited outreach.
Does Loresta send mass DMs on X?
No. It does not send cold campaigns, message follower lists, or automate engagement.
How does an X reply sound like the creator?
The creator sets voice details and can consent to learning from recent creator-authored replies. Loresta uses an editable summary plus the current conversation context.
What happens to a brand deal in X DMs?
Loresta alerts the creator and sends no automatic reply so the owner can handle terms, pricing, and negotiation.
How are X API costs controlled?
Provider usage is tracked and can be capped separately from the customer's included Loresta reply allowance. Current X pricing should always be checked in the official documentation.
Make routine DMs useful without giving up control
Teach Loresta your voice, approved facts, destination, and handoff rules before any automatic reply is enabled.