FaceBot WhatsApp Core gives businesses one place to connect WhatsApp, verify that the account is ready for API sending, and monitor the setup conditions that can affect campaigns and automated messaging.
Instead of treating WhatsApp setup as a one-time connection, FaceBot keeps important account signals visible after onboarding—including connection mode, display name approval, phone registration, messaging capacity, coexistence sync, and Meta billing health.
This helps your team answer a practical question before launching WhatsApp activity: Is this account actually ready to send?
What is WhatsApp Core in FaceBot?
WhatsApp Core is the WhatsApp Connection area inside FaceBot Settings.
It manages the connection between your FaceBot workspace and Meta's official WhatsApp Business Platform and provides ongoing visibility into the health of that connection.
FaceBot supports two main connection paths:
- WhatsApp Business App + API (Coexistence): Keep using your existing WhatsApp Business number in the mobile app while also connecting it to FaceBot.
- WhatsApp Business Platform (API Only): Connect a dedicated WhatsApp API number directly through Meta's platform.
After setup, WhatsApp Core becomes the place where administrators can review the connected phone number, WhatsApp Business Account information, connection type, registration state, approval progress, account capacity, and billing-related status.
Why WhatsApp Core matters
Successfully connecting a WhatsApp number does not automatically mean every WhatsApp feature is ready to operate.
Campaign sending can still depend on conditions such as:
- Display name approval
- Cloud API phone registration
- Valid registration PIN state
- Meta account health
- Available messaging capacity
- Active campaign constraints
- Billing or payment status
FaceBot brings these signals into one setup and monitoring workflow so users do not need to guess why a WhatsApp campaign cannot start.
Connect WhatsApp through Meta Embedded Signup
FaceBot uses Meta's official Embedded Signup flow for WhatsApp connection.
From Settings → WhatsApp Connection, the administrator can start the Meta onboarding process and connect the appropriate WhatsApp assets to the FaceBot workspace.
FaceBot handles the connection workflow and then stores the linked account information required for the workspace.
Choose the right WhatsApp connection mode
WhatsApp Business App + API Coexistence
Coexistence is designed for businesses that already use WhatsApp Business on a phone and want to add FaceBot without giving up the existing mobile workflow.
With Coexistence:
- The business number can remain active in the WhatsApp Business App.
- FaceBot can use the API connection for supported campaigns, AI, and automation workflows.
- Your team can continue using the mobile app for human conversations.
- History and contact synchronization can be enabled during setup.
This makes Coexistence useful for businesses that want to add automation while preserving the WhatsApp workflow their team already uses.
WhatsApp Business Platform / API Only
API-only mode is designed for a WhatsApp number that will operate directly through the WhatsApp Business Platform rather than remaining active in the mobile WhatsApp Business App.
This is appropriate when the number is intended primarily for API-driven messaging and automation.
Coexistence history and contact synchronization
During a Coexistence connection, FaceBot can support synchronization of WhatsApp Business history and contacts when that option is selected.
FaceBot tracks the synchronization process so users can understand whether data transfer is still in progress or has completed.
Sync states can include:
- Pending
- Receiving
- Complete
- Failed
- Declined
The exact state reflects the result returned through the Meta connection workflow.
Display name approval and WhatsApp readiness
WhatsApp display name approval is one of the account signals shown inside WhatsApp Core.
FaceBot can display states such as:
- NOT_SET
- PENDING
- APPROVED
- REJECTED
This makes it easier for administrators to see whether the business identity associated with the WhatsApp number still requires attention before normal sending workflows can proceed.
Cloud API registration and the 6-digit PIN
For applicable API setups, WhatsApp phone registration is separate from the initial account connection.
FaceBot provides registration controls directly in WhatsApp Core so users can complete this process without leaving the FaceBot workflow.
Save & Register PIN
When phone registration is required, the administrator can enter the valid 6-digit Cloud API registration PIN and use FaceBot to submit the registration to Meta.
Change PIN
If the registration PIN needs to be updated, FaceBot allows the user to change the WhatsApp registration PIN and save the new value.
Check Now
After setup or registration changes, Check Now allows the administrator to request an immediate account-status refresh.
This is useful when waiting for Meta approval or after correcting a registration problem.
FaceBot gives clear registration guidance
If Meta does not accept the registration request immediately, FaceBot keeps the registration state visible rather than treating the setup as complete.
For example, if the PIN is rejected or registration is still processing, the interface can guide the user to retry with the current valid PIN or wait for the account state to update.
Coexistence and API-only setups are handled differently
FaceBot does not force every WhatsApp number through the same setup instructions.
Coexistence connections have different operational requirements from dedicated API-only numbers.
For Coexistence, FaceBot can track information such as:
- Mobile app and API connection state
- History/contact synchronization status
- Webhook reception status
- Coexistence-specific readiness behavior
This prevents users from being directed through API-only registration steps when those steps do not apply to their connection mode.
WhatsApp account health and live status checks
WhatsApp Core combines connection data and account checks into practical readiness indicators.
These checks can include:
- Display name approval
- Cloud API phone registration
- Whether registration is still required
- Current connection type
- Messaging capacity information
- Active campaign constraints
- Billing/account warnings
This means the connected state alone is not treated as the final signal for campaign readiness.
Campaign protection through readiness checks
FaceBot uses WhatsApp account readiness information when a user attempts to create or launch supported campaign activity.
If an important requirement is missing, FaceBot can prevent the campaign from proceeding and guide the user back to the relevant WhatsApp setup area.
This helps avoid preventable campaign failures caused by incomplete account configuration.
Understand WhatsApp messaging capacity
FaceBot can surface messaging-capacity information associated with the connected Meta WhatsApp setup.
This is particularly important for businesses using the WhatsApp Campaign Manager, where available Meta messaging capacity can affect how quickly a large recipient audience is processed.
Keeping capacity information visible makes WhatsApp Core part of the wider campaign-readiness workflow rather than just an onboarding screen.
WhatsApp billing stays with Meta
WhatsApp message charges and payment-method management remain inside your Meta account.
FaceBot does not replace Meta billing management. Instead, WhatsApp Core gives administrators visibility into the billing/account state that can affect sending.
Available actions include:
- Open Meta Billing: Go to the appropriate Meta billing area when payment information needs attention.
- Sync from Meta: Refresh the latest billing and account status inside FaceBot.
Billing statuses in FaceBot
WhatsApp Core can display billing-related states such as:
- Meta-managed
- Warning
- Blocked
- Sync error
- Unknown
- Disconnected
If Meta reports a payment-related restriction, FaceBot highlights that the billing issue needs to be resolved through Meta before normal sending can continue.
How to set up WhatsApp Core in FaceBot
- Open Settings: Go to Settings → WhatsApp Connection.
- Select your connection type: Choose WhatsApp Business App + API for Coexistence or WhatsApp Business Platform for API-only operation.
- Complete Meta Embedded Signup: Follow Meta's official connection flow and return to FaceBot.
- Review Account Details: Confirm the connected phone number, WABA information, and connection type.
- Review Display Name status: Submit or monitor the display name if approval is still required.
- Configure Coexistence sync: If using Coexistence, choose the applicable history/contact synchronization option and monitor its status.
- Register the phone when required: Enter the valid 6-digit registration PIN and use Save & Register PIN.
- Use Check Now: Refresh the account state after approval or registration changes.
- Review Meta billing: Check the billing status, use Sync from Meta, or open Meta Billing if action is required.
- Confirm readiness: Resolve any outstanding warnings before proceeding to WhatsApp campaigns or automated messaging.
Disconnect and connection maintenance
WhatsApp Core also includes connection-maintenance controls for situations where the account setup needs to be changed.
This can include disconnecting the WhatsApp connection and choosing the applicable chat-retention behavior during that process.
Because disconnecting can affect live messaging workflows, it should be treated as an administrative action rather than a routine troubleshooting step.
Example workflow: keep WhatsApp Business on mobile and add FaceBot
A business already uses its WhatsApp Business number on a sales team's mobile phone.
The team now wants to add FaceBot campaigns, AI communication, and lead workflows without abandoning the existing app.
- The administrator opens Settings → WhatsApp Connection.
- They choose WhatsApp Business App + API.
- Meta Embedded Signup is completed using the existing business number.
- History and contact synchronization is enabled.
- FaceBot shows the connected account information and Coexistence status.
- The administrator monitors the display name and readiness checks.
- Billing status is synchronized from Meta.
- Once the required conditions are ready, the team proceeds to WhatsApp campaign and AI workflows.
The same business number remains available to the sales team in the mobile WhatsApp Business App while FaceBot adds supported API capabilities around it.
Who should use WhatsApp Core?
Businesses connecting WhatsApp for the first time
WhatsApp Core provides a guided path from Meta Embedded Signup to account readiness.
Businesses moving to Coexistence
Teams can add FaceBot to an existing WhatsApp Business App number while keeping mobile access active.
Businesses running WhatsApp campaigns
Account status, registration, capacity, and billing visibility help teams confirm that the WhatsApp foundation is ready before sending.
Administrators managing WhatsApp health
WhatsApp Core centralizes the connection signals that administrators need to monitor after initial setup.
Best practices
- Choose the correct connection type: Use Coexistence when the team needs to keep using the WhatsApp Business App alongside FaceBot.
- Use Check Now after setup changes: Refresh live Meta status after changing registration or account settings.
- Keep the current valid PIN under administrator control: It may be needed if phone re-registration becomes necessary.
- Monitor display name approval: Resolve approval issues before depending on the number for production campaigns.
- Watch synchronization status: Coexistence history/contact sync may need time to complete.
- Review capacity before large campaigns: Messaging capacity can affect campaign processing.
- Sync billing status after payment changes: Refresh Meta status when billing details have been updated.
- Resolve warnings before launching campaigns: Fix readiness issues instead of waiting for a send to fail.
- Avoid unnecessary disconnects: Disconnect only when the WhatsApp connection genuinely needs to be removed or replaced.
Frequently asked questions
Can I keep using WhatsApp Business on my phone while using FaceBot?
Yes. Select WhatsApp Business App + API (Coexistence) so the existing business number can remain available in the WhatsApp Business App while also connecting to FaceBot.
Does FaceBot use Meta's official WhatsApp connection flow?
Yes. WhatsApp Core uses Meta Embedded Signup for the supported WhatsApp connection process.
What is the 6-digit registration PIN?
It is the Cloud API registration PIN used when Meta requires the WhatsApp phone number to be registered for API sending.
Can I change the WhatsApp registration PIN inside FaceBot?
Yes. FaceBot provides a Change PIN workflow for supported setups.
Why is my WhatsApp number connected but campaigns are still blocked?
A connected number may still have incomplete requirements such as display name approval, phone registration, messaging-capacity restrictions, active campaign constraints, or billing/account warnings.
Can FaceBot check the latest account status?
Yes. Use Check Now to refresh applicable registration and account-readiness information.
Does FaceBot charge Meta WhatsApp message fees?
No. WhatsApp message billing remains managed through your Meta account. FaceBot surfaces relevant billing status and provides access to Meta billing when action is required.
Can FaceBot tell me when Meta billing is blocking WhatsApp sending?
Yes. WhatsApp Core can show billing/account states such as warning or blocked when that status is reported through the connected Meta setup.
Can FaceBot sync my existing WhatsApp Business contacts and history?
Coexistence setup supports history and contact synchronization when the corresponding option is selected and Meta makes the data available through the connection process.
From WhatsApp connection to campaign readiness
FaceBot WhatsApp Core is designed to make WhatsApp setup easier to understand after the initial connection is complete.
It brings together connection mode, Coexistence, account identity, display name approval, phone registration, PIN management, synchronization, messaging capacity, and Meta billing visibility in one administrative workflow.
The result is a clearer path:
Connect → Verify → Check Account Health → Resolve Issues → Start Sending.