01What this guide helps you do
Separate account, messaging and operational readiness into verifiable checks.
This guide focuses on one task within getting started. Its completion test is specific: Every critical dependency has a named owner and a result. 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 create a launch readiness checklist. Keep the scope limited to the relevant launch checklist. 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 owner. 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
Start with a real business task, such as answering an enquiry or preparing a small campaign. Identify the business owner, the person handling conversations and the person with Meta administration access. They can be different people. Complete account and number checks before evaluating a live message. A demonstration workspace is useful for learning navigation, but it cannot establish readiness for a different production account.
Account access, number status, team owner.
04Find the right workspace and feature
Start from Overview and Settings. 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 launch checklist. 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 |
|---|---|---|
| Workspace | The business account currently open | Compare the name before acting |
| Edition | India or UK journey | Check currency and regional context |
| Owner | Person accountable for the task | Make the next action explicit |
| Readiness | Current state of the relevant feature | Verify in the feature itself |
Apply these distinctions to the specific inputs for this guide: account access, number status, team owner. 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
Read the workspace name and edition before making changes. Then inspect the specific feature involved in this guide. Keep three questions separate: can you open the feature, has its configuration been saved, and can its live operation run? A successful sign-in answers only the first access question. This distinction helps a new team avoid declaring onboarding complete while number authorisation or operational ownership is still unresolved.
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: List the required states
Begin with the relevant inputs: account access, number status, team owner. 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: Assign an owner to each check
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: Record the evidence before launch
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 launch sheet has separate rows for number connection and template availability.
The useful lesson is the sequence of decisions, not a promised result for every business. In this scenario, begin with “List the required states”, continue with “Assign an owner to each check”, and finish with “Record the evidence before launch”. 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
Use a controlled example whose expected result you can describe in advance. Check the record in the relevant feature rather than relying only on a success toast. If another teammate will use the workflow, have them locate the same record using their own account. This checks both shared understanding and the intended workspace context without sending messages to a broad customer audience.
Every critical dependency has a named owner and a result.
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 launch checklist and the relevant status. | Calling the task complete without evidence. |
| The result conflicts with the intended choice. | Revisit: Assign an owner to each check. | 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
A green connection badge alone does not prove campaign readiness.
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 launch checklist. 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
Return to the earliest incomplete stage rather than repeating the entire onboarding journey. An access issue belongs with account membership; a number issue belongs with Settings and Meta authorisation; a message issue belongs with the relevant conversation or campaign. Record the stage and exact error so the responsible person can act. Preserve completed work unless there is evidence that it is incorrect.
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
On mobile, the same business task may be reached from a workspace menu instead of the desktop navigation bar. Use the feature name and workspace identity as your reference. Recheck previews and confirmation details after the keyboard closes. If you move between devices, reopen the saved record so that the second device is working from current data rather than an older screen.
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 launch checklist, 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 | Separate account, messaging and operational readiness into verifiable checks. |
| Inputs reviewed | Account access, number status, team owner |
| Outcome to verify | Every critical dependency has a named owner and a result. |
| Next owner | Workspace owner |
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 account access, number status, team owner. 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
A demo is a learning workspace. A successful preview is not evidence that a live number, payment or message is ready.
Launch in small, observable stages: account access, number connection, team ownership, a controlled conversation and then a wider rollout.
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
A useful launch checklist changes when the business changes. Review it when adding a new operator, changing the connected number or introducing a new campaign purpose. Keep the checklist focused on observable outcomes: who owns replies, where the current policy lives, and how a failed test is escalated. Do not turn a one-time successful demo into a permanent claim that every future workflow is ready.
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 account access, number status, team owner. Then confirm the workspace and the relevant launch checklist. The first action is “List the required states”. 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: Every critical dependency has a named owner and a result. 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: A green connection badge alone does not prove campaign readiness. Keep the exact symptom, the relevant reference and the last completed action. Ask the workspace owner 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 launch checklist were identified.
- The necessary inputs were reviewed: account access, number status, team owner.
- List the required states.
- Assign an owner to each check.
- Record the evidence before launch.
- The result was checked: Every critical dependency has a named owner and a result.
- The task-specific risk was considered: A green connection badge alone does not prove campaign readiness.
- Any unresolved issue has an accountable next owner and a useful evidence reference.