If you want to auto reply to Instagram DMs with AI, the setup is smaller than people expect. You connect your Instagram account to a workspace, you give an AI agent access to that workspace through an MCP server or the CLI, and you define what triggers a reply and what the reply says. The rest is comment-to-DM funnels and automations that run while you sleep.
Instagram comment or DM
|
v
keyword match (auto_)
|
v
AI drafts the reply
|
+------+------+
| |
v v
auto-send human review
(FAQ, link) (pricing talks)
What Auto Reply to Instagram DMs With AI Actually Does
There are two different things people mean when they say “auto reply.” The first is a comment-to-DM funnel: someone comments a keyword on your Reel, and they get a DM back. The second is an actual agent reading your inbox and answering messages.
Creator OS supports both, and they are not the same tool. The funnel lives in automations. The inbox work lives in the agent, through the same workspace your scheduled posts go out from.
Here is what is true on the Instagram side of Creator OS:
- Comment replies, hiding, DMs and comment-to-DM funnels are supported.
- DM replies are supported on Instagram, Facebook and X. TikTok has no DMs, and replying to TikTok comments is not supported.
- All your DMs land in one inbox across Instagram, Facebook and X.
Everything else, including the exact tool names and request shapes, is in the Creator OS docs. If you also want the comment side handled, read how to reply to comments with AI after this.
Why Manual DM Replies Cost You Followers and Sales
Think about when your DMs actually arrive. Late evening. Right after a Reel goes out. On a weekend. That is exactly when you are not at a desk.
So the DM sits. The person who made it is holding a live question and you are not there. If they asked for a link, they may just leave and find it somewhere else. If they asked a pricing question, they get nothing until tomorrow, and tomorrow they are colder.
Instagram makes this worse in one specific way: captions have no clickable links. If your answer is “link in bio,” you have already asked the person to work. A DM can carry a link directly.
That is the whole argument for automation here. Not scale for the sake of scale. Speed on the messages that were going to earn something anyway.
The Three Rules of a DM Bot That Does Not Feel Like a Bot
Rule one: answer before you sell
A good first message answers the question that was asked. If someone comments “plan” on a post about your program, the DM should send the plan, not a pitch deck.
Rule two: never guess at your own voice
Give the agent your real material. Your published articles, your existing posts, your pricing page. There is a full workflow for this in letting an AI agent research your published articles. An agent with your own words will sound like you because it is reading you.
Rule three: keep a door open
Every automated reply should make it easy to reach a real person. One line at the end is enough: “Reply here and I’ll take it from here.”
How to Connect Instagram DMs to an AI Agent (Step by Step)
Here is the actual setup. Nothing to install for the server path.
- Connect Instagram. In the web app or CLI, connect the Instagram account. Creator OS needs a Business or Creator account for Instagram publishing and messaging.
- Create an API key or a read and write MCP connection. Both are included in every plan, including the $19.99/month Creator plan.
- Add the hosted MCP server. In Claude, go to Settings, Connectors, Add custom connector, paste
https://mcp.creatoros.ca/mcp, sign in to Creator OS, pick the workspace, then choose read only or read and write. In ChatGPT, add the same URL as a connector in developer mode. - Or wire it into a code editor. For Claude Code:
claude mcp add --transport http creatoros https://mcp.creatoros.ca/mcp --header "Authorization: Bearer cos_live_...". Cursor, Windsurf and VS Code take anmcpServersentry with type http, the same URL and the same Authorization header. - Check what the agent can see. Read-only connections only see read tools, and the API refuses writes from them. That is a real safety rail, not a promise.
- Create the automation. This is where keywords live.
The automation itself is one CLI command:
creatoros automations:create \
--accountId acc_123 \
--postId post_456 \
--keywords "plan,pricing,how much" \
--matchMode contains \
--dmMessage "Here is the plan I mentioned. Which part do you want me to walk through?" \
--commentReply "Sent you a DM."Then check it is alive:
creatoros automations:list --cloud
creatoros automations:logs auto_789If you would rather start from a skill than a raw command, npx @creatoros/cli@latest init installs 14 Claude Code skills, including respond-to-dms and automations. If you want to see this wired up end to end, the walkthroughs live on the KevBuildsApps YouTube channel, and the Social Agents harness that runs your socials on Creator OS has its own launch video at youtube.com/watch?v=-QBJH_PK3pY.
Writing Prompts and Trigger Keywords That Convert
Keywords are the front door. Keep them literal. People comment the word you said out loud, not a synonym. If the Reel says “comment PLAN,” then plan is the keyword. Add the two or three variations you have actually seen, and use --matchMode contains so “the plan please” still matches.
Prompts are the back room. Do not write a personality. Write a job description.
You reply to Instagram DMs for a strength coaching business.
Rules:
- Answer the exact question first, in one or two sentences.
- For pricing, give the real number and the payment options.
- Never invent a discount, start date, or guarantee.
- If the message asks about injuries, refunds, or anything legal,
stop and hand off to a human.
- End with one question that moves the conversation forward.That last rule does more work than any clever phrasing. It turns a dead-end answer into a conversation.
Handling FAQs, Pricing Questions, and Link Requests Automatically
Split your inbox into three buckets and treat each one differently.
| Message type | What happens | Why |
|---|---|---|
| FAQ (“do you ship to Canada”) | Agent answers, no human | Same answer every time, nothing at stake |
| Link request (“send the guide”) | Agent sends a trackable link | Captions cannot carry links; DMs can, and you get click stats |
| Pricing or fit (“is this right for me”) | Agent gives facts, then hands off | High intent, worth a human sentence |
For links, Creator OS creates trackable go.creatoros.ca short links with click stats. That matters because it is the only way to know whether the DM funnel actually produced anything.
You can also send links as a first comment on the post itself, which is a different lever. There is a full breakdown in how to auto pin your first comment on YouTube. The same idea applies on Instagram, where the first comment is the closest thing to a clickable link you get outside a DM.
When to Hand Off to a Human and How to Do It Cleanly
Pick your handoff triggers before you turn the agent loose, and write them into the prompt. The ones that work:
- Anything about money the agent cannot confirm from your own pages.
- Complaints, refunds, and anything that sounds like a legal question.
- Anyone who asks for a person, twice.
Then make the handoff visible. The agent can mark a conversation read or archived with creatoros inbox:update-conversation <conversationId> --accountId acc_123 --status archived, or send a note to yourself. What matters is that you can open the inbox and see which threads are waiting, without scrolling through every answered FAQ.
Two guardrails make this safer than it sounds. Destructive tools, like deleting a post, deleting a comment, disconnecting an account or deleting an ad, are marked so your AI app asks first. And because an API key is pinned to one workspace, an agent holding one workspace’s key cannot post or reply from another.
Measuring Results: Response Rate, Reply Rate, and Signups
Three numbers tell you whether this is working.
- Response rate. Of the qualifying DMs, how many got a reply at all? This should be near total once automations run.
- Reply rate. Of the people who got a reply, how many wrote back? This is your prompt quality score. If it is low, your first sentence is not answering the question.
- Signups. Clicks on your
go.creatoros.calinks and what happened after. Without a trackable link, this number does not exist.
For per-post and per-account context, the agent can pull analytics directly: creatoros analytics:posts --platform instagram shows which posts drove the messages, and creatoros analytics:best-time --platform instagram tells you when your audience is actually awake. Run the funnel and the posting schedule on the same data instead of guessing.
If you want an agent that reads the results and decides what to change, that is what the open-source Social Agents harness is for. Start it with npm start creatoros social-agents. It interviews you about your brand, then posts, replies to comments and DMs, runs automations and reports back on a local dashboard, using your own model.
Get Started With Creator OS
The Creator plan is $19.99/month or $59.99/year and covers up to 8 connected accounts (7 socials plus Skool). API keys, the MCP server, the CLI and the agent skills are included in every plan, so the DM automation above costs nothing extra.
Make an account at creatoros.ca/sign-up, connect Instagram, and add https://mcp.creatoros.ca/mcp as a connector. Then build one automation for one keyword on one post. Watch three DMs. Adjust the prompt. That loop is the entire job.
If you run a coaching or consulting practice, the same setup is worth reading from that angle in AI social media manager for coaches and consultants. And if your funnel starts with video, the OPEN VIDEO EDIT skills turn a raw talking-head clip into an animated short with captions, rendered locally, which gives your DMs something better to link to.