Back to all articlesWhatsApp onboarding

Set asset custody expectations when an agency handles WhatsApp setup

Alactic Editorial10 min read

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

An agency is ready to begin WhatsApp setup, but the client has not decided whose business account will contain the assets, who controls the phone number, or who will receive verification requests. Starting now turns those unanswered questions into setup decisions—often made by whoever happens to be available.

Before setup begins, approve a custody worksheet that names the client’s business approver, identifies the intended assets, records number control, assigns verification participation, and defines final acceptance. The agency can perform the work without becoming the only party able to explain or access the result.

The acceptance test is simple: a client representative should be able to identify the agreed business assets and number from their own authorised access, explain who controls the verification channels, and locate the approved custody record. An agency screenshot alone is not enough.

1. Separate setup work from custody decisions

In an agency-led onboarding project, “ownership” can mean several different things. Someone may mean the business named in the setup, the account where an asset sits, the person with access, or the organisation paying the agency. Those are not interchangeable.

For onboarding purposes, use custody to describe the agreed operating arrangement: where assets will sit, who can identify them, who controls relevant channels, and who approves decisions. This worksheet is not a determination of legal ownership.

Split the arrangement into five responsibilities:

  • Business approval: who authorises the intended business identity and asset arrangement.
  • Asset identification: who records the business account, WhatsApp Business Account, and number being configured, including identifiers where available.
  • Number control: who maintains the ability to use and manage the selected number and its relevant verification route.
  • Verification participation: who supplies requested business information or completes a verification action through an authorised channel.
  • Final acceptance: who checks that the completed setup matches the agreed arrangement.

The agency may prepare records and guide the process across all five areas. That does not remove the need for a named client decision-maker. A useful default is for the client to approve custody and retain control of its business channels, while the agency performs only the agreed setup work. Any different arrangement needs explicit approval before work starts.

2. Identify the intended assets before creating anything

Begin with an inventory, not an invitation to “set up whatever is needed.” Ask the client to identify any existing business account, WhatsApp Business Account, and intended phone number. Record what is known and mark anything uncertain as unresolved.

Names alone are weak identifiers. Two accounts can have similar labels, and a familiar display name does not establish that the agency is working in the intended location. Record the visible asset name alongside its identifier where available. For a new asset, write “not yet created” and specify who must confirm its identifier after creation.

For each proposed asset, distinguish three states:

  • Existing and confirmed: a client representative has checked it through authorised access.
  • Existing but unconfirmed: someone believes it exists, but the client has not verified the record.
  • Proposed: creation is approved in principle, subject to the stated custody arrangement.

This avoids a common failure: creating a replacement because nobody can immediately find the original. If an existing asset is suspected but cannot be identified, pause that part of onboarding and investigate. A fresh setup may appear faster while leaving two competing records and no clear client-approved destination.

Where account structures or setup options are unclear, inspect the actual environment and current provider guidance before approving the arrangement. Do not treat a proposed diagram as evidence that the platform supports it.

3. Use a completed custody worksheet, not a blank promise

Fictional worked example: Cedar Lane Supplies has hired Harbour Setup Agency for WhatsApp onboarding. Every name and reference below is hypothetical. The references are worksheet labels, not real platform identifiers. This is a recommended operating design, not a description of a product control.

Hypothetical completed custody worksheet

Scope: Initial WhatsApp onboarding only. No messaging launch is authorised by this worksheet.

Client business approver: Maya Patel, Operations Director at Cedar Lane Supplies.
Agency setup lead: Alex Reed, Harbour Setup Agency.
Client verification participant: Jonah Lee, Business Systems Coordinator.
Client backup: Maya Patel, subject to confirmation that she can use the relevant channel.
Record location: Client-controlled onboarding folder, document reference CUSTODY-01.

  1. Business approval — client accountable, agency prepares. Maya approves the business identity and intended asset location before configuration. Alex prepares the inventory and flags uncertainties. Approval recorded: proceed using the client’s confirmed business account; do not substitute an agency-controlled account without a new written decision.
  2. Asset identification — agency records, client confirms. Business account worksheet reference: CLIENT-BUSINESS-A. WhatsApp Business Account worksheet reference: CLIENT-WABA-A, proposed and not yet created. Alex must enter the actual visible names and identifiers in the client record after creation. Jonah must independently locate and confirm them before acceptance.
  3. Number control — client responsible. Selected number worksheet reference: CLIENT-NUMBER-A, the client’s designated business line. Jonah confirms that the client controls the relevant number service and can participate through the verification route presented during setup. The full number is retained in the restricted client record, not the general project discussion.
  4. Verification participation — client completes, agency guides. Jonah attends the agreed setup session and handles verification actions through the relevant authorised channel. Alex explains the pending step but does not request permanent custody of the client’s email, phone service, or recovery credentials. If Jonah cannot participate, work pauses unless the approved backup has confirmed access.
  5. Unexpected verification request — client decides. If the process asks for information or access not covered here, Alex records what is requested and stops the affected step. Maya decides who may supply it after the request has been checked. No substitute personal or agency channel is used merely to keep the session moving.
  6. Final acceptance — client accountable, agency supplies evidence. Alex supplies the completed asset inventory and a list of unresolved items. Jonah performs the identification test using his own authorised access. Maya accepts only when the identifiers match, number control is confirmed, and no custody exception remains unexplained.
  7. Change rule — joint record, client approval. Any change to the intended business account, WhatsApp Business Account, selected number, or verification participant requires an updated worksheet and Maya’s approval before the affected action proceeds.

