Connect a qualifying Facebook Page or Instagram Business account to Manychat, configure at least one automation trigger, and send a test message to confirm end-to-end delivery. That is the complete setup, and it takes under an hour when the prerequisites below are already in place.
What You Need Before You Start
| Requirement | Have It? | Where to Get It |
|---|---|---|
| Facebook Page (not a personal profile) or Instagram Business or Creator account | Yes / No | Facebook Business Suite or Instagram settings under Account Type |
| Admin access to that Page or account | Yes / No | Page Settings > Page Roles, or Meta Business Suite > People |
| A Manychat account (free tier available) | Yes / No | Review the provider’s current plans and terms before subscribing. Final pricing and promotional terms may vary by plan, billing cycle, usage, region, and eligibility. |
| A verified phone number for SMS workflows (optional at setup) | Yes / No | Acquired through Manychat's SMS provisioning flow after account creation |
| Browser with third-party cookies enabled or the Meta app authorisation flow completed | Yes / No | Browser settings; Safari and Firefox may require a temporary exception |
Expected Outcome When This Tutorial Is Complete
By the end of this guide your Manychat account will be authenticated against at least one Meta channel, one automation flow will be live and assigned to a trigger keyword or entry point, and you will have received a confirmed test message proving the delivery path works.
Two implementation details trip up most setups before a single message is sent. First, Instagram automation requires that the connected account be classified as Business or Creator at the Instagram level, not just linked to a Facebook Page. Second, the Meta permissions dialogue during OAuth must be accepted in full; partial approval silently blocks trigger delivery without showing an error inside Manychat.
Teams running multiple client sites will also want to note that each connected Page or account occupies its own Manychat workspace. Plan limits apply per workspace, so a five-site operation and a fifty-site operation face meaningfully different subscription structures. Section 3 of this guide covers workspace organisation and plan selection in detail.
Steps 1 to 3: Building Your Manychat Foundation the Right Way
Evaluate the workflow benefit against your own baseline rather than assuming a specific measured outcome. These three steps cover account connection, channel selection, and your first working flow — along with the verification checks that confirm each stage actually landed.
Step 1: Connect Your Business Page or Channel
The first decision in any honest Manychat tutorial is which channel you're automating. Manychat supports Instagram Direct Messages, Facebook Messenger, and SMS as its core conversation surfaces. Before you create anything, connect the correct business asset — a Facebook Page with admin-level access, or an Instagram Professional account linked to that Page.
A common failure point here: connecting a personal Instagram profile instead of a Professional account. Manychat requires the Instagram Professional account type, and the integration will appear to succeed while silently refusing to send automated replies. Verify by navigating to the Connected Channels section in your Manychat dashboard and confirming the channel status reads as active, not pending or restricted.
Step 2: Define Your Entry Point (Trigger)
Every automation in Manychat starts with a trigger — the event that opens the conversation. Choosing the wrong trigger type for your goal is the single most common setup error.
If your goal is lead capture for a real estate workflow, a keyword-based comment trigger on listing posts is a reliable starting point. A user comments a word like "details," and Manychat sends them a DM automatically. Verify the trigger is live by posting a test comment from a secondary account and confirming the automated reply arrives within a few seconds.
Step 3: Build and Test Your First Flow
Use Manychat's visual flow builder to map the conversation path after the trigger fires. Keep your first flow to three or four steps: a greeting message, one qualifying question, a response branch, and a follow-up action such as tagging the contact or capturing an email.
Evaluate the workflow benefit against your own baseline rather than assuming a specific measured outcome.
Steps 4 to 6: Building Flows, Connecting Triggers, and Verifying Your Setup
With your account connected and your first automation shell in place, the next phase is where most implementations either solidify or stall. These three steps require the most deliberate attention on the path to understanding how to set up Manychat for a sustainable, multi-site workflow.
Step 4: Build Your First Automation Flow
Open the Flow Builder from the left-hand dashboard panel. The canvas-based editor lets you add action steps—send a message, ask a question, apply a tag, set a custom field, or branch on a condition. Start with a single linear path before adding branches. Always add a default reply or a fallback step at every branch endpoint before saving.
Step 5: Attach Triggers to the Flow
A flow without a trigger is inert. In the Growth Tools or Triggers panel, assign the entry point: a keyword reply, a post comment, a story mention, an SMS opt-in, or a link click, depending on your channel. Keyword triggers are case-insensitive by default, which reduces missed matches but can also fire on unintended replies. Test the exact keyword your audience is likely to send, including common misspellings, before going live. On any paid plan, you can set multiple keywords per trigger; on a free plan, review current plan documentation to confirm what trigger types are available, since channel and trigger access can change between billing cycles.
Step 6: Send a Live Test and Confirm the Verification Checklist
Before any flow reaches a real audience, send yourself a test conversation using the Preview or Test Flow function. Then verify the following:
- The entry trigger fires on the exact keyword or action you configured
- Each branch endpoint has a reply action or a graceful exit step
- Custom fields and tags are being written correctly—check the contact profile after the test
- Any external integrations (webhooks, CRM connections) return a success response, not a timeout
- Opt-out language appears where your channel or region requires it
A flow that passes all five checks is ready for a limited rollout. Expand the audience only after confirming that conversation data is landing correctly in your contact records.
Troubleshooting Your Manychat Setup: Common Failures and Fixes
Even a carefully planned setup can stall at unexpected points. The failures below show up repeatedly when teams work through how to set up Manychat across multiple client accounts, and most have a clear fix once you know where to look.
Connection and Permission Errors
The most frequent early blocker is a failed channel connection. Facebook Page and Instagram connections require that the authenticating user holds Admin-level Page permissions, not just Editor or Analyst access. Re-authenticating under a stable admin account usually resolves it immediately.
Instagram connections carry an additional requirement: the account must be a professional (business or creator) account linked to a Facebook Page. A personal Instagram account cannot be connected regardless of plan level.
Flows That Trigger Incorrectly or Not at All
A flow that does not fire is almost always a trigger configuration issue rather than a platform defect. Check that the trigger keyword is saved without extra spaces, that case-sensitivity settings match your expected audience input, and that the flow is set to Active, not Draft. For Comment Automation flows, confirm that the connected Post ID has not been deleted or archived on the social platform after the flow was published.
Variable and Tag Failures
Custom fields that appear blank in sent messages usually mean the subscriber data was never collected or the field name in the message template does not exactly match the field name defined in the Audience section. Field names are case-sensitive.
Validation Checks Before Going Live
- Channel connection status shows green in Settings, not a reconnect prompt
- Test Flow confirms the correct message sequence fires end-to-end
- Opt-in triggers comply with the platform's current messaging policy requirements
- All custom field references in message templates match saved field names exactly
- Flows intended for multiple client accounts are scoped to the correct connected Page
How to Contact Manychat Support
The Manychat Help Center search covers most configuration questions and is the fastest starting point. For account-specific issues, the in-app chat support option connects directly with the support team. Community forums are useful for edge cases where other practitioners have documented workarounds, particularly for real-estate and lead-capture automation patterns that involve multi-step qualification flows.
Did It Work? Verification Checks Before You Go Live
Binary Checks: Confirm the Setup Worked
Run through each of these before treating your Manychat setup as production-ready. Each item has a clear pass or fail state — no judgment calls required here.
- Trigger fires correctly: send a test comment or DM keyword and confirm the automation activates within a few seconds.
- The correct flow branch executes: verify the subscriber lands on the intended path, not a default or fallback message.
- Channel connection is active: Instagram, Facebook Messenger, or SMS shows a green connected status with no permission warnings in the dashboard.
- Opt-in and opt-out responses send: confirm a subscriber can request to stop messages and receives the correct reply immediately.
- Any conditional logic resolves: if your flow uses tags, custom fields, or conditions, walk through each branch manually with a test account.
- Integrations fire: if you connected a CRM, Google Sheet, or webhook, verify a test record appears on the receiving end.
Ready to Go Live? Subjective Readiness Review
Passing the binary checks means the mechanics work. Readiness is a separate question. Consider whether your reply copy matches your brand tone across every branch, not just the first message. Review the unsubscribe path one more time from a compliance standpoint, since channel policies on this point are non-negotiable regardless of plan.
Frequently Asked Questions
Current plans and pricing: Review the provider’s current plans and terms before subscribing. Final pricing and promotional terms may vary by plan, billing cycle, usage, region, and eligibility.
Do I need a paid Manychat plan to complete this setup, or does the free tier cover everything in the tutorial?
The free tier lets you connect a channel, build a basic flow, and send a test message, so you can follow every step in this tutorial without paying anything upfront. Where free accounts run into limits is trigger variety and the number of contacts you can message. If your workflow needs multiple keywords per trigger or advanced conditions, check the current plan documentation before assuming free covers it — those boundaries shift between billing cycles.
Can I manage multiple client Facebook Pages or Instagram accounts from one Manychat login?
Teams with strict client-separation requirements should verify the relevant vendor's current account, access, and data-handling model before relying on it for that workflow. You can switch between them under the same login, but plan limits — contacts, flows, features — apply per workspace independently. A five-client operation and a fifty-client operation face very different subscription costs as a result, so map out how many workspaces you actually need before choosing a plan.
How long does it realistically take to set up Manychat from scratch if I already have the prerequisites ready?
Under an hour is realistic when your Facebook Page or Instagram Professional account is already in order and you have admin access confirmed. The OAuth connection takes a few minutes, building a simple three-step flow takes another fifteen to twenty, and testing adds maybe ten more. The part that surprises people is troubleshooting partial Meta permission approvals — that can quietly add time if you don't catch it at the connection step.
What happens to existing conversations if I disconnect and reconnect a Facebook Page or Instagram account?
Reconnecting a channel does not delete subscriber records already stored in Manychat, but active conversations may drop mid-sequence depending on how long the disconnection lasts and whether session tokens expire. Any flows that were mid-execution during the gap will typically not resume from where they left off. After reconnecting, verify the channel status reads active and run a fresh test conversation rather than assuming in-flight sequences recovered automatically.
Is SMS setup included in the same process, or do I configure it separately after connecting a social channel?
SMS is a separate provisioning process inside Manychat and does not depend on completing your Instagram or Facebook Messenger connection first. After your account is created, you step through Manychat's SMS provisioning flow to acquire a verified phone number. You will need a verified phone number of your own to complete that step. SMS and social channels run as independent conversation surfaces, so you can have one, the other, or both active at the same time.