> ## Documentation Index > Fetch the complete documentation index at: https://knowledge.flowella.io/llms.txt > Use this file to discover all available pages before exploring further. # Setting up Meta for WhatsApp Business: end-to-end sequence > The eight steps required to go from no Meta presence to a WhatsApp Business Account ready for Flowella, in order, each linking to the detailed guide. Setting up Meta is the part of Flowella onboarding that surprises most teams. There are eight discrete steps, each of which Meta gates separately, and missing one usually means you cannot move forward until you go back and complete it. This page is the map. If you already have a WhatsApp Business Account (WABA) that is verified, billed, and approved to send messages, you do not need to start here — jump straight to [Connect Flowella to HubSpot](/hubspot/setup) and pick up the integration steps. Everything below is for teams setting Meta up from scratch. ## The sequence A **business portfolio** (formerly called a "Business Manager" account) is the top-level container Meta uses to group your business assets — Facebook pages, ad accounts, WhatsApp Business Accounts, and so on. Most agencies and product companies already have one; if you don't, you create it at business.facebook.com. Detailed walkthrough coming soon. For now, follow Meta's own guide and confirm your **15- or 16-digit business portfolio ID** afterwards. Meta needs three things on the portfolio before it will let you do anything serious: * A **main contact person and email address** * The **legal operating name** of your business * The **registered legal address** of your business These have to match public records (Companies House in the UK, the equivalent registry in your country). Mismatches are the most common reason verification stalls. Meta runs an automated check against the information above plus public records and your website. The **Start Verification** button appears in your portfolio's Security Centre once the business info is complete — except in newly created portfolios, where it can stay greyed out until a "dummy" asset (typically a Meta App) is attached. See [Business information & verification](/meta/business-verification) for the full procedure including the Start Verification workaround. A **WABA** is the WhatsApp-specific container that sits inside your portfolio. It holds your phone numbers, your business profile, and your message templates. You can create a new WABA via Flowella's Embedded Signup during onboarding, or attach an existing one if you already have it. You need a real, working phone number that is not already registered with the consumer WhatsApp app or the WhatsApp Business app. Mobile numbers and landlines both work; toll-free, freephone, and IVR-routed numbers do not. See [Phone numbers explained](/meta/phone-numbers) for the full eligibility rules and the verification options (SMS or voice call). Your **display name** is what customers see in WhatsApp instead of your phone number. It has to comply with Meta's naming policy and is reviewed for 1–3 business days before going live. Cover the rest of the profile (logo, description, business hours) at the same time. See [Display name & profile](/meta/profile-setup). WhatsApp messages cost money beyond Meta's free tier. You need a card attached at the WABA level, set as **Default**, before Meta will continue delivering messages once you exhaust the free service tier. See [Meta payment method](/meta/payment-method). Open Flowella's [Dashboard](/app/dashboard) and check the **Channels** section. A healthy WABA shows the green status indicator and an approved business verification badge. If anything is amber or red, follow the troubleshooting links inline to resolve it. ## Where each step blocks Understanding which step gates which is the difference between a 30-minute setup and a three-day stuck ticket: * **Steps 1–2 gate step 3.** You cannot start verification without a portfolio and complete business information. * **Step 3 gates step 7.** You cannot add a working payment method to an unverified WABA, and unverified accounts cap at 250 unique recipients per 24 hours. * **Step 5 gates step 6.** Display name approval runs against the phone number, so the phone number needs to be registered first. * **Step 6 gates messaging.** Templates need an approved display name to send under the business name instead of the raw number. * **Step 7 gates volume.** Without a Default card on the WABA, Meta will eventually pause message delivery. ## Co-existence: a shortcut if you already use the WhatsApp Business app If you currently use the WhatsApp Business app on a phone with the number you want to keep, you can **co-exist** rather than fully migrate. Co-existence connects your existing number to the Business Platform while leaving the app working for 1:1 chats. It skips parts of steps 4–6. See [Co-existence](/meta/co-existence). ## After Meta is set up With the Meta side complete, the rest is the Flowella integration: * [Connect Flowella to HubSpot](/hubspot/setup) — link your HubSpot portal, choose Quick Start templates, finish onboarding * [Workflow Actions](/hubspot/workflow-actions) — wire up triggers and actions in your HubSpot workflows * [Templates](/app/templates) — build the first WhatsApp template you want to send If you get stuck at any point, the [Troubleshooting](/troubleshooting/onboarding) page covers the most common Meta-side problems and their fixes.