Getting Started with WABA.FLOTA: Complete Setup Guide
If you've just signed up for WABA.FLOTA and aren't sure what to click next, this is the complete path from "brand-new account" to "sending and receiving real WhatsApp messages" — no technical background required.
Step 1: Create your account
Go to the login page and sign in with either your phone number (OTP) or your Google account. Both methods work identically — whichever one you use first becomes your permanent login, so pick the one you'll always have access to.
Step 2: Complete onboarding
The first time you log in, you'll land on a short 2-step onboarding wizard:
- Business name — this becomes your workspace name across the dashboard.
- Choose a plan — Starter, Growth, or Pro (you can change this later from Dashboard → Plan Matrix, no need to overthink it now).
Once you submit, your workspace is created instantly and you're dropped into the dashboard.
Step 3: Connect your WhatsApp number
This is the step that actually makes the bot able to send and receive messages. In the dashboard, look for Connect WhatsApp Number:
- Click it — a Meta (Facebook) popup opens.
- Log into your own Facebook Business account inside that popup.
- Pick or create a WhatsApp Business Account (WABA), and verify the phone number you want to use.
- Close the popup once it confirms — WABA.FLOTA automatically receives everything it needs (the number, the access token, webhook subscription) in the background. There's nothing to copy-paste manually.
Until this step is done, your dashboard will show the connection as pending — that's expected, and normal to see for a minute or two while Meta's side finishes verifying.
Don't have a Meta Business account yet? You'll need one before this step — it's free to create at business.facebook.com, and your WhatsApp number must not already be actively used inside the regular WhatsApp Business app (Meta requires it be free for API use).
Step 4: Set your AI agent's personality (optional but recommended)
Go to Dashboard → Bot Prompt. This is where you tell your AI sales agent who it's representing — your business name, tone (formal/friendly), what it should and shouldn't say, and any specific policies (pricing, delivery, refunds). A good starting prompt is 3–5 short paragraphs; you can always refine it later based on real conversations. See our dedicated guide on building your AI sales agent for a full walkthrough.
Step 5: Send a test message
Once your number shows as connected, message it yourself from a personal WhatsApp number. You should get a reply within a few seconds — that confirms the whole pipeline (webhook → AI agent → reply) is working end-to-end.
What to set up next
With the basics live, the next things worth configuring are usually:
- Dashboard → Menu — if you sell physical products, add your catalog so the AI can quote prices and take orders.
- Dashboard → Website API — if you have your own website/backend, connect it so the AI can pull live stock/order data instead of guessing. See how to connect your website.
- Dashboard → Campaigns — once you have subscribers, you can send them broadcast messages. See how to run broadcast campaigns.
- Dashboard → Team — invite staff and set up shared inbox routing if more than one person will be replying to customers.
Common setup questions
Why does my WhatsApp connection still say "pending" after I closed the popup?
Meta's verification can take a minute or two. If it's still pending after 10+ minutes, disconnect and retry the Connect WhatsApp Number flow — a half-finished popup session is the most common cause.
Can I use a WhatsApp number that's already active in the regular WhatsApp Business app?
No — a number must be available for API use, meaning it isn't currently logged into the standard WhatsApp Business mobile app. Migrate or use a fresh number.
Do I need a developer to do any of this?
No. Everything above is click-through from the dashboard. The only exception is if you want a custom integration with your own website's backend, which the Website API guide covers — even that is a no-code form, not custom development.