When I used Manychat on a new project in 2019, we acquired a relevant contact for under CZK 5 and grew the database to 1,231 contacts. These are historical figures from one project, not a current benchmark or guarantee. Platform rules, advertising costs, and people’s expectations have changed since then.
The biggest mistake is unchanged: a company starts drawing a complicated chatbot before knowing which conversation it should simplify. The automation then resembles a telephone switchboard with seven options and no person.
When Manychat makes sense
- quick answers to recurring questions,
- delivering promised material after a clear interaction,
- qualifying a prospect with a few short questions,
- booking or handing a contact to sales,
- follow-up care within the rules of the specific channel.
It is not suitable for sensitive advice, complaints requiring individual assessment, or situations where the company cannot take over the conversation. Automation should shorten the journey, not lock out a person.
Start with one scenario
Write down the trigger, the user’s expectation, and the desired outcome. For example, a person comments on a post promising a checklist, confirms interest in a private message, receives a link, and can ask a question. That is the first flow. Add branches only after it works.
Manychat gathers current flow, condition, action, and other options in its official Automation section. Interface labels change; the trigger–condition–message–action logic remains.
The 24-hour window is not a minor detail
For Messenger, Instagram, and WhatsApp, Manychat works with a 24-hour window from the user’s last interaction. Its messaging windows documentation explains that automated messages outside the permitted window are blocked and that rules differ by channel and message type. Do not evade limits by renaming an advertisement as a service message.
Design the flow so the important value arrives immediately and later communication has its own legitimate channel. If you want to continue by email, ask clearly for the address and explain what you will send. See the articles about email marketing and GDPR in online marketing.
Comment automation
A comment trigger can open a useful path from a public reaction to a private conversation. According to the official Facebook Comments Trigger guide, a private reply alone does not automatically subscribe the user or necessarily open the 24-hour window; the user must interact with the message element.
Practical flow:
- The post clearly says what the person receives after commenting.
- The trigger reacts to a sensible keyword or all comments, according to the scenario.
- The public reply is natural and does not promise something different from the private message.
- The first private message asks for simple confirmation through a button or quick reply.
- After the interaction, deliver the promised content and offer a path to a person.
Handle repeated comments, your own administrator replies, and users who do not allow messages. Test from a personal account that is not a Page administrator.
How to write a flow
- One message has one question or one call to action.
- Name buttons after the outcome, not generically “continue”.
- Explain why you ask for a phone number, email, or company.
- Offer back, exit, and handoff to a person.
- Let users write their own answer where presets are insufficient.
For every branch, imagine someone answering differently than expected. If the flow has no path for them, the automation is not finished.
Data and integrations
Store only data with a clear purpose in custom fields. Agree on field names, source, retention period, and which system is the primary record. A CRM usually needs contact identity, source, qualifying answers, time, and consent where relevant. It does not need every technical tag from every branch.
Test integrations with errors too: a duplicate contact, missing email, unavailable webhook, and delayed sales reply. Tag advertising links according to the shared guide for UTM parameters, but never put personal data in URLs.
Measure completed work
Subscriber counts or opened messages are operational signals. For outcomes, track:
- how many people meaningfully started and completed the flow,
- where and after which question they dropped out,
- how many conversations a person took over and how quickly,
- how many qualified inquiries or orders resulted,
- how many people ended, blocked, or reported the flow.
Once a month, review active automations, their owners, and whether their promises are current. An old flow under a year-old post may still distribute an invalid link.
Safe launch
- Choose one recurring scenario with clear value.
- Draw the shortest route and the handoff to a person.
- Verify the specific channel’s rules in current documentation.
- Test every branch, mobile, errors, and the integration.
- Launch to a small part of traffic and watch negative signals as well as conversions.
- Add another flow only according to the data.
Manychat is useful when customers receive a relevant answer faster. If it merely lets a company send more messages to more people, it is mostly an amplifier of the problem. We can review the automation design and follow-up measurement via contact.