Meta App Review
Human Agent Permission: Why It Gets Rejected and How to Show a Real Human Handoff
The Human Agent feature lets real people reply outside the standard messaging window. Reviewers approve it only when the screencast proves a human is actually replying.
What the Human Agent feature allows
For Messenger and Instagram messaging, businesses can reply freely within a standard messaging window that opens when the user messages them. The Human Agent feature lets a real person reply for longer, up to seven days after the user's last message, using the HUMAN_AGENT message tag. It exists for support cases that need more time, such as an agent waiting for information from another team.
The key word is human. Automated replies, bots, and AI-generated messages are not allowed to use this tag. When I built AI-assisted messaging flows, this distinction became central to the architecture, not just to the App Review.
Why Meta rejects Human Agent permission requests
- The screencast shows automated or bot replies instead of a person typing.
- There is no visible handoff from automation to a human agent.
- The app has no agent interface, so the reviewer cannot see where a human replies from.
- The use-case text mentions follow-ups, reminders, or promotions, which are not allowed with this tag.
- The video does not show the reply arriving in Messenger or Instagram.
- The message is sent within the standard window, so the reviewer cannot see why the tag is needed.
How to demonstrate a real human handoff
- Show a user sending a message to the Page or Instagram professional account.
- Show the conversation arriving in the app's agent inbox.
- If automation exists, show the handoff: the bot stops and the conversation is assigned to an agent.
- Show a human agent typing and sending a reply from the inbox.
- Show the reply arriving in Messenger or Instagram on the user's side.
- Explain in a caption that the human agent tag is applied only to messages sent manually by agents.
Follow the general screencast structure for login and permissions, then dedicate a separate chapter to this handoff.
Writing the Human Agent use-case description
A good description explains why a human sometimes needs more time. For example: “Customers contact the business about delivery problems. When an agent must wait for the warehouse to confirm a replacement, the reply can take more than a day. The agent replies manually from the Inbox page. Only messages typed and sent by an authenticated agent use the human agent tag. Automated replies never use it.”
Avoid describing marketing, re-engagement, or reminder use cases. Those belong to other messaging features with their own rules.
Enforcing the Human Agent rule in the backend
The safest approach is to enforce the rule in code, not only in documentation. In the backend, I only attach the human agent tag when the message was created by an authenticated agent action, never from an automated workflow or AI response.
def build_message_payload(message, conversation):
payload = {"recipient": {"id": conversation.psid},
"message": {"text": message.text}}
if conversation.standard_window_open():
payload["messaging_type"] = "RESPONSE"
elif message.sender_type == "agent" and message.created_by_user_id:
payload["messaging_type"] = "MESSAGE_TAG"
payload["tag"] = "HUMAN_AGENT"
else:
raise PolicyError("Window closed: only a human agent can reply")
return payloadThe sender type comes from the request that created the message: an agent session, an automation rule, or the AI service. It is never inferred from the message content.
Human Agent and AI-assisted replies
Many inboxes now suggest AI-drafted replies to agents. I treat a suggestion as human only when an agent actively reviews, edits if needed, and clicks send. Fully automatic AI replies are treated as automation and follow the standard window. The design is covered in more detail in building an AI reply agent without breaking Meta policies.
Designing the agent inbox for compliance
The agent interface is where the Human Agent rule becomes visible. I show each conversation's window state clearly: standard window open, extended human window, or closed. When the standard window has closed, the composer shows a short notice that replies are sent as human agent messages, and automated suggestions are disabled unless an agent explicitly edits and sends them.
Assignment matters too. A conversation that needs more time is assigned to a named agent, so it is clear who is responsible for the reply within the seven-day limit. Agents see a countdown and a queue of conversations close to the limit, which helps them prioritize.
These details make the App Review easier, because the reviewer sees the rule built into the product, and they keep the team compliant long after approval.
Testing before submitting
- Send a test message to the Page, wait until the standard window closes in your test setup, and confirm an agent reply succeeds with the tag.
- Confirm that an automated reply in the same situation is blocked.
- Confirm the inbox shows agents whether the window is open, extended, or closed.
- Check that the webhook pipeline records inbound timestamps correctly, because the window logic depends on them.
Frequently asked questions
How long can a human agent reply with the HUMAN_AGENT tag?
Up to seven days after the user's last message, for replies sent by a real person.
Can a chatbot use the Human Agent tag?
No. The tag is only for messages written and sent by a human. Automated replies must follow the standard messaging window.
Does Human Agent apply to WhatsApp?
No. WhatsApp has its own customer service window and uses approved templates outside it. See designing a WhatsApp booking bot around the messaging window.
Is an AI-suggested reply sent by an agent allowed?
If a human reviews and sends it, it is treated as an agent message in most designs. Fully automatic AI replies are not. Keep this rule explicit in your product.