Back to all articlesWhatsApp onboarding

Choose the right business portfolio for WhatsApp onboarding

Alactic Editorial9 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

The team is preparing WhatsApp onboarding, and several business portfolios appear plausible. One carries the current company name, another belongs to an old project, and a third is managed by the agency supporting the launch. The operator suggests choosing whichever one they can already access.

Access makes a portfolio available to inspect; it does not establish that it is appropriate for this business. Before committing, compare the candidates against the same evidence requirements and record either a justified selection or a stop decision.

This guide covers that pre-onboarding decision. It does not prescribe asset transfers, corporate ownership changes or exact platform navigation. The output is a short evidence pack and an authorised selection record, not a promise that the selected portfolio will satisfy every subsequent onboarding requirement.

1. Define the business and the decision boundary

Start with the operating business responsible for the intended customer conversations. Record its current company identity, customer-facing brand, proposed messaging purpose and internal business sponsor. Without this reference point, reviewers may compare portfolio names without agreeing on what the selected portfolio needs to support.

A display name is useful for recognition but is not a reliable decision key. A historical name may have a legitimate connection to the current business; a matching brand name may refer to an abandoned project. Establish the relationship using current business records and confirmation from someone accountable for the intended use.

Separate three responsibilities: the business sponsor confirms the intended use, the administrator explains the candidate and relevant access arrangements, and the onboarding operator performs the authorised next step. One person may hold multiple roles, but each responsibility should remain explicit.

Define the boundary of the review as well. The team is deciding which existing candidate, if any, has enough supporting evidence to proceed. It is not deciding how to reorganise assets or settle disputed ownership. Questions requiring those decisions belong in a separate authorised review.

2. Build an evidence sheet for each candidate

Apply the same evidence categories to every plausible portfolio. Otherwise, a familiar candidate tends to receive assumptions in its favour while an unfamiliar one receives closer scrutiny.

  • Identity: What connects this portfolio to the operating business? Record the evidence and who confirmed its relevance.
  • Relevant assets: Which WhatsApp-related accounts, phone numbers or other relevant assets are known? Separate checked information from historical notes and unresolved entries.
  • Responsibility and authority: Who can substantiate the intended use, authorise the next step and maintain administrative continuity?
  • Operator access: What access has actually been checked? Do not substitute a job title or recollection of past access for a current finding.
  • Correction dependencies: What must be resolved before selection, who will resolve it, and what evidence will show completion?

For each entry, include a review date and an evidence reference, such as an internal record title or a recorded administrator confirmation. Keep sensitive supporting material in an appropriate restricted location rather than copying it into every handoff.

Record the actual portfolio identifier available in the reviewed record, alongside its display name. An internal shorthand such as CAND-A is useful only if it links unambiguously to that identifier. Identifying the portfolio and establishing authority to use it are separate checks: neither an identifier nor a screenshot of access settles the authority question.

Use explicit findings such as confirmed, unknown or conflicting. A blank asset field could mean that no relevant assets were found, that the reviewer lacked visibility, or that nobody checked. Those are different findings and should lead to different follow-up work.

3. Work through three candidates using the same criteria

Fictional worked example: All organisations, people, identifiers, dates and findings in this example are hypothetical. The identifiers are illustrative values, not a statement about any platform's identifier format. This is a recommended decision method, not an Alactic customer result.

Cedar & Loom Trading operates the Cedar & Loom customer brand. Its service team plans to onboard WhatsApp for customer-service conversations. Maya is the business sponsor, Arun is the onboarding operator and primary administrative contact, and Leena is the backup administrative contact.

On the hypothetical review date of 14 April 2026, Arun records three candidates. The table is the comparison summary; its evidence references point to the supporting findings described below.

CriterionActive companyObsolete projectAgency-controlled
Display nameCedar & Loom TradingCedar Launch StudioLantern Agency
Internal referenceCAND-ACAND-BCAND-C
Recorded portfolio identifier482731905661509284377931460285
Business connectionCurrent relationship confirmedHistorical project relationship onlyAgency identity; intended arrangement unresolved
Relevant assetsReviewed inventory recordedOld entry requires investigationProposed arrangement not documented
ResponsibilitySponsor and administrative contacts confirmedNo current sponsor confirmedAgency lead identified; client continuity unresolved
Remaining workInternal contact-record cleanupInvestigate current responsibility and assetsResolve operating arrangement separately
Review outcomePreferred, subject to closureDo not select nowDo not select now

Active company: bounded remaining work

Evidence entry A1 records the current company record, internal brand register and Maya's confirmation connecting the operating business to the proposed conversations. Entry A2 contains Arun's reviewed inventory of relevant assets, checked with the service lead. An unrelated archived campaign asset is listed separately rather than treated as part of this onboarding.

Entry A3 records checked access for Arun and Leena and identifies their administrative responsibilities. The internal contact register still names a former backup contact, so Leena must correct that record. The review found no unresolved identity or intended-use dependency; the remaining issue is a known documentation discrepancy.

