“Interested!” is not a registration. A person can comment, receive a DM, click a ticket link, and still leave without a ticket.
Build your event campaign around that last gap. Instagram should help people understand the event and reach registration. The ticketing system should confirm their place, collect any payment, and send the information they need to attend.
This division gives you a simpler flow and a count you can trust. It also prevents the embarrassing message that says “You’re in!” to someone whose payment failed.
Put the event details where people can decide
Before building the automation, publish a complete registration page. Include the event date, time zone, location or online format, price, what the ticket includes, and the cancellation or refund terms you actually offer. Say whether there is a recording. If you do not know yet, do not let an automated answer invent one.
Your Instagram post should reveal enough for someone to choose whether to continue. Hiding the price until the end of a chat may produce more conversations while wasting everyone’s time.
Give the campaign a specific request: “Comment CLAY for the Saturday workshop details and booking link.” That is clearer than “Comment YES to transform your creativity.” Use a keyword tied to the event, especially when several promotions run at once.
Keep one person responsible for the source page and automation. If the workshop moves, sells out, or closes registration, both need to change.
Use the first DM to deliver, not declare success
For a simple event, the opening private reply can contain the details and ticket link. This keeps the journey short. The important tradeoff is that a website click alone does not open a continuing Instagram messaging window.
If attendees commonly need help choosing a session, use an in-chat Quick Reply first. Manychat’s comment-trigger documentation distinguishes a regular button or Quick Reply interaction from an Open website action: the former can establish the interaction needed to continue; the website action does not.
Here is an illustrative flow for a fictional ceramics workshop. The date, price, and venue are examples:
- Post: “Make your first mug on November 14, 2026, 10 a.m.–noon Eastern, at Maple Ceramics, 12 Example Lane. Tickets are $55, including materials. Comment CLAY for the booking link and directions.”
- Opening DM: “Here for the mug workshop? Tap below for the details.” Add a Quick Reply labeled “Show workshop.”
- Details: Restate the date, local time zone, duration, price, and venue. Link to the registration page. Offer “Ask a question” as an optional path.
- Checkout: The attendee chooses tickets and completes registration on the ticketing site.
- Confirmation: The ticketing system sends the confirmation and attendance instructions after a successful registration.
These are sample messages, not results from an actual campaign. Fill in real details before using them. Do not copy “materials included” if attendees need to bring their own supplies.
Let checkout own payment and capacity
Sending a payment link in a DM does not mean payment happens natively inside the chat. For this workflow, send people to your established ticket checkout, where they can see the price, complete payment if required, and receive confirmation.
A Manychat tag such as “interested in workshop” is useful for routing. It should never be the final attendee list. Likewise, a “Book now” click is evidence of a click, not a purchased ticket.
Eventbrite’s order-confirmation documentation, for example, places the confirmation page after successful order completion and lets organizers add information to the confirmation email and ticket. That is the right stage for arrival instructions, what to bring, and how to contact the organizer.
If you connect ticketing back to the automation, update registration status only from a verified registration or order event. Decide how duplicate notifications, refunds, and cancellations affect that status. Never mark someone registered because they reached the checkout page.
For a first campaign, you may not need that integration at all. A reliable ticket page and confirmation email can complete the job. Add synchronization when it solves a real operating problem, such as staff repeatedly checking two systems.
Plan reminders on a channel that can send them
An event next week needs a reminder next week. An Instagram comment today does not establish permission for that message.
Meta’s private-reply rules allow follow-up messages only after the recipient responds, and within 24 hours of that response. Manychat’s standard messaging-window guidance says scheduled automated messages are prevented from sending once the window closes. A delay block does not extend it.
Use your registration platform’s attendee communication for essential event instructions and reminders, following its settings and the permissions you have collected. Keep an optional marketing subscription separate from registration. If you offer SMS reminders, make that channel choice explicit rather than treating an Instagram interaction as consent.
Eventbrite documents automatic reminder emails for published events: 48 hours before an in-person event, and 48 hours, two hours, and ten minutes before an online event. Inspect those settings before adding your own schedule, or attendees may receive duplicate reminders. Other platforms have different defaults.
Do not try to turn the human-agent support extension into a reminder workaround. respond.io’s Instagram documentation explicitly excludes automated messages and content unrelated to the person’s inquiry from that extension.
Borrow the useful part of other campaigns
In Manychat’s Floreat Forum case study, agency founder Amberlea Henriques describes offering event guides and asking people whether they wanted reminders. Borrow that relevant offer and explicit choice. The older, vendor-published case used Facebook Messenger notification features; it establishes neither current Instagram permissions nor the ticket sales you should expect.
Give unusual questions a person to reach
Automated answers can cover published details such as duration, location, and whether supplies are included. Route questions about accessibility arrangements, payment problems, cancellations, or exceptions to someone who can resolve them.
Ask only for what is necessary to handle that question. Avoid collecting detailed personal information in a public comment or an improvised DM questionnaire. Give attendees an appropriate private contact route when more detail is needed.
The handoff should include the event and the question already asked. Pause the flow while a team member responds. An attendee asking for a refund should not simultaneously receive a message encouraging them to buy another ticket.
Test the sold-out version too
A prelaunch test should cover more than the happy path. Use a new account to trigger the actual post, find the private reply, tap through, and complete a test registration using your ticketing provider’s supported process.
- Check a nonfollower account. Meta says those private replies go to Requests.
- Check that a failed or abandoned checkout produces no registration confirmation.
- Check sold-out and closed-registration pages. Offer a waitlist only if one actually exists.
- Check the confirmation on a phone, including the time zone, location, and joining instructions.
- Check late entry into the campaign, after the event has ended. Retire the invitation or replace it with an honest update.
Manychat’s comment trigger only runs for the first comment a person leaves on a post or Reel, so use a suitable fresh test rather than repeatedly posting the keyword from one account.
Count registrations and attendance separately
Give the DM campaign its own ticket link. Eventbrite’s promotional tracking links report visits and ticket sales associated with each link; its documentation notes that views can take longer to appear than sales. Preserve the generated link exactly when sharing it.
Put that campaign link in the DM’s booking button. Use separate links for the profile bio, email, and any partner promotion; reusing the DM link everywhere makes its sales total impossible to interpret. Complete a test order from the actual DM button, confirm it appears under the intended link, and exclude the test from your campaign totals.
Record the path from distinct requesters to ticket-page visits, completed registrations, and checked-in attendees. Choose whether your report counts orders, tickets, or people: a single buyer purchasing four tickets makes those totals different.
Calculate attendance against valid registrations after cancellations, then examine where people were lost. A weak checkout rate calls for a review of price, details, or checkout friction. A weak attendance rate calls for a review of reminders, joining instructions, and the event’s timing. They require different fixes.
Campaign links show recorded attribution, not proof that automation created every sale. For the financial side, use our DM automation ROI guide. To sketch the campaign before building it, use the DM Campaign Field Guide and name the exact event that will mean “registered.”
First published . Updated with current research and practical examples.
