Creative · Community report
Build comment-to-DM automation
A creator on X says they replaced a paid Manychat plan by building their own comment-to-DM automation with Muse, reporting 3,031 DMs from 5,438 comments in two days plus a WhatsApp bot. The post shows no build details, so this page covers planning the flow, the rules to check and a safe test before launch.
What you can get
What it is
Automation spec and message set
A reviewed spec and message set for comment-to-DM automation, tested on a small scale before launch; not a guarantee of delivery numbers, cost or platform approval.
It came back right when
- A test comment with the trigger word from your second account receives exactly one DM with the correct link.
- Comments without the trigger receive no DM.
- The DM includes an opt-out line you approved.
- Your daily log shows comments received and DMs delivered side by side.
The checks are editorial, not from the source.
- Prepare
The account, post and trigger keyword the automation should watch
- Ask and review
Write down the exact flow: which post, which trigger word, what the DM delivers, and what a non-matching comment gets.
- Check the result
A test comment with the trigger word from your second account receives exactly one DM with the correct link.
The source case
@QRoonjha reports building their own comment-to-DM automation with Muse instead of paying for Manychat, which they say creators pay $90+/month for. By their account, two days in it had delivered 3,031 DMs from 5,438 comments, and a WhatsApp bot they also built had served 934 people, at a cost of $0 so far. The post does not show how the automation was built, which platform or account it runs on, what the messages said, or why roughly 2,400 comments did not lead to a DM. No setup steps, code, screenshots of the agent conversation or platform approval appear in the text.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
Creators pay @ManychatHQ $90+/month for comment-to-DM automation.
Source excerpt
2 days in: 3,031 DMs delivered from 5,438 comments, plus a WhatsApp bot that has served 934 people.
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring The account, post and trigger keyword the automation should watch, The exact link, file or offer the DM should deliver, Admin access to the account and any developer app you are willing to set up, Your approval of the message text, opt-out line and a small test before launch. Source community report, checked 2026-10-22.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
What you need
You supply
- The account, post and trigger keyword the automation should watch
- The exact link, file or offer the DM should deliver
- Admin access to the account and any developer app you are willing to set up
- Your approval of the message text, opt-out line and a small test before launch
How to try it
Editorial, not from the source
- Write down the exact flow: which post, which trigger word, what the DM delivers, and what a non-matching comment gets.
- Check the official route and rules for automated messages on your platform, including account type, app review, permissions and any reply window, before building anything.
- Have the agent draft the trigger rules, DM text, public comment reply and an opt-out line, then edit them yourself.
- Test with a second account of your own: comment the trigger, confirm the DM arrives once, and check a misspelled trigger.
- Approve the switch to live, then compare comments received with DMs delivered each day and look into the gap.
- Keep a way to pause the automation quickly, and review replies to the DMs so real questions get a human answer.
What the creator reports
@QRoonjha frames the post as a cost comparison: creators pay Manychat "$90+/month" for this kind of tool, and they say they built their own with Muse for free. Two days in, by their count, 3,031 DMs had gone out from 5,438 comments, and a separate WhatsApp bot had served 934 people, with "Cost so far: $0."
That is the whole account. The post does not name the social platform, say how comments were detected or messages sent, or show the DM text. The gap between comments and delivered DMs is not explained; it could be repeat commenters, non-matching comments or delivery limits, and the post does not say which.
Rules to check before you build
In general, automated DMs on Instagram and Facebook go through Meta's official messaging APIs, which usually require a professional or business account, a connected developer app and specific permissions, and some platforms limit when an automated reply may be sent after a user interacts. WhatsApp bots usually run on the WhatsApp Business Platform, which has its own rules on opt-in and message templates.
Read the current platform documentation yourself before connecting anything. A self-built tool avoids a subscription, but it also means you are responsible for keeping tokens private, respecting opt-outs and staying within the platform's limits.
Testing the flow before it goes live
Comment the trigger word from a second account you control and check that exactly one DM arrives with the right link. Try a misspelling, a reply to another comment and a comment with no trigger, and confirm each behaves as you planned.
Once live, keep a simple daily log of comments received and DMs delivered. If the gap grows, pause the automation and find out why before more people are missed or messaged twice.
Open Muse to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
Limits to confirm
- The post gives no build details: no platform, API, hosting, code or agent conversation is shown.
- The 3,031 DMs, 5,438 comments, 934 WhatsApp users and $0 cost are the author's own figures, with no dashboard or receipt in the text.
- The post does not explain why fewer DMs were delivered than comments received, or whether any platform limits or rules were involved.
- No account type, approval or permission requirement is confirmed by the source; check the platform's current rules yourself.
- This is an attributed community report, not reproduced by this guide. The suggested workflow and checks are editorial guidance, not a recovered conversation or guaranteed product capability.
If it goes wrong
Editorial, not from the source
- Commenters say they never got the DM
- Check whether their comment matched the trigger exactly, whether their account accepts messages, and whether the platform limited sending; compare against your daily log.
- Some people received the same DM twice
- Pause the automation and add a rule that sends one DM per person per post, then retest with your second account.
- The automation stopped sending after a while
- Access tokens and permissions can expire or be revoked. Check the connected app's status and reconnect only after reviewing what access it asks for.
Common questions
Can Muse build comment-to-DM automation?
One creator reports building it with Muse and says it delivered 3,031 DMs from 5,438 comments in two days. The post shows no build details, and this guide has not reproduced it.
Is a self-built setup really free?
The author reports a cost of $0 so far after two days. The post does not say what hosting, API access or accounts were used, so check whether any of those carry costs or limits for you.
Why might fewer DMs go out than comments come in?
The post gives no reason for its gap. In general, causes include repeat commenters, comments without the trigger word, users who can't receive messages and platform sending limits.
Did the creator also build a WhatsApp bot?
They report a WhatsApp bot that "has served 934 people", but say nothing about what it does or how it was set up.
Next
Related to this task
More in Creative
Similar tasks
Get recurring task recommendations — ask your own agent to check for relevant updates.