How to Build an Instagram Lead Qualification Flow
CommentLink flows include conditions, buttons, delays, tags, email/phone collect, follow-gate, AI reply, HTTP request, and human-handoff. An Instagram lead qualification flow should use as few of those as the job needs. This is how to assemble one — not a second “do you need a flow builder” essay, not the comment keyword strategy, and not the question list.
Start with one keyword, one question, two branches, and a human-handoff. Add nodes only after the simple version works. Fallback is not optional — people will type novels. AI in this flow is CommentLink’s ai_reply node, not Meta Business Agent, and it should not invent prices.
Minimum viable qualification flow
- Trigger: comment keyword or inbound DM keyword (comment_keyword, reel_comment, or dm_keyword). Not Live, not Trial Reels, not Click-to-Direct ads.
- Send message: confirm the ask and include anything the caption promised.
- Buttons or a question: two intents max on version one (BOOK versus INFO).
- Condition: route BOOK versus INFO on the reply or the tap.
- add_tag on each path so the inbox is filterable.
- Human-handoff when they type something you did not plan.
Do not start with HTTP request, follow-gate, and AI on day one. Those are extras after the two-path version is boring and correct. Simple versus multi-step: simple Instagram automation vs multi-step.
A concrete canvas: education Reel
Trigger: comment FEES. Node 1 send_message: “Current fee page: [URL]. Need the syllabus PDF or a counsellor for a custom batch?” Node 2 send_buttons: SYLLABUS | COUNSELLOR. SYLLABUS → send PDF URL, tag browser, stop. COUNSELLOR → “Reply with city + month.” Condition on city list → tag buyer, send counsellor hours, human-handoff. Fallback: “I can send the fee page (already above) or pass you to a person — reply HUMAN.”
Silent people already have the fee page. That respects one private reply per comment. Later buttons only matter if they tap. Do not delay 12 hours and send COUNSELLOR unsolicited.
Fallback is not optional
People will type novels. Fallback messages in Instagram DM automation keeps them from hitting silence. A fallback is a last scripted line plus a door: HUMAN, or the public asset again — not a third sales URL they did not ask for.
If they fail the same fallback twice, stop. Hand off. Looping “sorry I didn’t get that” is how you look like a broken IVR at 11pm IST.
AI in this flow — tight boundary
CommentLink has an AI reply node. It is not Meta Business Agent, and it should not invent prices. Boundaries: AI for Instagram lead qualification. Use AI after a human would have typed anyway — a long inbound that is not BOOK or INFO. Do not let it own checkout or fees.
Put ai_reply behind a condition: only if they did not match BOOK/INFO/HUMAN. Cap it. Then handoff. A model that “sounds helpful” can still send the wrong batch date.
Wiring steps you can copy
- Name the flow after the keyword, not “master bot.”
- Draw two boxes on paper: browser asset, buyer URL. If you cannot, you do not need a flow yet — you need a caption.
- Build trigger → send_message (payload) → send_buttons (two) → condition → tag → stop or handoff.
- Add fallback on unmatched text.
- Add collect_email only if the browser path actually uses a list. Do not collect to look busy.
- Test: keyword comment, button A, button B, garbage sentence, HUMAN. Five outcomes.
Funnel language if you need it: qualification funnel. Handoff design: handoff workflow. Criteria for who is sales-ready: sales handoff criteria.
Mistakes that fatten a simple job
- Twelve nodes before the first URL. Instead: payload in node 1.
- Follow-gating a fee page on a tourist Reel. Instead: send the page; gate only if you accept fewer sends.
- HTTP request to a CRM CommentLink does not sync natively. Instead: tag + export. Do not block the DM on a brittle webhook.
- One flow for GUIDE, FEES, and REFUND. Instead: separate triggers. Refund is handoff, not a branch of FEES.
- Delay as fake typing. Instead: delay is for spacing after they reply, not theatre.
- Silent WhatsApp hop mid-flow. Instead: they write WhatsApp; wa_keyword is a different trigger.
Copyable node list for version one
comment_keyword FEES → send_message (fee URL + Requests note) → send_buttons (SYLLABUS | COUNSELLOR) → condition → add_tag → (send PDF | ask city + human_handoff) → fallback → human_handoff after two fails.
Do not add ai_reply, follow_gate, or collect_phone until that path is correct on a second account. Version two can collect email on SYLLABUS if you will actually mail the list.
What CommentLink cannot do in a qualification canvas
No Live comment trigger, no Trial Reels trigger, no Broadcast Channel posting, no Click-to-Direct ads, no Shopify catalog messaging, no Meta Business Agent, no native HubSpot CRM. No silent comment→WhatsApp. Instagram triggers you can actually use: comment_keyword, reel_comment, story_reply, story_mention, dm_keyword, new_follower. WhatsApp: wa_keyword, wa_first_message, wa_template_reply — after they are on WhatsApp.
The canvas will not guess your branches. If BOOK and INFO need the same URL, you do not have a qualification flow. You have a link sender — and that is fine. Delete the extra nodes.
A second canvas: salon BOOK versus PRICE
Trigger: comment_keyword BOOK or PRICE — two automations, not one spaghetti graph. BOOK → send_message with the colour-booking URL and hours in IST → fallback HUMAN. PRICE → send_message with starting rates → send_buttons (BOOK NOW | JUST RATES). BOOK NOW can send the same scheduler. JUST RATES stops. If they type “last colour fried my hair,” condition on BURN/FRIED/REFUND → human-handoff, no Saturday promo.
Conditions should match words you would bet money on: city names you serve, BOOK, INFO, HUMAN, REFUND. Do not condition on “interested” — everyone is interested in a vacuum. If you need more than two buttons on version one, you do not have a qualification flow yet. You have a menu. Split Reels.
Follow-gate belongs after you decide the payload is worth withholding. Gating PRICE on a tourist Reel means fewer rate-card sends. That is a growth tactic, not qualification. Qualification is BOOK versus INFO, not follower versus not.
Story reply path: a merch or hours sticker can use story_reply with the same two buttons. It is a second trigger into a copy of the flow or a shared flow if your builder allows it. It is not a second private reply on the Reel comment.
Clothing brand version one: comment SIZE → chart URL in send_message → buttons (RESTOCK | WHOLESALE). RESTOCK tags browser and stops. WHOLESALE asks MOQ band; unpublished quantities go to human-handoff. Do not add collect_phone until wholesale actually calls. Delay, if you use it, only after they tapped — never as a silent second chart.
FAQ
How do I build an Instagram lead qualification flow?
Start with one keyword, one question, two branches, and a human-handoff. Add nodes only after the simple version works. Put the promised asset in the first send.
Which trigger should I use?
comment_keyword or reel_comment for caption keywords; dm_keyword for inbound. Not Live, not ads CTD, not Trial Reels.
Is fallback required?
Yes. People type novels. A fallback plus HUMAN beats silence or an infinite sorry-loop.
Should AI qualify the lead?
Not for prices, seats, or legal. Use ai_reply for unmatched language, then hand off. Keep checkout on a script.
Can the flow continue if they never reply?
Not as extra private replies on that comment. Design message one to stand alone. Later nodes wait for inbound.
Do I need HTTP request on day one?
No. Tags are enough. A webhook that blocks the DM is how a launch dies. Add it later if you actually maintain it.
Should BOOK and PRICE share one flow?
Usually no. Two triggers, two first DMs. Share a human-handoff pattern, not a twelve-node graph that tries to be both.
Related reading
See Instagram DM automation
Comments, Stories, keywords, follow-gates, lead capture and a shared inbox — official Meta APIs.
See DM automation