Build a WhatsApp asset inventory before starting onboarding
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
One colleague says the business already has a WhatsApp account. Another has a login from a former agency. The intended phone number appears on the website, but nobody knows who manages its service. Starting setup at this point turns assumptions into decisions.
Before onboarding, create an asset register that identifies the business portfolio, WhatsApp business account, intended phone number, proposed display name and responsible business owner. For each entry, record what was observed, where the evidence lives, who supplied it and which questions remain open. Keep asset existence, identity and control as separate findings.
This WhatsApp business onboarding asset checklist is a discovery exercise—not an instruction to create accounts, change permissions or move a number. Its purpose is to make the next setup decision defensible: reuse an identified asset, investigate an uncertain one, or consider a new asset only after checking for an existing setup.
1. Define the decision the inventory must support
Begin with a short statement of intended use. For example: which business entity needs the setup, which customer-facing brand it represents and which phone number the team intends to use. Without that boundary, people may supply perfectly valid evidence for the wrong business unit.
Ask the team to answer a concrete question: Which existing assets, if any, are candidates for this onboarding? Do not ask only whether the company “has WhatsApp.” That wording can refer to a phone app, an account used by another department or a setup managed through a service provider.
Make the inventory broad enough to capture plausible candidates, but narrow enough to investigate. If two portfolios appear relevant, record both. If an unrelated regional account turns up, retain a brief exclusion note rather than expanding the entire project around it.
The output should support a decision, not force one. “Candidate identified; control unresolved” is more useful than an unsupported “ready.” Equally, “not found in the evidence reviewed” is more accurate than “does not exist.”
2. Use evidence states instead of a single complete checkbox
A single complete checkbox hides important differences. An account may visibly exist while its relationship to the intended business remains unclear. A staff member may be able to view it without being the person responsible for authorising its use.
Use a small set of evidence states consistently:
- Confirmed: Direct, dated evidence supports the specific claim being recorded.
- Reported: A named person has supplied the information, but the underlying evidence has not been checked.
- Unresolved: Evidence is missing, conflicting or insufficient for the decision.
- Proposed: The team has selected an intended value, but it is not being presented as an existing or approved asset.
- Excluded: The candidate was investigated and is outside this onboarding scope; record why.
Apply a state to a claim, not just to an entire row. For example, an account's identity can be confirmed while its operational owner remains unresolved. Record “account identifier observed” separately from “business control confirmed.”
For each claim, capture the evidence date and its limitations. A historical screenshot can establish what was visible at the time; it does not establish current access. A verbal assurance can identify a useful contact; it should not silently become proof of control.
3. Gather identifiers without collecting credentials
Start with the business sponsor and people who currently operate customer communications. Ask them for existing records, the names of relevant administrators and any agency or provider contacts involved in the setup. Request a limited, authorised review of the relevant account details rather than broad access simply for discovery.
Capture the following distinctions:
- Business portfolio: Its displayed name and identifier, the business it is believed to represent, and the evidence linking it to this project.
- WhatsApp business account: Its name and identifier, plus evidence of its association with the candidate portfolio. Do not infer that association from matching names alone.
- Intended phone number: The full number in a consistent format, its reported current use and the person or team responsible for the underlying number service.
- Proposed display name: The exact intended spelling, its internal business approver and whether it is merely proposed or has an evidenced existing status.
- Responsible business owner: The person accountable for the business decision, distinct from a technical administrator or external operator.
Record separately who can currently see the assets, who manages the number service and who can authorise the business decision. These may be different people.
Keep passwords, verification codes, recovery secrets and access tokens out of the register. Evidence links should point to appropriately restricted business records. If a capture contains unrelated information, retain only what is necessary to substantiate the claim.
4. A hypothetical completed asset register
Fictional worked example: Every business name, person, identifier, evidence reference and date below is hypothetical. The register is completed as a discovery artifact even though several findings remain unresolved. The identifier placeholders are not real platform IDs.
Scope: Cedar Lane Office Supplies wants to identify existing assets for its customer-service onboarding. Review date: 14 April 2026. Register custodian: Priya Shah, operations coordinator. Evidence root: the restricted internal folder “Customer communications / Asset discovery / April review.”
Business portfolio
- Recorded value: Cedar Lane Trading; identifier placeholder
PORTFOLIO-EXAMPLE-A. - Evidence state: Identity confirmed; suitability for this business unit unresolved.
- Evidence location: Evidence record E01, dated account-detail capture from an authorised review with Morgan Lee, internal administrator.
- What the evidence establishes: Morgan could view a portfolio with that name and identifier on the review date.
- Control finding: Morgan reports administering it for the parent company. The sponsor has not yet confirmed that it is the intended portfolio for this onboarding.
- Open question and owner: Elena Ruiz, business sponsor, to confirm whether this portfolio represents the intended operating business.
WhatsApp business account
- Recorded value: Cedar Lane Service; identifier placeholder
WABA-EXAMPLE-B. - Evidence state: Identity and association with the candidate portfolio confirmed; current operational responsibility unresolved.
- Evidence location: E02, dated account-detail capture showing the account identifier and portfolio association.
- What the evidence establishes: This is a distinct account associated with the portfolio recorded in E01, rather than merely a similarly named account.
- Control finding: Morgan can view its details. An older handover note names a former agency as an operator; that note does not establish current access.
- Open question and owner: Priya to obtain a current responsibility statement from Morgan and the former agency contact, without requesting permission changes.
Intended phone number
- Recorded value: Full number stored in restricted evidence record E03; masked register reference
NUMBER-EXAMPLE-C, ending 0148. - Evidence state: Intended number confirmed by the sponsor; current account association unresolved; number-service responsibility reported.
- Evidence location: E03, sponsor's intended-number record; E04, existing service inventory supplied by the facilities team.
- What the evidence establishes: The sponsor has selected this number. E04 lists facilities as the internal service contact but has not been reconfirmed.
- Control finding: Neither the website listing nor the service inventory proves who currently controls the number service or which WhatsApp setup uses it.
- Open question and owner: Facilities lead Sam Okafor to confirm current service responsibility; Morgan to establish whether the number is associated with the candidate account or another setup.
Proposed display name
- Recorded value: Cedar Lane Support.
- Evidence state: Proposed; internally selected, not represented as externally approved.
- Evidence location: E05, dated brand-owner decision note with exact spelling.
- What the evidence establishes: The business wants this name. It does not establish any platform review outcome.
- Open question and owner: Elena to resolve the difference between the proposed name and the existing account label before setup decisions are finalised.
Responsible business owner
- Recorded value: Elena Ruiz, customer operations director; Priya Shah maintains the register.
- Evidence state: Business responsibility confirmed; technical asset control remains separately recorded above.
- Evidence location: E06, internal project responsibility note acknowledged by Elena.
- What the evidence establishes: Elena owns the intended-use and reuse decisions. It does not establish that she has account access.
- Open question: None for business accountability; technical-control questions remain assigned to the relevant contacts.
Discovery decision: Retain the existing portfolio and account as reuse candidates. Pause setup decisions involving the intended number until its existing association and service responsibility are established. Do not create replacement assets simply because the investigation is incomplete.
5. Resolve the unknowns that could change setup
Not every blank field deserves the same urgency. Prioritise questions whose answers could change which asset is used, who must participate or whether the proposed setup would duplicate an existing one.
For this recommended workflow, treat these as decision blockers:
- The candidate portfolio cannot be distinguished from another similarly named portfolio.
- The relationship between the candidate account and portfolio has not been evidenced.
- The intended number's current use or account association is unknown.
- No responsible business owner will confirm the intended use.
- Evidence about control conflicts, or depends solely on an unconfirmed historical contact.
Other uncertainties may allow discovery to continue without authorising setup. For example, a proposed display name can remain clearly marked as proposed while the team confirms account identity. That does not imply the name will be accepted or that later checks are unnecessary.
Give each blocker a named investigator, a requested evidence item and a review date. “Check with IT” is not a resolution plan. “Sam to confirm the current number-service contact and attach the current internal service record” is actionable.
6. Avoid the shortcuts that create duplicate assets
Matching names instead of identifiers. Two entries with the same brand name may be different assets. Recover by capturing identifiers and evidence of the relevant relationships. Preserve both candidates until the ambiguity is resolved.
Treating a public number as proof of control. A website shows what the business publishes, not who manages the underlying service. Recover by identifying the current service custodian and checking the number's existing setup separately.
Assuming an agency-owned process means an agency-owned asset. A provider's involvement does not, by itself, answer which business asset is in use or who controls it. Ask for evidence of the specific account and current responsibilities rather than drawing conclusions from invoices or old email threads.
Creating a fresh account to bypass uncertainty. This may make the immediate task look simpler while leaving the intended number or business identity unresolved. Recover by pausing the creation decision, recording the missing evidence and escalating it to the business owner. Investigation is slower than guessing, but it preserves the option to reuse the right setup.
Over-collecting evidence. A large folder of unlabelled screenshots is hard to audit and may expose unnecessary information. Prefer a small evidence index in which each record supports a named claim. This requires more careful annotation but makes contradictions easier to spot.
7. End discovery with a measurable handoff
Hand off the register with one of three explicit outcomes: reuse candidate identified, further investigation required, or no existing candidate found within the documented search scope. None of these is a promise of onboarding eligibility or successful setup.
The handoff should state who and what was checked, when the evidence was reviewed, which candidates were excluded and which findings remain reported rather than confirmed. A new setup proposal should include that search scope so “we found nothing” cannot be mistaken for proof that nothing exists.
Your next action is to open one register and complete the five asset entries above. Measure readiness by evidence coverage, not by how many boxes contain text: every confirmed claim needs a retrievable reference; every unresolved setup blocker needs an owner, a requested evidence item and a review date.
Once those conditions are met, the onboarding team has a usable starting point: an identified candidate set, a clear account of what is known, and a bounded list of questions to resolve before making changes.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications