WhatsApp, Meta, and phone channels
Connect WhatsApp Business and Meta messaging, and provision Spacebrain phone numbers without confusing the three resource models.
Spacebrain exposes several messaging channels, but they do not share one universal Meta or phone connection. Choose the resource model that matches the conversation you need to operate.
| Channel | Connection model | Primary result |
|---|---|---|
| WhatsApp Business Cloud API authorization through Meta | WhatsApp Business numbers and Inbox conversations | |
| Messenger and Instagram | Meta Lead Ads & Messaging authorization, then Facebook Page subscription | Page DMs, linked Instagram DMs, and optionally lead forms |
| SMS and voice | A phone number provisioned in Phone Numbers | Text and call activity for that workspace number |
These channels are separate
A Spacebrain phone number is not automatically a WhatsApp Business number. A Meta Lead Ads & Messaging connection does not connect WhatsApp. Connecting WhatsApp does not subscribe Facebook Pages or import Meta lead forms.
Provider eligibility, verified businesses and numbers, messaging limits, number inventory, country support, pricing, compliance requirements, plan access, and rollout can vary. The signed-in connection screen is authoritative for the current workspace.
Connect WhatsApp Business
The current WhatsApp screen uses the WhatsApp Business (Cloud API) flow through Meta.
Before connecting, confirm that the authorizing person can access the intended Meta business resources and WhatsApp Business Account. The eligible business, verification, number, template, and messaging-policy requirements are determined by Meta and can change independently of Spacebrain.
- Open Integrations → WhatsApp.
- Choose Connect WhatsApp.
- Complete the Meta authorization with the identity that owns or administers the intended WhatsApp Business Account.
- Return to Spacebrain and inspect the connection status.
- Confirm the displayed WhatsApp Business Account ID.
- Review the discovered phone numbers, their verified names, and the number marked Default.
- Send an allowed test message to the business number from a separate phone.
- Confirm that the message appears in the unified Inbox and that a reply from the thread reaches the tester.
If Spacebrain reports a connected account but shows No phone numbers found, authorization succeeded without exposing a usable number on that WhatsApp Business Account. Verify the selected Meta business, the number's status in Meta, and the authorizing user's access. Do not substitute a number purchased in Spacebrain unless it has separately gone through Meta's supported WhatsApp onboarding.
Connection states can include Connected, Expired, Error, and Disconnected. Reauthorize an expired or errored connection with the correct owner and retest both inbound and outbound paths. Before disconnecting, identify Inbox assignments, agents, automations, templates, and active customer conversations that rely on the WhatsApp channel.
Connect Meta Lead Ads & Messaging
The Meta integration uses one Facebook authorization to power supported Lead Ads, Messenger, and Instagram work. It remains separate from the WhatsApp connection.
Prerequisites
- A Facebook identity with administrator access to at least one intended Page.
- For lead capture, Page and form access appropriate to the provider's Lead Ads permissions.
- For Instagram DMs, an eligible Instagram account linked to the intended Facebook Page.
- An agreed CRM owner, field mapping, consent model, and follow-up process for imported leads.
If no Pages appear after authorization, the current screen directs you to confirm that the Facebook user has admin access to a Page. Reconnect with the right identity rather than subscribing an unrelated Page.
Authorize and subscribe a Page
- Open Integrations → Meta.
- Choose the Meta connection for Lead Ads & Messaging and complete Facebook authorization.
- Review every Page returned to Spacebrain.
- Inspect whether the Page has lead access, whether its webhook is subscribed, and whether a linked Instagram account is detected.
- Subscribe only the Pages that belong to the active workspace.
- Send a test Messenger DM and, when linked, an Instagram DM.
- Confirm that each arrives in the correct Inbox channel and that replies return to the correct provider thread.
Subscribing a Page enables delivery for supported Page lead forms and Messenger or Instagram DMs. A Page can be useful for DMs even when it does not have Lead Ads access; the current screen disables View Forms when lead access is unavailable. Treat messaging readiness and lead-form readiness as separate checks.
Configure lead forms
For each form you intend to synchronize:
- Open the Page and form in the Meta integration.
- Review the suggested field mapping rather than accepting it automatically.
- Map provider fields such as name, email, phone, company, and address to the correct Spacebrain CRM fields.
- Leave a field unmapped when its data should not be stored.
- Choose the synchronization policy:
- Sync all leads processes all eligible submissions.
- Only sync if email present excludes submissions without email.
- Manual sync only retains operator control over importing.
- Save the mapping and submit an internal test lead.
- Inspect the created CRM record, ownership, source context, and any automations it triggers.
- Use Backfill only after mapping and automation effects have been reviewed.
Imported leads can show states such as New, Processed, or Error, with campaign or ad context when available. A Page subscription does not guarantee that every historical form is automatically imported; backfill is an explicit, potentially high-volume action.
Meta connection states can include Active, Expired, Revoked, and Error. Reconnect with the intended Page administrator when permissions change. Disconnecting the Meta account stops the shared Lead Ads and supported Messenger/Instagram connection for the workspace, so assess all three surfaces first.
Provision a Spacebrain phone number
The Phone Numbers area provisions workspace number resources. It is not a generic “bring your own carrier” credential form in the current interface.
- Open Phone Numbers and choose to buy a number.
- Select a country and, when available, an area code or number type such as local or toll-free.
- Review the exact setup charge, monthly credit renewal, and total due now in the confirmation dialog.
- Complete any regulatory information requested for that country or number type.
- Purchase with the workspace credit balance.
- Assign the number to an AI agent or configure the intended incoming-call behavior.
- Run internal inbound call and text tests before publishing the number.
Inventory, country coverage, local and toll-free types, quoted cost, regulatory requirements, and messaging capability vary by provider and region. Pricing shown during search can be an estimate; review the final confirmation before purchase. The current purchase flow charges the setup amount and first month immediately, then renews monthly in credits.
An active number can be assigned or reassigned to an agent, configured for incoming calls, manually paused or resumed, and released. A number paused for insufficient credits can stop operating until the balance is restored. Release Number is presented as irreversible; remove it from campaigns, sites, forwarding rules, customer records, and compliance registrations before confirming.
A purchased number is not complete launch approval
Confirm the applicable messaging registration and compliance state in the Trust Center, plus consent, quiet hours, opt-out handling, recording rules, and regional requirements for the actual use case. Number ownership alone does not authorize unsolicited or high-volume messaging.
End-to-end channel test
For every enabled channel, use a test identity that is not the connected business identity and verify:
- A new inbound message creates or matches the expected contact.
- The correct workspace, channel, Page, or number is shown.
- Assignment and notifications reach the intended teammate or agent.
- One reply reaches the provider exactly once.
- Consent and opt-out behavior work as designed.
- Disconnecting or pausing the test channel prevents new sends without losing the audit context you need.
Do not retry customer-facing sends blindly after a timeout. Check the provider thread and Spacebrain conversation first; the original request may have succeeded even if the screen did not receive a final response.
Next step
Keep moving
Open the relevant Spacebrain module, ask for help, or tell us how to improve this guide.