01What this guide helps you do
Gather the correct access and number details before authorising the connection.
This guide focuses on one task within numbers & meta connection. Its completion test is specific: The selected assets belong to the intended business. Use that result to decide whether the task is finished. Opening a page, entering a value or seeing a brief notification can be part of the process without establishing the complete result.
02When to use this workflow
Use this workflow when your immediate goal is to prepare for Meta embedded signup. Keep the scope limited to the relevant connection record. If you are solving a different problem, use the related guides at the end rather than applying every action here to unrelated records.
The usual operational owner is the workspace administrator with access to the relevant Meta business. If another person owns the relevant business facts or permissions, involve that person before changing the shared record. Individual access and business authority are not always the same thing.
03Prepare the information you need
Have an authorised Meta business administrator available and confirm access to the intended number. Know which business portfolio and WhatsApp account should own the connection. Do not use an unfamiliar asset simply because it appears in a selector. Keep the Alactic setup page and provider popup open through completion. Verification, asset selection and the final workspace result are distinct parts of the same journey.
Business administrator, intended number, workspace.
04Find the right workspace and feature
Start from Settings → WhatsApp. Treat this as a feature locator: the arrangement of menus can differ between the web interface and the native application. Confirm the workspace name and the relevant record before proceeding, especially if you manage more than one business or use both India and UK accounts.
The target of this task is a connection record. Keep its identity visible while you work. A similarly named record or a previously open browser tab can otherwise make a correct action affect the wrong context.
05Understand the information on screen
| Information | What it means | Practical check |
|---|---|---|
| Business portfolio | Provider business context | Select the intended business |
| WhatsApp account | Provider account containing the number | Check access and ownership |
| Phone number | Customer-facing sending identity | Compare the complete number |
| Readiness states | Separate provider assessments | Read each label independently |
Apply these distinctions to the specific inputs for this guide: business administrator, intended number, workspace. You do not need to collect every possible field in the workspace. Use the information needed to make this decision and to verify its result.
06Inspect the current state first
Compare the displayed business, number and connection state with the intended setup. A connected label, business verification status, messaging availability and display-name review describe different things. Record the particular state that matters to the task. If the provider window reports completion but the workspace does not, treat the result as unresolved until the saved connection state can be inspected.
If the intended result is already present, check whether any further action is necessary. This is particularly useful after an interrupted session or when another teammate may have completed part of the work.
07Step 1: Open the real workspace
Begin with the relevant inputs: business administrator, intended number, workspace. Resolve any ambiguity that would change which record or business decision the task concerns. Keep a short note of the original state if you will need to compare it later. This creates a clear starting point for the next action instead of relying on memory after several screens have changed.
08Step 2: Check Meta business access
Use the result of the first action as the context for this one. Check the exact label, selected value or evidence involved rather than assuming that a default matches the intended task. If you identify an inconsistency, resolve it before proceeding. Keep the change narrow enough that its effect can be understood without comparing many unrelated edits.
09Step 3: Start the connection flow once
Finish by checking the observable result, not only whether the interface accepted an interaction. If the result is still pending or cannot be verified, preserve that distinction in your notes. A clearly recorded unresolved state is more useful than announcing completion and discovering the missing part during a live customer task. Use the verification guidance below for the relevant feature.
10Worked example
The owner writes down the business name before entering the provider popup.
The useful lesson is the sequence of decisions, not a promised result for every business. In this scenario, begin with “Open the real workspace”, continue with “Check Meta business access”, and finish with “Start the connection flow once”. Compare the result with the completion test before applying the same process to a wider set of records.
Use invented names and references when practising this example. Keep the structure realistic, but do not copy a live customer conversation or payment record into training material simply to make the demonstration look authentic.
11Verify the result
After the provider flow returns, inspect Settings and confirm the actual number associated with the workspace. Read any readiness information and distinguish it from the connection itself. A controlled message test is useful only after the account is ready and the test recipient is appropriate. Keep the number identity check separate from the test result so a successful message from the wrong business is not mistaken for success.
The selected assets belong to the intended business.
12Decide what to do next
| What you observe | Appropriate next step | What to avoid |
|---|---|---|
| The expected result is visibly present. | Keep the result and continue with the intended business task. | Repeating a completed action without a reason. |
| The result is still pending or uncertain. | Review the current connection record and the relevant status. | Calling the task complete without evidence. |
| The result conflicts with the intended choice. | Revisit: Check Meta business access. | Changing unrelated records to hide the symptom. |
Use the observed state to choose a branch. A recovery action should address the actual cause and preserve any work that is already correct. If several people are involved, make the next owner explicit so a pending state does not become an unattended task.
13The main mistake to avoid
An employee's unrelated business portfolio can be selected accidentally.
This mistake can make the task appear finished while leaving the business outcome unresolved. Return to the inputs and the named steps when the result is unclear. Keep a useful distinction between what you observed and what you expected. If a weaker signal is all that is available, describe the remaining uncertainty and identify how it can be checked.
14Diagnose an unexpected result
Compare the expected result with the exact current state of the connection record. Record which of the three actions was last completed and what happened next. Keep the exact validation message or visible status where one exists. This separates an input problem from a saved-state problem and helps another person reproduce the same example.
Check the workspace, selected record and current view. Change one relevant factor at a time. If you change several unrelated settings together, a later success may not explain which change actually resolved the issue.
15Recover without duplicating work
If a signup window closes or a request times out, inspect the existing state before creating another attempt. Repeated partial flows can make it harder to understand which authorisation completed. Capture the time, application address and visible error. An application host-domain error belongs to the platform's Meta configuration; missing access to a business asset belongs to the relevant Meta business administrator.
If the result depends on a provider or another authorised person, record that dependency and use the appropriate route. Do not simulate success by manually changing an unrelated display value or by removing evidence of the original outcome.
16Use the workflow on web and mobile
Provider authorisation can involve a separate browser window or session. On a small screen, keep track of both the provider flow and the originating workspace. Allow the normal popup journey where required and return to Settings after completion. If the application view appears unchanged, refresh the connection status and verify the account context before assuming the number needs to be registered again.
When comparing devices, match the same account, record and relevant filters. A desktop screenshot and a mobile screen from different contexts are not evidence of inconsistent data. If a layout problem prevents completing the task, report the screen name, device context and the affected control with private details removed.
17Keep a useful operational record
Retain only the information needed to explain the task: its purpose, the relevant connection record, the action taken and the observed result. If the operation produced a safe reference, keep it with the time and workspace context. This makes a later handover or support query more precise than a screenshot with no explanation.
| Record | Useful content |
|---|---|
| Purpose | Gather the correct access and number details before authorising the connection. |
| Inputs reviewed | Business administrator, intended number, workspace |
| Outcome to verify | The selected assets belong to the intended business. |
| Next owner | Workspace administrator with access to the relevant meta business |
18Protect private information
Use the minimum customer or business information needed for the task. Restrict access to authorised colleagues, and redact unrelated names, numbers and message content when sharing a screenshot. An evidence reference is often more suitable than copying the underlying private document into a general field or support message.
For this workflow, the useful input categories are business administrator, intended number, workspace. They should help you make and verify the decision; they are not a reason to publish a customer database, credentials or internal operating notes. The fictional example in this guide can be used for training without exposing live records.
19Know the limits of this workflow
Alactic cannot create ownership of a number or bypass a Meta verification decision. A completed provider popup must still be confirmed in the workspace.
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.
Read the linked source material for decisions controlled by a provider or by the applicable commercial terms. A practical guide explains how to approach the task; it does not add a new contractual guarantee or establish that every business use is legally suitable. Use the responsible business owner for unresolved exceptions.
20Review the process over time
Review number ownership and administrator availability when staff roles change. Keep an authorised person able to manage the Meta business assets. Do not publish account credentials or provider tokens in an internal handover that may later be shared externally. Document the user-visible recovery route and the responsible owner instead. A connection that worked previously may still require attention after an access or account change.
Update related instructions when the underlying business fact or product behaviour changes. Keep a representative example from this workflow so a future revision can be compared with an explicit expectation rather than judged from memory.
21Practical questions
What should I check before starting?
Prepare business administrator, intended number, workspace. Then confirm the workspace and the relevant connection record. The first action is “Open the real workspace”. Starting there keeps later decisions grounded in the correct record and avoids trying to solve a different problem with this workflow.
How do I know the task is complete?
Use this observable test: The selected assets belong to the intended business. If a state is pending, describe it as pending. If a save or provider operation is uncertain, inspect the current record before repeating it. The result matters more than whether a button was pressed.
What if the result still does not match?
Review this risk first: An employee's unrelated business portfolio can be selected accidentally. Keep the exact symptom, the relevant reference and the last completed action. Ask the workspace administrator with access to the relevant Meta business or the appropriate support route to review the remaining issue, using a small reproducible example rather than a broad export of customer data.
22Completion checklist
Use this checklist as a final review of the task, not as a substitute for the steps above. If an item remains unresolved, identify the next action and its owner. Do not mark a provider-dependent or unverified result complete merely because the rest of the checklist is finished.
- The intended workspace and connection record were identified.
- The necessary inputs were reviewed: business administrator, intended number, workspace.
- Open the real workspace.
- Check Meta business access.
- Start the connection flow once.
- The result was checked: The selected assets belong to the intended business.
- The task-specific risk was considered: An employee's unrelated business portfolio can be selected accidentally.
- Any unresolved issue has an accountable next owner and a useful evidence reference.