Instagram DM automation: one queue, ready drafts, approved replies
Instagram DM automation routes the direct messages you receive on Instagram, and comments where they are connected, into the same queue as your WhatsApp, email and web form requests. The request that has waited longest rises to the top. Drafts for common questions arrive ready and wait in an approval queue, and by default a person decides what is sent. Earlier conversations with the same person open beside the draft. Where a chatbot is used, it tells people it is a bot and hands unknown questions to a human.
A customer sees a post and asks their question on Instagram. They ask about a price or an appointment and wait for an answer in the account inbox. The same day, requests also arrive on WhatsApp, by email and through the website form. When every channel has its own inbox, nobody can see at a glance which request is still unanswered. Instagram DM automation gathers these into one queue, with messages and comments listed beside the other channels.
The order of the queue is simple: the request that has waited longest moves to the top. Drafts for common questions arrive ready and go to an approval queue. A draft is built from sources the business supplies: the price list, service descriptions, frequently asked questions, past correspondence and the customer record. If a sentence has no match in those sources, the system does not write it. In the default setup, a person decides what is sent. In that setup the automation does not speak for the business without control.
For certain types of request, direct sending can be switched on. That is an option, not the default. The rule behind every directly sent reply is kept in the record. Anyone can later read why a reply went out. Earlier requests and conversations with the same person open beside the draft, so nobody has to open a second screen to search for history. Time limits are handled by rule too: a request that passes the limit you set moves to the top and its owner is notified.
Where a chatbot takes part, it tells the person it is a bot. When a question has no source behind it, the bot does not invent an answer and hands the conversation to a human. The connection uses Meta's official Instagram API and needs a professional (business or creator) account. Meta's messaging rules apply to that connection, and the setup follows them. Messages contain personal data, so GDPR (and UK GDPR) applies to how they are stored and used. Setup starts with a one-week discovery, and the first live flow opens within 4 to 8 weeks. We work from Rotterdam and Istanbul.
What goes wrong today
- 01
The Instagram inbox sits apart from everything else
A message sent on Instagram stays in the account inbox, while WhatsApp and email live elsewhere. With no shared list, nobody can see at a glance which request is waiting. One queue collects every request on a single screen, whatever the channel.
- 02
Comments are missed
A question under a post arrives as a comment and sits apart from the message inbox. If nobody goes back to that post, the question stays unanswered. Comments can be connected to the same queue as messages, so a waiting question becomes visible.
- 03
Common questions are retyped every time
Questions about prices, opening hours, the address and appointments arrive again and again. Typing each answer by hand costs time and lets the wording drift. Drafts for common questions arrive ready; a person checks them and corrects them where needed.
- 04
Nobody can tell who sent a reply
When several people use the account, it is hard to know afterwards whose approval a reply went out under. In the approval queue, every reply passes through a person. For request types with direct sending, the rule behind each reply is kept in the record.
- 05
The customer history lives somewhere else
If the history stays in another tool, the reply is written with half the picture. Earlier requests and conversations with that person open beside the draft.
- 06
Nobody remembers the waiting request
On a busy day a message slips down the list and is forgotten. If remembering depends on one person's attention, things get forgotten. A request that passes the limit you set moves to the top and its owner is notified. The rule is written into the system.
Scope of the build
One queue for messages and comments
Messages from Instagram land in the same queue as WhatsApp, email and the web form, and comments can be connected to it. Instagram connects to the request-handling product as a channel that is not on its standard list. Each request is recorded with its arrival time. The request that has waited longest rises to the top. Instagram and WhatsApp appear in one panel, so the team looks at a single screen.
Ready drafts for common questions
Drafts for common questions come from sources the business supplies: the price list, service descriptions, frequently asked questions, past correspondence and the customer record. A sentence with no match in those sources is not written.
Approval queue and the decision to send
A prepared draft goes to the approval queue, and a person decides whether it is sent. The approver and the time of sending are recorded. In the default setup, no reply goes out without approval.
Direct sending when you want it
For certain types of request, direct sending can be switched on. The business decides which types. The rule behind each directly sent reply is kept in the record.
Customer history beside the draft
Earlier requests and conversations with the same person open beside the draft. The person writing the reply does not open a second screen to find history. The customer record is read from the connected CRM or from the panel.
Time-limit rule
The business sets a waiting time. A request that passes it moves to the top of the list and its owner is notified. Remembering is not left to any one person.
Rules for the chatbot
A person talking to a bot is told plainly that it is a bot. When a question has no source behind it, the bot does not invent an answer and hands the conversation to a human. Meta's messaging rules apply to that connection, and the setup follows them. A chatbot can be brought in with the same setup if you want one.
How the build runs
- 01
Discovery
Over one week we map the channels, today's waiting times and the questions that come up most. The result is a written discovery report.
- 02
Queue and sources
Instagram and the other channels are connected to one queue. The sources the drafts will use are collected from the business.
- 03
Approval and time rules
We write down who approves, which request types may go directly and what the waiting limit is. The first live flow opens within 4 to 8 weeks.
- 04
Measurement and growth
Before and after setup, we measure first reply time and the share of requests left unanswered. A new channel is added without disturbing the live flow.
Products used in this build
Request handling
Requests from five channels collect in one list, the draft reply arrives ready, and the decision to send stays with you.
AI chatbot and voice receptionist
It greets customers on your site and on the phone, answers what it has a source for, and hands the rest to a person.
WhatsApp Business integration
Notifications, order tracking and customer conversations gather in the business account; the history stays with the company.
Terms used on this page
- Instagram DM automation
- Instagram DM automation gathers Instagram messages and comments into one queue and prepares draft replies. By default, a person decides what is sent.
- Approval queue
- An approval queue is the stage where a prepared draft waits for a person to decide whether it is sent.
- Time-limit rule
- A time-limit rule moves a request to the top of the list and notifies its owner once it passes the waiting time you set.
- Direct sending
- Direct sending is a setting for chosen request types. A reply goes out without waiting for approval, and the rule is kept in the record.
- Draft reply
- A draft reply is a response text prepared from sources the business supplies and checked by a person before it is sent.
Instagram DM automationFrequently asked questions
A message from Instagram lands in the same queue as WhatsApp, email and other channels. A draft for common questions arrives ready and waits in the approval queue. A person checks the draft and decides whether it is sent. In the default setup, no reply goes out unapproved.
Comments under a post can be connected to the same queue as messages, so a waiting question is not missed. The decision to send stays with a person, as it does for messages. Direct sending is a separate option that you switch on for chosen request types.
In the default setup, a person from the business decides. If you want direct sending for certain request types, it can be switched on. The rule behind each directly sent reply is then kept in the record and can be read later.
Yes. Where a chatbot takes part, it tells the person plainly that it is a bot. When a question has no source behind it, the bot does not make up an answer. It hands the conversation to a human.
If a question has no match in the sources the business supplied, the system does not invent a reply. Without a source it produces no answer; it marks the question and passes it to a person. Someone on your team then answers it.
Yes. Instagram and WhatsApp are connected to the same panel, and email and the web form sit in the same list. Earlier requests and conversations with the same person open beside the draft.
Drafts are built from sources the business supplies: the price list, service descriptions, frequently asked questions, past correspondence and the customer record. The system does not write a sentence that has no match in those sources.
No. Customer records and message history are not used to train models. In the default setup, only a reply you have approved is sent out. Messages contain personal data, so GDPR (and UK GDPR) applies to how they are stored and used.
The business sets a waiting time. A request that passes it moves to the top of the list and its owner is notified. The rule is written into the system, so remembering does not depend on one person's attention.
The connection uses Meta's official Instagram API and needs a professional (business or creator) account. Meta's messaging rules apply to that connection, and the setup follows them.
The first week is discovery, when we map the channels, the approval rules and today's waiting times. The first live flow opens within 4 to 8 weeks. Your own timing is written into the discovery report.
The process first, the proposal after
In a short discovery call we map the process together and tell you plainly whether it is worth automating. If it is not, we say that too.
30 minutes · no preparation needed
