Building a DM flow that hands off to a human

When a person should take over

• The flow cannot answer the question

  Anything outside the prepared options, such as a custom quote or a complaint.

• Someone asks for a person

  Messages like human, agent or talk to someone should always go to the inbox.

• Money or personal data is involved

  Refunds, orders and account problems deserve a person.

• The flow would repeat itself

  If the same fallback message is about to be sent a second time, stop and hand over instead.

Design the handoff step

1. 1
   Pause automation for this contact

   Once a person takes over, stop automated messages in that conversation so the bot does not talk over them.

2. 2
   Tell the contact what happens next

   Send one clear message, for example Someone from our team will reply here. Do not promise an exact time you cannot keep.

3. 3
   Route it to the right person

   Tag the conversation with the reason, so whoever handles that kind of request sees it first.

4. 4
   Pass on the context

   Show the trigger, the keyword and the messages so far, so nobody has to ask the contact to repeat themselves.

Mind the response window

On Instagram, Meta's messaging policy gives businesses up to 24 hours to respond to a user. For cases that need longer, the Human Agent tag allows businesses to manually respond within a 7-day period.

That tag is the reason the handoff matters. It covers people replying manually, not automated follow-ups. A flow that recognises a conversation needs help should route it early, while a normal reply is still possible.

Write the fallback message carefully

Every flow needs a fallback for input it does not understand. A good fallback admits it, offers the most common options again and mentions that a person can help.

Measure the handoff

Track how often conversations reach a person and how long they wait. A rising handoff rate usually points to a flow that misses common questions. Long waits point to routing or staffing. More on this in what to measure.