NEFES uses the verified information in the business's brand memory for customer communication and separates out exceptions that need a human decision. This guide explains when a message should move from a standard reply to a human decision. For account permissions, the Delegating Instagram DM management to an agency guide is separate.
Decision tree: first identify the type of information
Question 1 — Is the answer in the business's approved fixed information? For example, if the restaurant address or opening hours card is up to date, a reply can be prepared.
Question 2 — Does the answer require real-time records? If the question involves stock, an appointment slot available today, a room on a specific date, a personalized price or a campaign exception, it requires an up-to-date business record and authorized approval.
Question 3 — Is there a complaint, risk or personal data? Topics such as health, allergens, food safety, refunds, payment disputes, children, identity or serious crises are taken out of the standard automatic reply.
Question 4 — Is a handoff to the right person possible? If the business representative handling the message's subject is not clear, the right person is identified first; a request is not forgotten after saying “we are looking into it.”
Practical decision table for six messages
| Message example | Automatic first information | Is a human handoff needed? |
|---|---|---|
| “What time do you close today?” | Approved current opening hours | If the special day is unclear |
| “Where is your menu?” | Valid menu link | If the link or menu is wrong |
| “Is there an appointment tomorrow at 14:00?” | Relevant date and contact channel | Yes, real-time availability |
| “Is a double room free on this date?” | Request information and booking path | Yes, room record |
| “I had an allergen problem with my order.” | Short reply that acknowledges the seriousness | Yes, the relevant authorized person |
| “My payment was taken but the order did not arrive.” | Confirmation that the request was received | Yes, payment/operations |
This table is not permission to send automatic replies. The message features the platform actually supports and the permissions of the user's account are checked separately.
What four pieces of information should a human handoff note include?
- Subject: What the customer briefly asked; do not add unnecessary personal data.
- Reason for handover: Real-time pricing, critical complaint, payment, or authority limit.
- Owner: Branch manager, reservations officer, venue owner, or an appropriate staff member.
- Follow-up status: Is it clear whether the request has reached its recipient, a reply is pending, or it has been resolved?
A human handover record should not become an excuse to copy customer identity details into several systems unnecessarily. The information shared is limited to what is needed to resolve the issue.
Two honest handoff sentences for the customer
Restaurant complaint: “We are looking into what you experienced carefully. We are sharing the matter with our restaurant manager and will make sure you receive a reply with verified information.”
Boutique hotel availability: “Our reservations team needs to check current room availability for your requested date. We are passing on your request; they will confirm definite availability.”
No firm timeframe is promised here. If the business actually meets a response time and has committed to it in writing as part of the service scope, it may be stated separately.
What happens to a customer who gets no reply?
Handing a request over to a person does not mean the automation has finished its job. After the handover, it should be visible through the business's appropriate follow-up channel whether the matter was addressed or remains open.
Three operational states: NEW_REQUEST → IN_HUMAN_REVIEW → RESOLVED. If the second stage takes longer, the owner is notified again according to the business's working hours and actual operating capacity. These labels are a recommended workflow; they are not a claim that they are ready-made system fields in the current Instagram or NEFES panel.
For which questions is an automatic reply useful?
Fixed, verifiable information, such as opening hours, location, general service list, and an up-to-date menu link, is an easy starting point when the message context is right.
In complex personal situations, complaints, or reservation decisions, the goal is not to force automation, but to move the customer to the right person and prevent the conversation from getting lost.
Meta's help documentation explains the automatic first reply and message automation settings in the Business Suite inbox; however, this document alone does not prove that the same API function or unlimited messaging permission is available on every Instagram account. Meta's help page on automatic replies.
How do you measure success?
“100 messages auto-replied” on its own is not customer satisfaction or sales. Incorrect automatic replies, handovers to the owner, repeat questions from customers, and genuinely resolved incidents should be tracked separately.
| Measurement | Comment | What it is not |
|---|---|---|
| Number of automatic replies | Standard reply action | Resolved request |
| Topic handed over to a person | Exception and decision needed | Sales |
| Resolved genuine complaint | Issue marked as resolved in the business record | Fully automatic resolution of all messages |
| Actual reservation/appointment | Authorized record | Just a DM |
| Information update needed | Missing/incorrect card in brand memory | Negative customer rating |
NEFES handles message routing based on real business information together with content management and brand memory. Final check: Does approved information answer this question? Is a current record needed? Is there a specific risk? Is the right person identified? Is the handover really being followed up?
Adapt this guide to your business
Define separate handover labels for complaints, payment disputes, and requests that need definite information. Keep the distinction between an automatic reply that only tells the customer their request was received and one that says the issue has been resolved.
