Customers recognize your number and its SIM is in your office, but the bot was configured inside an account your employee cannot access. When changing implementers, you may discover that the question extended beyond control of the number: who administers the business assets, authorizes access and supports transition?
Map assets before connecting the bot
Meta's official Postman collection introduction identifies separate Cloud API assets: a business portfolio, a WhatsApp Business Account or WABA, and a business number. Do not reduce these to the display name beside a conversation. Ask the implementer to explain their relationship in the proposed solution, including non-secret references.
There may also be an integration application, CRM-provider account and bot-hosting service. Administration can be distributed among your company, implementer and provider. Owners need not learn to generate credentials; they need to know who can grant or recover access and approve changes if a particular person is absent.
A test of proposal clarity
Imagine a printing center adding an order-intake bot to an established customer-service number. One proposal says “number connected”; another identifies the portfolio, business account, company administrator, implementer permissions and subscription management. This is fictional: no account was opened, number connected or message sent.
A table alone supplies no legal ownership or migration guarantee. It exposes unanswered questions: can an authorized company representative review the assets, do important notices reach an internal owner, and what remains administrable after implementation ends? Request appropriate access evidence rather than an unidentified screenshot.
A three-level asset card
For each level identify an internal owner, backup and access-recovery contact, with the implementer's boundaries. Exclude passwords, verification codes and keys. This is a proposed discussion and handover tool, not a judgment about ownership of an unreviewed account.
| Level | Clarify | Request evidence |
|---|---|---|
| Telephone number | Number administration and authorized verification access | Company control without sole dependence on an outsider |
| Meta assets | Portfolio, WABA and administrators | Authorized representative access, non-secret IDs and asset relationships |
| Implementation service | Application, provider, billing and operations | Implementer permissions, limits, renewal and change owners |
Add templates as items whose creation, review management and location need clarification. Number migration does not automatically establish transfer of every template or approval. If a provider account is involved, identify transferable deliverables and dependencies on its current policies and terms.
The SIM does not settle platform permissions
HubSpot's help-desk connection document separates company-portfolio administration, WABA control and number verification access. Use this as a concrete example of access layers rather than treating HubSpot as mandatory or applying its requirements to every chatbot provider.
Ask how the implementer receives necessary limited access, how that access is reviewed at completion, and who handles lost administration or an internal employee's departure. A shared password is not a continuity plan. Equally, do not revoke live access without understanding the impact and approving an alternative; ongoing operation might depend on it.
Discuss the app and history before selecting a path
HubSpot distinguishes standard connection from coexistence, which permits continued Business App use alongside the system under its requirements. History and media limits also differ. Do not generalize that every integration disables the app or that every transition preserves all earlier conversations and attachments.
Specify the proposed path, history behavior during change, who checks current requirements and who plans transition. Any potential interruption or company action should appear in the proposal. A provider's estimate for one operation does not guarantee your complete transition duration or platform approval.
What remains after handover?
Have the company representative explain how to locate assets and each responsible party without disclosing secrets in a recording. Retain a redacted evidence reference, review date and process for updating the card after employee or provider changes. This is more useful than a file whose permissions nobody knows are still valid.
Broader code, data and ownership questions and WhatsApp bot cost components remain separate topics. When discussing chatbot implementation with Nextwave, provide the requested asset and access map to compare operations and handover alongside conversation features.
Available references and limitations
The Meta Postman introduction and HubSpot documents on channel connection and coexistence were read on 4 November 2026. No migration, template-approval or partnership guarantee is offered. Prepared with AI assistance and information and translation review.
