Assess an existing WhatsApp setup before changing providers
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
Do not treat a new provider’s onboarding form as proof that your existing WhatsApp setup can move. Before scheduling work, document which account and number you use, who controls them, what services depend on them, and which transition route both providers have confirmed in writing.
The useful output is a dependency assessment, not a migration date. It should separate verified facts from assumptions and show exactly what prevents a decision. A business can be ready to evaluate a provider while still being unready to authorise changes to its live number.
The assessment below is a recommended operating practice. It does not establish that a particular transfer route, retained history, coexistence arrangement or uninterrupted service is available.
1. Establish what the business actually has
Start with the existing service, not the destination provider’s sales description. Ask the person responsible for the current setup to identify the account, registered number and provider relationship using records they can inspect.
Record the following in one shared assessment:
- Business identity and account assets: the business portfolio and WhatsApp business account identifiers, where applicable, and the business that controls them.
- Number registration: the exact number in international format and the account or service under which it is registered.
- Current operating model: whether staff use an app, a provider-managed inbox, a Platform-connected service or a combination that needs investigation.
- Commercial relationship: the contracting business, current provider and any agency or reseller between them.
- Access holders: named internal administrators and external parties with relevant permissions.
Do not infer ownership from a working inbox login or a bill. Those records may establish access or payment responsibility without settling control of the underlying account. Likewise, knowing an account identifier is not proof that someone is authorised to change it.
Attach evidence references rather than passwords or recovery codes. An internal record can point to an access review, account screenshot or provider ticket stored in a restricted location.
2. Separate number control from account access
A common assessment failure is to write “we own the number” when the only evidence is that customers call it. Break that statement into questions that can be answered separately.
- Who holds the telephone service account for the number?
- Who can receive verification communications, if required for the proposed route?
- Who can authorise changes within the current business account?
- Who controls any relevant security settings, and what is the authorised recovery process?
- Does an agency or former employee hold access that the business cannot currently administer?
These are discovery questions, not a claim that every route requires the same verification or security steps. Ask the providers which requirements apply to the exact source and destination arrangement.
Use least-privilege access during discovery: people should receive only the access needed to inspect or confirm their part of the setup. Do not solve an unclear ownership chain by sharing an administrator’s credentials.
If control is disputed or unproven, record a blocker. Starting destination onboarding will not, by itself, resolve the source-side authority problem.
3. Inventory what would stop working or become inaccessible
The number is only one dependency. A provider change can also affect the tools and records surrounding conversations. Assess each dependency independently rather than using a single “data migration” checkbox.
Conversation operations
List shared inboxes, agent assignments, queues, open cases, conversation notes and attachments. Ask whether each item can be exported, accessed after termination, imported at the destination or only retained as a separate archive. Treat those as different outcomes.
Connected business processes
Identify CRM updates, webhooks, order notifications, scheduled campaigns, reporting jobs and automated replies. For each connection, name the owner, trigger and business consequence of failure. An outbound notification may stop while the inbox still appears healthy.
Messaging readiness
Record where templates, recipient permission evidence and opt-out records are maintained. Do not assume these records or their operational enforcement will appear in the destination workspace without specific confirmation.
Under the WhatsApp Business Messaging Policy, recipient permission matters and opt-outs must be honoured. Approved templates are used to initiate Platform conversations and outside the customer-service window, which opens or resets with a user message and lasts 24 hours. Template approval does not guarantee delivery. Consequently, campaign preparation, template review and actual delivery should remain separate readiness states in your assessment.
If automation is involved, include its human escalation path as a dependency. The destination is not operationally equivalent merely because it can send a response; staff also need a workable way to receive and resolve escalations.
4. Ask both providers to confirm the same proposed route
A general statement that a provider supports transfers is not a decision-ready answer. Send both providers the same concise description of the existing setup and proposed destination. Include relevant identifiers through an appropriate private support channel.
Request written answers covering:
- Applicability: Is the proposed route supported for these specific source assets and this destination arrangement?
- Prerequisites: What permissions, account conditions, security actions or approvals must be satisfied, and by whom?
- Source actions: Must the current provider release, disconnect or change anything? Which actions could be destructive or difficult to reverse?
- Destination outcomes: What happens to the number registration, templates, history, attachments, settings and integrations? Ask about each separately.
- Service constraints: What restrictions or service interruption risks apply? What remains unknown until a later check?
- Failure handling: If an action fails, who investigates, what evidence is needed and what recovery options are actually available?
Ask each provider to identify assumptions and exclusions. A destination answer conditioned on source release is not confirmation that source release is available. Similarly, a source export capability does not establish destination import support.
Keep confirmations attached to the exact route discussed. If the destination account, number or provider arrangement changes, ask whether the earlier answer still applies.
5. Use explicit evidence states
Every material assessment line should carry a status, evidence reference, owner and next action. A simple set of states is sufficient:
- Confirmed fact: supported by an inspected record or written answer that applies to this setup.
- Conditional option: described as possible, but dependent on a named prerequisite that is not yet satisfied.
- Unknown: no applicable evidence has been obtained.
- Blocker: an unresolved condition prevents the business from approving the proposed route.
- Not required: deliberately excluded, with an accountable business owner accepting the consequence.
“Confirmed” should be narrow. Confirmed permission to export conversation records means exactly that; it does not mean history will appear in the new inbox. Where providers give conflicting answers, retain both and mark the affected decision as blocked rather than choosing the more convenient response.
6. Fictional worked example: a completed assessment
The following business, evidence references, provider responses and decisions are entirely hypothetical. They illustrate how to complete the assessment, not capabilities offered by any provider or results achieved by an Alactic customer.
Business: Cedar Desk Supplies. Purpose: assess whether its existing customer-service number can be used with a prospective provider. Assessment owner: operations manager. Current decision: continue feasibility enquiries; do not schedule live changes.
Source assets and number control
- Business account and number — confirmed fact. The operations manager matched the account identifiers and full telephone number in the current workspace to the provider’s written inventory. Evidence: restricted record A. Next action: include these identifiers in the destination feasibility request.
- Telephone service control — confirmed fact. The finance manager inspected the telephone service account and confirmed the business is the account holder. Evidence: record B. This does not establish that all registration prerequisites are satisfied.
- Administrative access — confirmed fact with a gap. An internal administrator can inspect the relevant business assets. An external agency also has access. Evidence: access review C. Next action: document which changes require the agency and remove unnecessary access through an authorised process.
- Security prerequisite — unknown. The person responsible for a relevant security setting has not been identified. Owner: internal administrator. Next action: obtain the supported verification or recovery procedure without circulating credentials.
Existing service dependencies
- Shared inbox and open cases — blocker. Supervisors rely on current assignments and notes. The source provider has confirmed that a conversation export is available, but has not specified its contents. The destination has not confirmed import support. Owner: service lead. Required decision: acceptable archival access versus operational continuity for open cases.
- Order notifications — unknown. An internal application sends events to the current provider. Owner: engineering lead. Required evidence: connection inventory and destination compatibility assessment. No replacement connection has been authorised.
- Templates — conditional option. The prospective provider has requested the current template inventory before assessing what can be used at the destination. Owner: messaging lead. Next action: supply the inventory and obtain an asset-specific answer.
- Permission and opt-out records — blocker. Permission evidence is held in the CRM, while a separate suppression list is maintained in the current messaging service. Owner: CRM administrator. Next action: reconcile the records and confirm how opt-outs would be enforced in the proposed operating design.
- Automated triage — unknown. The current automation sends unresolved requests to a supervisor queue. Owner: service lead. Next action: define the required human handoff and establish whether the destination workspace and plan support it.
Written confirmations and unresolved blockers
- Confirmed source-side option: the current provider has offered an export and a review of the proposed transition request. This confirms neither transfer feasibility nor destination import.
- Conditional transfer option: the prospective provider has described a possible route, subject to reviewing the exact source arrangement and security prerequisites. No end-to-end transfer option is confirmed.
- Current provider confirmation needed: required source actions, export scope, post-termination access and consequences of disconnecting service.
- Prospective provider confirmation needed: applicability of the route, prerequisites, treatment of each asset, integration requirements and failure escalation.
- Unresolved blockers: security control, open-case access, opt-out enforcement and the lack of matching written route confirmations.
- Decision owner: operations manager. Next review occurs when blocker owners supply evidence, not when a preferred launch date arrives.
7. Compare trade-offs and define a safe stop
Once options are documented, compare what each would preserve, replace or leave behind. Keeping historical records in a separate archive may be acceptable for occasional reference but unsuitable if agents need those records during every active case. Rebuilding an integration may provide a clearer operating design but require more engineering work than the business expected.
Keep commercial dependencies separate too. Record provider subscription commitments, export charges if applicable, and termination conditions from actual written terms. For future cost assessment, separate provider or platform subscriptions, Meta messaging charges and AI usage. Consult the current Meta pricing information for message-category, recipient-market and applicable exception details rather than carrying an old rate assumption into the decision.
Define a stop condition before anyone changes the source setup. If required authority is missing, provider answers conflict or the business cannot accept a documented loss of access, pause the proposed route. Do not cancel the current service merely to discover whether cancellation unlocks the next step.
If a premature action has already occurred, record exactly what changed and when, preserve available error evidence, and contact the responsible providers. Do not assume that re-registering, reconnecting or repeating the action will restore the previous state. Recovery options need confirmation just as the original route does.
8. Make the next decision measurable
The next action is an evidence review, not a launch booking. Assign an owner to every unknown and send a single, consistent confirmation request to both providers.
At the review, report three observable measures: how many critical dependencies have applicable evidence, how many blockers remain, and how many provider answers still conflict. Do not use a high completion percentage to hide one unresolved critical dependency.
Approve transition planning only when the business has a documented route, named prerequisite owners, accepted handling for existing services and records, and written answers for material failure scenarios. That approval permits detailed planning; it is not a promise that the eventual transition will succeed without interruption.
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