WhatsApp Web Sessions and Official API Migration: A Planning Guide

PIB’s 1 December 2025 release reports DoT directions issued on 28 November 2025 for specified app-based communication services using Indian mobile numbers. It describes periodic web-service logout no later than six hours, re-linking and a 90-day implementation requirement.

That historical announcement does not establish the behavior of every integration today, a timer starting at every QR scan, a universal exemption for Cloud API or a verified deadline for your account. This guide does not certify current enforcement or legal compliance. Check the current applicable provider and regulatory position before relying on a specific cutoff.

The practical migration question is narrower: does your current automation depend on a browser-linked session, how do you notice a disconnect, and what stops or recovers safely? Keep the observation separate from the rule’s legal scope.

Some unofficial integrations imitate a web client; others may have different mechanisms. Record the actual software, connection method, account owner and support arrangement rather than asserting that all such APIs fail in the same way.

An interrupted session can leave payment reminders, invoice messages or support routing incomplete. It does not tell you whether every queued message failed, whether one was already delivered or whether a retry would duplicate it. Preserve business references and investigate actual status.

Do not plan a keep-alive workaround or an undocumented bypass as a business reliability strategy. Evaluate a permitted, supported path and an operator fallback. Equally, an official API label is not a promise of uninterrupted service or immunity from restrictions.

Identify whether the number is on the Business App, already API-only or new. Assess coexistence and standard registration separately. Do not delete, deactivate, disconnect or re-register a working account based on this guide; agree a supported migration, backup and recovery plan first.

Coexistence is an option to assess for an existing Business App number. Confirm eligibility for that number, account, country, app/API version and rollout before planning a hybrid setup. This guide does not confirm availability for your account.

Confirm whether history and media import is offered, which records are included, consent, linked-device support and synchronization behavior. No fixed import period, device count or complete CRM history is guaranteed.

A standard path means your team needs an API application and a chosen inbox or integration. Document where staff will answer, which permissions they receive and how attachments, assignment and escalation will work. Do not assume a particular provider portal is the only possible interface.

Confirm the transition steps for an existing app or API number before unregistering anything. Display-name treatment, business verification and badge approval are separate questions; a demonstration of a branded profile does not prove your account will receive that display.

Choose a reversible sequence where the supported flow allows one. Agree how to stop the old automation, reconcile outstanding records and recover if registration or the new inbox is unavailable. Do not delete a working account based on this guide.

A hybrid assessment is useful when staff need the Business App as well as API automation. Assess the exact number, country, app/API version and provider flow. Confirm how manual and automated replies are distinguished and how operators avoid duplicate answers.

Ask which records, attachments and devices carry over, which remain in the app and what the integration actually stores. A connected account is not proof that every historical chat became CRM data. Confirm permission and retention for the records you intend to copy.

Phone changes, inactivity, disconnects and app updates can affect operations. Obtain the supported connection and recovery instructions for your account; this page establishes no fixed inactivity period, automatic reconnection or permanent avoidance of re-authentication.

The Business Messaging Policy calls for accurate business identity and customer support contact information. Use details that describe the actual operator and the service customers receive. A name, brand affiliation or verification document must not be invented to obtain approval.

If the selected verification flow requests a website, use a functioning site that genuinely describes your business and check the requested ownership/details with the provider. Do not submit a dummy website or fabricated evidence to pass review. The detailed verification documentation could not be retrieved for this check, so this page does not assert a universal list of required documents or domains.

Business-profile contact options, business verification and the privacy duties relevant to your own operation are distinct. Whats91’s operator details and legal documents do not become universal customer website requirements. Confirm what applies to your business and onboarding flow.

Onboarding, verification, template review and integration timing depend on the account, provider, workflow and outstanding approvals. Confirm the scope and schedule with the team; no instant approval, fixed waiting period or go-live deadline is promised.

A customer message opens or resets the 24-hour reply window. Outside it, an approved template is needed. Permission to use a message format does not determine its price; confirm the effective category, allowance and account conditions separately.

Inventory first-contact, follow-up and support messages separately. Record the intended purpose, recipient permission and template status for the actual flow. Approval of a template is not permission to send it to every stored contact.

Keep an operator route for invalid customer mappings, disputed balances, failed media or unresolved delivery. A change in connection model should not remove the customer’s way to get help. Review opt-outs before moving any contact list.

Effective 1 October 2026; original INR billing card, per delivered message. This schedule is not the price for messages delivered before 1 October 2026. Whats91 passes through Meta messaging charges without markup. Whats91 platform subscriptions, setup, integrations and applicable taxes are separate.

Meta’s public pricing page, checked 29 September 2026, describes charges for delivered messages by recipient market and category. Keep an API acknowledgement, delivery evidence and an invoice as separate records. A queued or accepted request is not a final charge; missing evidence leaves billing unresolved.

Whats91 platform subscriptions: Coexistence ₹699/month or ₹5,000/year; Standard ₹949/month or ₹7,000/year. Monthly billing has a one-time setup fee of ₹1,000 or ₹2,000 respectively; annual billing includes setup. These amounts exclude 18% GST, added on top. Meta message charges pass through separately without Whats91 markup. Add-ons, feature eligibility, trials, renewal, invoice treatment and activation need separate confirmation. No payment or activation is available on this website.

Separate number/onboarding work, ERP integration, inbox/subscription, message charges and invoice treatment. Confirm duration, renewal and cancellation in writing. There is no confirmed two-year or three-year saving, price lock or universal provider markup here.

Readiness is a sequence of checks, not a fixed go-live promise. Agree who can approve each stage and which failure prevents the next one. Preserve an operator-controlled pause so a broken mapping or uncertain delivery state does not trigger more sends.

Cutover decision map

Assess, rehearse and retain a recovery path

A browser-linked dependency needs an inventory and stop criteria before any separately authorized migration.

01

Assess

Record the current session dependency, number state and supported path.

02

Rehearse

Test synthetic failures and uncertain delivery without customer traffic.

03

Recover

Set an operator pause and rollback criteria before a pilot.

A synthetic rehearsal can exercise state handling and reconciliation without accessing customer accounts. A real pilot needs separate authority, confirmed recipients and a supported account. Do not treat a website contact enquiry as authorization to register a number or send messages.

Whats91 onboarding assistance, integrations, support channels and response commitments depend on your agreed service scope. Provider/account approval is separate from Whats91 assistance; no organization policy establishes universal Meta eligibility.

For a migration discussion, bring the connection method, number state, operator needs, history scope and outstanding queue. Ask for a written path, cost scope and recovery plan. A supported migration can be evaluated without promising that every old workflow, mobile feature or stored conversation will transfer.