Product

InboxHelpDeskAIKnowledge BaseSalesIntegrations

Solutions

Customer SupportE-commerceService BusinessesSales Teams

Resources

BlogHelp CenterDocumentationComparePricing

Company

About SystemerContactPrivacyTerms
Get startedLog in
HomeBlogInstagram Direct for business: how to reply faster without losing requests
Guide· 8 min read

Instagram Direct for business: how to reply faster without losing requests

For many Ukrainian stores Instagram is not a marketing channel. It is the shop floor, the checkout and the complaints desk at once.

Instagram is where a large share of Ukrainian retail actually sells. A customer sees a photo, taps the story, asks the price and expects an answer the way they would expect it from a friend — in minutes, not tomorrow morning.

That expectation is the whole problem. A phone with the app on it is a fine place to answer five messages a day. It is a terrible place to run a business channel that receives two hundred.

What Direct really contains

A business account receives four different things in the same place, and they behave differently:

  • Direct messages — the main conversation, with the full history.
  • Story replies — a message attached to the story the customer reacted to. Without that context the reply reads as a riddle.
  • Comment mentions and replies — public, and often the same question three customers are also reading.
  • Message requests — from accounts that have never written to you. They wait in a separate folder and are the single most common source of a lost lead.
The folder nobody opens

Message requests do not send a normal notification. If nobody checks that folder daily, new customers — the ones who have never written before — are exactly the group you never answer.

The 24-hour window

Meta allows a business to reply to a customer through the API for 24 hours after the customer's last message. Inside that window you can send freely. Outside it, only specific message types are allowed, and a generic promotional follow-up is not one of them.

This has practical consequences for how you work:

  1. A question that arrives at 22:00 and gets answered at 09:00 is inside the window. A question answered on the third day is not.
  2. Asking the customer a clarifying question restarts nothing — the clock runs from their last message, so every unanswered clarification burns time.
  3. Building your process around messaging people days later is building on something the platform will eventually stop.

The practical rule: answer while the window is open, and if you need an out-of-window follow-up, move the conversation to a channel that allows it — email or a phone call the customer agreed to.

What a connected inbox changes

Connecting Instagram to a shared inbox through the official Meta API changes four things:

On the phoneIn a connected inbox
History belongs to the device and the person holding itHistory belongs to the company and survives staff changes
One person can answer at a timeSeveral managers, with assignment and no double replies
Requests folder checked when someone remembersEvery request in the same queue as everything else
Story context lost as soon as the story expiresThe story the customer replied to stays attached to the thread
Price and stock answered from memoryAnswered from the catalogue, with the source shown

The one that surprises teams is the last one. Most Direct questions are not complicated — price, availability, size, delivery, "is it still 2,490?". They are simply repetitive, and the person answering them is your most expensive employee at that moment. This is exactly the work AI drafts with a source attached are for.

Mistakes that get accounts restricted

  • Logging in with a password through a third-party service. Any tool that asks for your Instagram password instead of going through Meta Business is a grey integration. When Meta notices, the account is restricted, not the tool.
  • Mass outbound messaging. Instagram is not an email list. Bulk sends to people who did not write first are the fastest route to a block.
  • Auto-replies that never hand over. A bot that answers everything, including the complaint about a broken parcel, converts an unhappy customer into a public comment.
  • Answering a story reply without the story. Context is half the answer; without it you look like you are guessing.

A setup that holds at 200 messages a day

  1. Convert the account to a business account and connect it to a Meta Business page — the API requires it.
  2. Connect Instagram to your inbox through the official integration, not through a personal login.
  3. Put your twenty most common answers into the knowledge base: prices, delivery, returns, sizing, payment. See the knowledge base checklist.
  4. Turn on AI drafts for those twenty, with approval required. Watch the drafts for a week before letting anything send itself.
  5. Route requests and story replies to the same queue as Direct, with a rule that flags anything mentioning a problem, a refund or a delay for a person.
  6. Measure the first response time by hour of day — see what a good first response time looks like. The evening gap is usually where the money leaks out.

The goal is not to answer instantly with a robot. It is that the customer who asks the price at 23:40 gets the price at 23:40, and the customer whose parcel arrived broken gets a person.

Frequently asked

Do I need a business account to connect Instagram?

Yes. Messaging through the official Meta API requires an Instagram professional (business or creator) account linked to a Meta Business page. A personal account cannot be connected legitimately.

Can we reply to a customer a week later?

Not with a normal message through the API. Meta allows free-form replies for 24 hours after the customer last wrote. After that only specific message types are permitted, so plan the follow-up through a channel the customer agreed to.

Will connecting an inbox get my account blocked?

Not if the connection uses the official Meta integration. Blocks come from password-based third-party logins and from bulk outbound messaging, not from using the platform API as intended.

See Supporter on your own channels.

Connect one messenger, point the AI at your documents and watch the first answer come back with its source attached.