A comment keyword is a useful event, but it is not a complete lead. The person has raised a hand; the workflow still has to deliver the public promise and learn enough to choose a useful next step.
Here is a practical model for an Instagram waitlist that behaves like a small state machine instead of a generic autoresponder.
State 1: promise received
The public post defines the contract. If it says “Comment WAITLIST for the launch details,” the first DM should contain those details immediately.
Do not gate the promised information behind a survey. Delivery is the success condition for the first state.
A useful payload is short:
- acknowledge the comment;
- provide the promised overview or link;
- explain what the link contains;
- ask one optional question.
State 2: one answer changes the route
Choose a question whose answer changes the next message. Good examples include:
- Are you buying for yourself or a team?
- Are you using a spreadsheet, another tool, or nothing yet?
- Is your goal to learn the workflow or have someone implement it?
If every answer produces the same response, the question is decorative. Define the branches before the post goes live.
A solo creator may need a starter guide. An agency may need multi-account information. A person with an urgent project may need a booking link, while someone exploring may need a concise product tour.
State 3: store useful context
Record the trigger, source post, answer, and resulting branch with the contact. That context prevents the next human message from restarting the conversation.
DMComments can use comment keywords to start a workflow, send the promised resource, capture a lead, and continue through a path you define. Its product-launch template follows the same pattern: comment, waitlist entry, qualification, and a relevant next step.
Handle non-ideal input
Test more than the exact keyword in the setup screen:
- Different capitalization and extra spaces.
- A keyword inside a sentence.
- A typo or unrelated reply.
- No answer to the follow-up question.
- A new question that needs a human.
- The same person commenting twice.
The goal is not to automate every conversation. It is to make the common path reliable and make human takeover obvious.
Measure state transitions
A comment count alone cannot tell you whether the waitlist works. Track:
- comments that triggered the intended workflow;
- successful delivery of the promised resource;
- answers to the qualifying question;
- movement from each answer to the next useful action;
- the state where people stop.
These numbers reveal whether the problem is the public CTA, first DM, question, branch, or destination.
A good waitlist respects the small commitment the commenter already made. Deliver first, ask one question that matters, and make the answer change what happens next.
Explore the workflow templates and interactive demo at DMComments.
Top comments (1)
Modelling the waitlist as a branching conversation is the right abstraction: the comment keyword is intent, and the next two or three questions decide what kind of lead it is. I built chatform.in on the same idea for forms outside Instagram (questions as a conversation, follow-ups on vague answers, webhook out). How do you handle people who stop replying after the first branch?