Without a system
Chasing details by hand.
- Asking for an email in a separate message later
- Details scattered across chats and notes
- No reason given for the information you need
- Resource requests mixed up with newsletter sign-ups

A Linkar webinar enquiry recipe. Share the date and registration route, collect requested contact details, and keep confirmed attendance clearly defined.
Free to start. Paid plans from ₹199 a month.
Instagram · Enquiry in a conversation
Resources and enquiries
Use this recipe for viewers who request information about an online event.
Share an accurate event page or collect the details needed for a joining-information request.
Make the date, local time, and confirmation process clear.
An Instagram acknowledgement is not automatically a registration in an external event platform.
Recipe in 3 steps
Replace the sample copy and links, then test the supported journey in your own account.
Check date, time, topic, joining format, and registration terms. Use a maintained destination rather than a temporary private link.
Choose WEBINAR or a distinct event word. Configure any contact questions only for the purpose you explain.
Complete the external registration route and check the confirmation. Disable or update the Instagram flow once the event ends.
Before and after
Without a system
With Linkar
Example conversation
Follow one request from the moment it arrives to the step after the reply.
Before you start
Four things and no developer. With these ready, you can build this workflow and test it from another account.
An Instagram professional account
Business or Creator. Personal Instagram accounts are not supported.
A reason for every detail you ask
Explain why you need an email or an answer before you ask for it.
The free plan to start
5 automations and 1,000 messages a month. Features and limits depend on the plan.
No code
Choose the interaction, write the reply, and test it from another account.
Why it helps
Collect only what helps, and keep it beside the conversation it came from.
Give each webinar its own destination and campaign word where practical. Old posts should not send a different event without explanation.
Tell people whether they still need to complete registration. A saved contact and a confirmed attendee are separate stages.
Before you switch it on
A caption saying ‘tomorrow’ becomes confusing later. Keep the absolute date and intended local time visible. If you collect details in Linkar, verify how they enter the event process rather than assuming a connection exists. Later reminders need the appropriate communication permissions.
Campaign notes
Explain the purpose before asking for an email or an additional answer. Linkar can validate an address’s format and save configured conversational fields with a contact. Format validation does not prove mailbox ownership. A short intake should give your team relevant context, while retry and exit messages keep the process understandable.
A saved address is not blanket permission for recurring marketing. Keep requested resource delivery and newsletter enrolment distinct, and test any external handoff you configure. Collect only the information needed for the enquiry. Review the completed record and fulfilment step yourself before calling the campaign a working lead journey.
Only if you have configured and tested an appropriate process or supported connection. This recipe can share the registration link or collect an enquiry; external attendee registration is a separate step.
No. Use Linkar’s supported builder options to choose the interaction, write your messages, and configure the next steps. Supply your own destinations and test the full journey. If you need help with an account or delivery issue, contact support.
Still have a question?
Your next reply starts here
Start free with 5 automations and 1,000 messages a month. Choose an interaction, write the answer, and test your first workflow.
Free₹0a month
Creator₹199a month