Hypothetical approval entry: Maya approves the pre-setup arrangement. The WhatsApp Business Account identifier remains pending creation and must be confirmed before final acceptance. Alex acknowledges the stop conditions and responsibility to update the inventory.

The worksheet is deliberately specific about what remains unfinished. Pre-setup approval authorises a defined plan; it does not certify that assets already exist or that onboarding has succeeded.

4. Plan verification around the person who controls the channel

A client contact being available for a meeting is not the same as that person controlling the required channel. Before scheduling the setup session, ask the named participant to confirm which relevant business email, number, or other requested channel they can actually use. Check the route presented by the current setup process rather than assuming a particular verification method will be offered.

Keep the coordination record separate from sensitive verification material. The worksheet should say who participates and what happened, not become a store of passwords, one-time codes, recovery secrets, or unnecessary copies of business documents.

The agency should guide the client to complete sensitive actions through the relevant authorised interface wherever possible. If a step appears to require disclosure or handling beyond the agreed arrangement, pause and review it rather than improvising in a shared chat.

Record outcomes plainly: “client participant completed the requested action,” “request still pending,” or “channel unavailable.” Do not convert a scheduled session into a completed verification status. If the participant cannot use the required route, reschedule or resolve control first; agency convenience is not a custody decision.

5. Decide which exceptions are worth accepting

Client-controlled custody introduces coordination work. The agency may need to wait for an approver, and a setup session may stop because the right person is unavailable. Those delays are visible and can be planned. An unclear arrangement can be less visible until acceptance, when the client discovers it cannot identify the assets without the agency’s help.

An agency-controlled arrangement may also be proposed. Do not approve it with a vague assurance that the assets can be moved later. First establish whether the proposed future change is actually supported and what dependencies it would involve. If that cannot be confirmed, treat future transfer as unresolved—not as a promised remedy.

For any exception, record:

  • The specific asset or channel affected.
  • Why the default arrangement is not being used.
  • What the client will and will not be able to identify or control.
  • The client approver’s decision.
  • The condition that would trigger reconsideration.

A temporary arrangement still needs a defined end condition. “Until setup is done” is insufficient if nobody has defined completion. Tie the condition to an observable event, such as the client confirming the asset identifiers and the approved number-control arrangement.

6. Stop and recover when the record does not match reality

A custody mismatch should stop the affected setup action, not trigger a rushed workaround. Preserve the current record, establish what changed, and obtain a revised client decision before continuing.

The wrong business account is open

Do not create the next asset simply because the agency can proceed in that account. Compare the visible account identifier with the approved worksheet. If they differ, correct the working location or obtain a new approved arrangement. Record any actions already taken so the discrepancy is not hidden.

The number is controlled by an unavailable person

Mark number control as unresolved. Ask the client to establish an authorised participant or reconsider the selected number. Do not substitute an agency number without explicit approval and a review of the resulting custody implications.

A new asset was created before agreement

Inventory the asset and its current location. Tell the client what was created and which assumption drove the action. Review the available correction options before creating more assets or attempting changes. Do not promise that an asset can be transferred, removed, or recreated without checking the actual options and consequences.

The agency says setup is finished, but the client cannot find it

Keep acceptance pending. Check whether the issue is a mismatched identifier, the wrong account context, or an access problem. Resolve it within the approved arrangement, then repeat the client-led test. A successful agency demonstration does not prove client custody.

7. Make the client identify its own assets before acceptance

Run the acceptance test with the agency available to clarify, but not acting as the client’s substitute. The client representative should use their own authorised access and the approved worksheet.

  1. Find the intended business account. Read back its visible name and identifier and compare them with the record.
  2. Find the WhatsApp Business Account. Confirm that the recorded asset is the one used for this onboarding.
  3. Identify the selected number. Match it to the restricted record and explain who controls its relevant service and verification participation.
  4. Locate the custody worksheet. Show where the client keeps the approved arrangement and subsequent changes.
  5. Explain unresolved items. Distinguish completed setup actions from pending verification or other unfinished work.

Record each result as pass, fail, or not yet testable, with a short reason. The target is that every applicable item passes before final acceptance. Any item that cannot yet be tested remains open unless the client explicitly accepts that limited state and understands what has not been established.

This test establishes whether the agreed custody arrangement is observable. It does not establish permission to contact recipients, template approval, message delivery, or broader operational readiness.

8. Set one measurable gate for the next setup session

Before the next agency setup session, have the client approver sign off one worksheet covering all five responsibilities: business approval, asset identification, number control, verification participation, and final acceptance. Count unresolved custody decisions separately from routine setup tasks.

The pre-setup gate is no unresolved custody decisions for the actions about to be performed. New asset identifiers may remain pending creation, but their intended location and confirmation responsibility must already be agreed. At the end of setup, record how many applicable identification checks the client passed and name the person responsible for each remaining issue.

That gives both parties a clear basis for proceeding: the agency knows what it is authorised to configure, and the client can recognise the result without relying on the agency’s memory.

WhatsApp onboardingAsset custodyAgency handoverVerification

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