To reply to comments from 100 iPhones, stop opening each device and route every comment into one Creator OS inbox. Each account in the workspace reports its comments and DMs into a single searchable list, and replies go back out through the web app, the API or the CLI. One person answers the whole fleet from one dashboard.
100 accounts (each its own workspace seat)
|
v
platform comment and DM streams
|
v
Creator OS inbox <-- comments + DMs, searchable
|
+--> reply_to_comment (public reply)
+--> private-reply (comment becomes a DM)
+--> keyword automation (reply + DM in one step)
|
v
one dashboard, one CLI, one MCP connection
What Does Reply to Comments From 100 iPhones Actually Mean
It means 100 social accounts, each logged in on its own device, all answered by one person from a shared inbox instead of 100 screens.
The phones are just where the accounts live. The real problem is the reply gap: comments pile up across devices and networks, and no single person can watch 100 screens. Creator OS treats the account as the unit, not the device. An account connects once to a workspace, and from then on its comments and DMs arrive in one place.
A workspace is one set of socials: one account on each of 11 platforms plus Skool. If you run more than one set, you use an agency plan, and each client workspace gets its own scoped API key. An agent holding one workspace key cannot post to another. That boundary is what keeps a large fleet organized. For the connection detail, the agents docs list every reply surface Creator OS supports.
Why Replying at 100-Device Scale Breaks After Setup
Setup is the easy part. Replying is where a 100-device fleet stalls.
- Comments arrive on different networks. Instagram, Facebook, X, Threads, YouTube, LinkedIn and Reddit all support comment replies through the API. They do not share a screen.
- DMs are a second stream. Instagram, Facebook, X, Reddit and WhatsApp each hold messages that need an answer.
- Nothing is searchable across apps. You cannot ask “who asked about pricing this week” across 100 open apps.
- Volume arrives unevenly. One account can take most of the traffic on any given day, and the manual loop has no way to show you which one.
So the fleet works for a week, then the unread count becomes the product problem. The fix is not more people on more phones. The fix is one place where every comment and DM lands, with a search that spans all of them.
How the Creator OS Inbox Handles Comments From 100 Accounts
Every connected account reports its comments and DMs into one inbox, and you reply without knowing which phone sent what.
The inbox is searchable across all DMs. Comments show per platform and per post. You can reply publicly, hide a comment, like it, or send a private reply that turns into a DM. The comment-to-DM funnel runs on Instagram and Facebook: somebody comments a keyword, and the automation sends them your link.
From the CLI, the loop looks like this:
# see what came in across accounts
creatoros inbox:comments --platform instagram --limit 50
# read comments on one specific post
creatoros inbox:post-comments post_123
# reply in public
creatoros inbox:reply post_123 --accountId acc_abc \
--message "Sent you the link in a DM."
# answer a comment privately, as a DM
creatoros inbox:private-reply post_123 cmt_456 --accountId acc_abc \
--message "Here is the guide you asked for."
# hide a spam comment instead of feeding it
creatoros inbox:hide-comment post_123 cmt_789 --accountId acc_abc
Note the –accountId flag. With 100 accounts in play, the account is part of every reply, because the same comment text can exist on five posts. The API uses the same model: a key is pinned to one workspace, and ids are typed tokens such as acc_, post_ and cmt_. If your agent is wired through the hosted MCP server, the tools are list_comments, reply_to_comment, hide_comment, list_conversations and send_message.
One rule to remember: TikTok does not support comment replies through the API. On TikTok for Business accounts you can hide or delete a comment, but not reply to it. Plan TikTok engagement for the app and let the inbox handle the rest.
Where WhatsApp Fits in a 100-Account Reply Workflow
WhatsApp is a separate messaging channel, not a way for Instagram or Reddit replies to leave. It connects to the same inbox so the people you talk to most end up in one queue.
You connect a WhatsApp Business number. A personal WhatsApp account will not connect. From then on WhatsApp sits next to your Instagram and Reddit DMs, and the message rules are different from a public reply:
| Window | What you can send | Who pays |
|---|---|---|
| Within 24 hours of the customer’s last message | Free text reply | No template charge |
| Outside 24 hours | A Meta-approved template to open the conversation | Meta bills the template to your own WhatsApp Business account |
| To a list or tagged segment | A broadcast, now or on a schedule, with timed sequences | Each recipient is a billed template delivery |
The practical pattern: when a comment needs a real answer and a link, reply publicly in one line. If the person is already a WhatsApp contact, continue there. If they are not, open with an approved template and keep the list to people who opted in. Every WhatsApp recipient is a billed template delivery, so broadcasts are for your own audience, not for cold commenters. Request shapes and template creation live in the WhatsApp API docs.
Can You Reply From One Dashboard Without Switching Apps
Yes. One inbox, one search box, and one set of reply controls covers every account you have connected.
- Comments across Instagram, Facebook, X, Threads, YouTube, LinkedIn and Reddit, with public reply, hide, like and delete actions.
- DMs from Instagram, Facebook, X, Reddit and WhatsApp, plus Slack DMs to the bot and @mentions. Discord is the exception: the bot can send DMs to members but cannot read the replies.
- One search across all DM conversations, so a question asked on account 7 is findable from the same bar as account 93.
- Automations that keep working while you sleep. A keyword automation on Instagram or Facebook replies to the comment and sends the DM, scoped to a post or an account.
creatoros automations:create \
--accountId acc_abc --postId post_123 \
--keywords "guide,link,send" --matchMode word \
--commentReply "Just sent it to your DMs." \
--dmMessage "Here is the guide you asked for."
That one command replaces a person watching one phone. Run it across the accounts that get the most traffic and the humans handle the rest. The comments to DM use case walks through the funnel end to end.
What to Do When 100 Accounts Get More Comments Than You Can Answer
Sort by what earns money, automate the repeat questions, and let the agent read the numbers back to you.
A triage order that holds up at 100 accounts:
- Answer buying intent first. Comments asking price, availability or “where do I get this” go to the top. The comment-to-DM funnel is the right tool here.
- Automate the FAQ. Most of the volume is the same five questions. Keyword automations answer those, and the DM carries the link. Captions have no clickable links on Instagram, so the DM is where the link lives.
- Hide the noise. Spam and bait get hidden, not answered. Hiding is one CLI call and does not feed the thread.
- Read the numbers weekly. Per-post analytics, daily account metrics and best time to post all come back through the same API, so an agent can tell you which of the 100 accounts is actually driving replies.
This is where an agent harness helps. Social Agents is an open source harness that runs your socials on Creator OS: it interviews you about your brand, then posts, replies to comments and DMs, runs automations and reports on a local dashboard. You bring your own model. Start it with npm start creatoros social-agents. The repo is at github.com/kevinbadi/social-agents.
For a visual walkthrough, watch the videos on the KevBuildsApps YouTube channel, and the launch video if you want the short version first.
FAQ
How do I reply to comments from 100 iPhones at once?
Connect the accounts to one Creator OS workspace, open the inbox, and reply from there. Every comment from every connected account lands in the same list, and the reply goes back out through the API with the right account id attached. You never touch the phones for the reply itself.
Can one person manage 100 iPhone comment replies without switching apps?
Yes. Comments from Instagram, Facebook, X, Threads, YouTube, LinkedIn and Reddit sit in one inbox, and DMs from Instagram, Facebook, X, Reddit and WhatsApp sit beside them in the same search. One person can work a queue instead of bouncing between 100 screens.
Does WhatsApp Business work for replying to comments at scale?
It works for the messaging half. A WhatsApp Business number connects and becomes part of the inbox, so the conversations you care about sit with your comment queue. Free text is limited to 24 hours after the customer’s last message; outside that window you open with a Meta-approved template, and Meta bills each delivery to your own account.
How is this different from running agents on many phones?
Running agents on many phones is about giving an agent devices to act through. Creator OS is the reply and analytics layer above the accounts: one inbox, one API, one hosted MCP server, and a CLI that can answer comments, send DMs and report on 100 accounts from one machine. Point the accounts at Creator OS and the reply gap closes.
What is a safe reply limit per account per day?
Creator OS does not publish a fixed per-account reply number, and you should not trust one that is invented. Treat each account like a person: answer the comments that need an answer, keep automated replies to genuine questions, and watch per-account metrics so a burst on one account does not hide a problem on another.
Get Started With Creator OS
Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included. Agency plans add a scoped API key per client workspace, which is how you keep ten client workspaces from bleeding into one another.
Create an account at https://www.creatoros.ca/sign-up, connect your first few accounts, and try the inbox on a small batch before you scale to the whole fleet. The docs at https://www.creatoros.ca/docs cover authentication, webhooks, post options and every endpoint the inbox uses.
Get started for $0
Free trial for new subscribers. Cancel anytime.