Define the boundary
Choose the routine questions the assistant may handle and the conversations that always return to a person.
Instagram Planned
Comment-to-DM automation should continue a requested conversation, not manufacture one
Loresta does not currently offer comment-triggered outbound DMs. This planned workflow will require official Meta capability and strict creator-controlled triggers.
A comment is not universal permission for promotion
Comment-to-DM tools commonly watch for an explicit keyword or supported interaction, then continue the requested exchange privately. That is different from sending unsolicited DMs to everyone who engages with a post.
Any Loresta implementation would stay inside official Meta capabilities, creator-approved triggers, and provider rate limits. It would not scrape commenters or simulate browser activity.
- Explicit creator-defined trigger
- Official provider capability
- No commenter scraping
- No bulk cold DMs
The private reply still needs to be useful
Moving a person into DMs does not justify a generic pitch. The first message should deliver the item or answer the keyword promised, then allow a real inbound conversation to continue.
Loresta's voice, fact, media, and handoff controls would apply after the permitted trigger so follow-up remains consistent with the creator's boundaries.
- Deliver what was requested
- No invented urgency
- Current-thread context
- Owner handoff
Treat this page as rollout transparency
Comment-to-DM automation is not currently available in Loresta. The product will not show a working connection or charge for the capability until official access, safety behavior, and delivery tests are complete.
Creators interested in the workflow can join the product rollout and prepare their voice profile while the integration remains planned.
- Planned label
- No false availability
- No bypass method
- Launch only after testing
A controlled rollout
Use the smallest safe workflow first, then widen it only after real conversation review.
Add the creator context
Approve the voice, facts, destination, and optional media that can support a useful reply.
Connect carefully
Authorize the supported inbox with official access and begin in draft-first mode.
Review and improve
Inspect replies, handoffs, usage, and repeated intent before widening any automation rule.
Launch checklist
Every connection and automatic reply should remain authorized, observable, and reversible.
- Official account authorization
- Inbound-only messaging
- Creator-approved facts
- Editable voice profile
- Conversation context
- Low-confidence handoff
- Personal and business inquiry handoff
- Visible usage and pause controls
Frequently asked questions
Direct answers about capability, rollout status, and creator control.
Does Loresta support Instagram comment-to-DM today?
No. It is a planned capability and depends on official Meta access and completed safety testing.
Is comment-to-DM the same as cold outreach?
No. A compliant workflow should use a supported explicit trigger and deliver what the person requested, not message unrelated commenters in bulk.
Will Loresta scrape Instagram comments?
No. Loresta is designed around official provider access rather than scraping or simulated browser actions.
Can I join a waitlist for the feature?
You can create a Loresta account and follow the rollout, but the dashboard will continue to label unsupported Instagram capabilities honestly.
Prepare the workflow while the integration is planned
Loresta keeps voice, facts, media, policies, and human handoffs visible before automation expands.