Browse topics
25 practical guides

Numbers & Meta connection

Connect a business number, understand signup states and recover safely when approval is interrupted.

A useful starting point

Match the business portfolio, WhatsApp account and phone number before authorising a connection. If completion is uncertain, inspect the saved state before starting another attempt.

01

Prepare for Meta embedded signup

Gather the correct access and number details before authorising the connection.

02

Choose the correct Meta business portfolio

Prevent a valid login from linking the wrong business assets.

03

Check access to the WhatsApp business account

Separate personal login access from permission to manage the relevant account.

04

Select the right number connection path

Choose the path that matches the number's current WhatsApp use.

05

Connect a new business number

Complete signup for a number the business controls and can verify.

06

Evaluate an existing Business App number

Understand the offered onboarding route without assuming every number is eligible.

07

Plan a provider migration

Coordinate the move with both the current arrangement and the destination workspace.

08

Verify a number through an OTP channel

Use the verification route presented by the provider and keep the code private.

09

Troubleshoot an unavailable verification code

Check reachability and the selected channel before requesting more codes.

10

Keep a long signup session open

Allow the provider flow to finish without treating a reminder as a confirmed failure.

11

Recover after closing the signup popup

Determine whether authorisation completed before starting another connection.

12

Handle a connection request timeout

Resolve uncertainty without repeatedly submitting the same authorisation.

13

Understand the JSSDK unknown host error

Recognise a platform login-domain configuration issue and report it accurately.

14

Recover from a blocked provider popup

Allow the expected login window without weakening unrelated browser protections.

15

Distinguish connected from ready to send

Read the connection and readiness states as separate checks.

16

Read number and account identifiers safely

Use provider identifiers to compare assets without treating them as public marketing content.

17

Refresh account readiness from Meta

Fetch current provider states before acting on an older screenshot.

18

Resolve access changes after onboarding

Recover when a business administrator's permissions have changed.

19

Connect a UK test number

Test reachability, ownership and workspace state for a UK number.

20

Avoid connecting a number to the wrong workspace

Check both the current Alactic account and the selected Meta asset.

21

Disconnect a number deliberately

Understand the effect of removing a connection before confirming the action.

22

Reconnect after an incomplete setup

Resume from the actual saved state rather than reconstructing it from memory.

23

Protect verification and login information

Keep account recovery and number verification within authorised channels.

24

Document a connection problem for support

Provide enough context to diagnose the failed stage without sending secrets.

25

Check the first conversation after connection

Verify the connected number through a small authorised inbound test.

Relevant public sources

Find your next step

Search by task, feature or question.

Browse the full directory →