Obsolete project: an unanswered investigation

Evidence entry B1 explains the historical project name but contains no current sponsor confirmation. Entry B2 identifies an old WhatsApp-related entry in project notes; its current purpose and relationship to the planned onboarding remain unknown.

A former project contact is recognisable to the team, but current administrative responsibility has not been established. This candidate cannot be treated as a simple cleanup task: investigation could reveal either a suitable arrangement or reasons not to use it.

Agency-controlled: a separate operating decision

Evidence entry C1 confirms the agency relationship. However, no approved operating arrangement explains why the agency portfolio should support this client's setup, how ongoing client access would work, or who would maintain continuity after the engagement.

The agency lead is a useful contact, but that does not answer the client's responsibility questions. This candidate is not rejected because agency involvement is inherently unsuitable. It remains unselected because the proposed arrangement needs a separate decision before the team can evaluate it properly.

4. Classify correction effort before choosing

The comparison now produces a defensible preference: Candidate A has a substantiated business connection, reviewed relevant assets and a bounded documentation correction. Candidates B and C require new evidence that could change the selection itself.

Use three work categories rather than labelling every obstacle a quick fix:

  • Record cleanup: A known discrepancy with an agreed correction and completion check. In the example, Leena updates the internal backup-contact entry and records where the corrected version can be found.
  • Investigation: An unanswered factual question. For Candidate B, the investigator must establish current administrative responsibility and the old asset's purpose before proposing a decision.
  • Structural question: An unresolved operating arrangement requiring separate authorisation. For Candidate C, the client sponsor and agency lead must clarify responsibilities and continuity expectations.

Do not assign a confident time estimate to an investigation merely because the first enquiry looks small. Finding an old contact is not the same as establishing present responsibility. Likewise, documenting a structural question does not authorise a transfer or ownership change.

A large existing asset inventory does not automatically make a portfolio preferable. It can provide useful continuity when well understood, or increase uncertainty when its purpose is unclear. Compare relevance and unresolved dependencies, not asset count.

5. Complete one decision and handoff record

Consolidate the decision, stop conditions and handoff acceptance criteria into one record. That prevents a summary table marked preferred from being mistaken for permission to begin.

Stop the selection if the operating business is unclear, the candidate's relationship to it is unsupported, relevant assets have unexplained or conflicting intended uses, authority to proceed is unresolved, or administrative continuity depends on an unconfirmed arrangement. These are recommended operational gates, not claims about platform eligibility rules.

The following completed artifact carries the actual example identifier through to the final handoff. Reuse its field labels for another review, replacing every fictional value with checked evidence.

FieldHypothetical completed entry
Operating business and purposeCedar & Loom Trading; customer-service conversations for the Cedar & Loom brand.
Selected portfolioCedar & Loom Trading; recorded portfolio identifier 4827319056; internal reference CAND-A.
Review evidenceA1: company and brand connection; A2: reviewed relevant-asset inventory; A3: checked administrative contacts and access. Reviewed 14 April 2026.
Selection reasonCurrent business connection established, relevant assets understood and internal administrative responsibilities confirmed.
Condition before proceedingLeena must replace the outdated backup-contact entry in the internal register and attach the corrected-record reference.
Business authorisationMaya authorises proceeding only after reviewing the recorded correction. Status at review: pending.
Operator and identity checkArun performs the next authorised onboarding step using identifier 4827319056, checking it against the selection record rather than relying on the display name.
AlternativesCAND-B, identifier 6150928437: unselected pending investigation. CAND-C, identifier 7931460285: unselected pending an approved operating arrangement.
Handoff statusNot ready. Becomes ready when the correction reference and Maya's authorisation are recorded.
Review checkpointBefore the next onboarding session; Arun checks the record remains current.

This record supports a clear acceptance test: another operator can identify the same portfolio, locate the evidence, see whether the condition is closed and determine who authorised proceeding. Until those fields are complete, the outcome is a conditional preference, not an executable instruction.

If no candidate qualifies, use the same structure for a stop record. Enter no portfolio selected, the blocking question, the required evidence, the responsible investigator and the next review checkpoint. Preserve rejected candidates and their reasons so the next reviewer does not repeat the comparison from memory.

6. Replace informal choices before committing

If someone has already suggested a portfolio but has not committed a setup action, pause and complete the comparison. Treat the suggestion as a candidate, not a decision that must be defended. Obtain authorisation through the completed record before continuing.

If onboarding has already begun, ask an authorised administrator to establish the current state and consult current official guidance or an authorised support route before further changes. Do not improvise transfers, ownership changes or repeated setup attempts as part of this selection review.

In the fictional example, the next action is narrowly defined: Leena corrects the register, Maya records authorisation and Arun checks identifier 4827319056 at handoff. If any of those checks fails, the record remains not ready. That observable boundary is the practical outcome of the review: a specific portfolio selected for documented reasons, or a specific unanswered question preventing commitment.

WhatsApp onboardingBusiness portfoliosOperational readiness

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