The agent was unable to access ManyChat's official website directly (blocked by Cloudflare), but successfully assembled a comprehensive explanation by synthesizing information from six third-party sources (blog posts, help articles, and comparison sites). The agent provided clear answers to what ManyChat does, who it's for, how it's priced, and how it compares to alternatives—though several details remain unclear due to reliance on secondary sources rather than official documentation.

• ›The official ManyChat domain returned 403 Cloudflare challenges on both homepage and pricing page ([1], [2]), forcing the agent to pivot entirely to web search and third-party sources. The agent never accessed any content directly from manychat.com itself.
• ›Web search results ([4]) surface third-party pricing analyses and help documentation (help.manychat.com), but not the primary website. The agent fetched five third-party sources ([5], [6], [9]) and two additional searches ([7], [8]) to build the answer. All final-answer citations point to external blogs and help docs, not primary product pages.
• ›The site is effectively invisible to agent navigation—not because information doesn't exist, but because the primary domain is inaccessible. An agent cannot verify current pricing, confirm feature availability, or read official positioning statements. Pricing details came from third-party reviews dated 2026, which may lag behind actual changes.
• ›Confusing gaps explicitly called out by the agent reflect gaps in what the third-party sources disclosed: AI quality comparisons, exact WhatsApp/SMS per-message rates, contact overage mechanics, and integration ecosystem scope. The agent flagged these honestly rather than inferring from prior knowledge.
• ›The agent's pricing table and comparison framework are reliable (multiple sources converged on the same figures), but the agent noted the pricing model was recently restructured (March 2026), and secondary sources may not reflect the latest changes. Direct access to manychat.com/pricing would have resolved this uncertainty immediately.