Industry InsightsFeatured

WhatsApp Web 6-Hour Logout Rule in India: Complete Guide for Businesses

India's new DoT directive mandates automatic logout for WhatsApp Web and desktop sessions every 6 hours. Here's what your business needs to know and how to adapt.

Published

Feb 26, 2026

Reading time

10 minutes

Category

Industry Insights

What you'll learn

  • WhatsApp Web sessions will automatically logout every 6 hours
  • Rule applies to all web/PC clients including Telegram and Signal
  • Mobile app usage remains unaffected by this regulation
  • No exceptions have been granted for businesses
  • Cloud API integration bypasses session limitations entirely

What is the 6-Hour Logout Rule?

India's Department of Telecommunications (DoT) has introduced new regulations under the Telecom Cyber Security Rules that fundamentally change how WhatsApp Web and desktop applications function in the country.

The core requirement:

Any WhatsApp Web or desktop session must be forcibly logged out no later than 6 hours after it was linked.

This rule comes alongside SIM-binding requirements that tie messaging accounts to the original active SIM card used during registration.

Key Facts at a Glance

Session LimitMaximum 6 hours from QR code scan
TypeHard limit (not inactivity timeout)
Applies ToWhatsApp Web, Desktop, and similar platforms
Mobile AppNOT affected
ExceptionsNone granted
DeadlineFebruary 27, 2026

Which Platforms Are Affected?

Affected by the Rule

  • WhatsApp Web in all browsers
  • WhatsApp Desktop (Windows & macOS)
  • Telegram Web/Desktop clients
  • Signal Desktop application
  • Other messaging web/PC clients

NOT Affected

  • WhatsApp mobile app on your registered phone
  • WhatsApp Business mobile app on primary device
  • WhatsApp Cloud API integrations (server-side)
  • Normal mobile messaging patterns

Important: Your phone app can stay logged in as usual. Only web/desktop companion sessions face the 6-hour cap.

How the Logout Process Works

Understanding the session lifecycle helps you prepare your team for the changes:

1

Link WhatsApp Web

Open WhatsApp Web in your browser and scan the QR code from your phone. The 6-hour timer starts immediately.

2

Normal Usage Period

For the next 6 hours, use WhatsApp Web normally—send messages, receive notifications, access all chats.

3

Automatic Termination

Once 6 hours are reached, the platform terminates the session automatically. You'll see a prompt to re-link.

4

Re-authentication Required

To continue, you must open WhatsApp on your phone and scan a fresh QR code.

Critical: This is a hard upper limit. There's no "keep alive" option regardless of how actively you're using the session.

Why Is DoT Implementing This?

Combatting Cross-Border Cyber Fraud

"Long-lived web/desktop sessions are used for cross-border cyber-fraud: criminals authenticate once in India, then keep a web session alive abroad without the SIM/device, using Indian numbers for scams."

— DoT Official Documentation

Security Objectives

Terminate Unattended Sessions

That can be exploited remotely

Force Re-authentication

Proving control of phone/SIM

Mirror Banking Security

Where session timeouts are standard

Impact on Business Operations

Team TypeCurrent WorkflowAfter Implementation
Support agents (8hr shifts)Single login for entire shiftRe-scan at least once per shift
Sales teams on desktopAlways-on accessRe-authenticate every 6 hours
Operations with continuous messagingUninterrupted workflowsSession breaks mid-conversation
Customer serviceSeamless handoffsPotential gaps during re-scanning

Compliance Timeline

November 28, 2025

Directive issued

✓ Complete

February 27, 2026

Implementation deadline

⏳ Approaching

Late March 2026

Compliance report due

Pending

No extensions have been announced. DoT has confirmed the February 27, 2026 deadline is final.

How to Adapt Your Workflows

Immediate Actions (This Week)

1

Communicate Changes to Your Team

Send a clear notification to all team members who use WhatsApp Web about the upcoming 6-hour session limit.

2

Schedule Re-authentication Breaks

Plan 5-minute breaks at 6-hour intervals. Create backup coverage during re-authentication periods.

3

Update Documentation

Add re-scanning procedures to training materials. Create visual guides for the process.

Long-Term Solution: WhatsApp Cloud API

Recommended for businesses needing uninterrupted messaging

FeatureWhatsApp WebCloud API
Session limit6 hoursNo limit
Requires phoneYesNo
Automated workflowsLimitedFull support
Team collaborationManualBuilt-in
UptimeUser-dependent99.9% SLA

How Cloud API Bypasses the Limit

  • Operates server-side (not in browser)
  • Not dependent on web sessions
  • Automated workflows continue uninterrupted

Get Started with Cloud API

Partner with a Meta BSP like Whats91 for enhanced features and expert support.

Business Preparation Checklist

1
Phase 1: Assessment

  • Document current WhatsApp Web usage across teams
  • Calculate hours of continuous usage per agent
  • Identify workflows most dependent on web access
  • Estimate potential productivity impact

2
Phase 2: Planning

  • Choose adaptation strategy (Cloud API or workflow changes)
  • Create budget for new tools or services
  • Assign implementation lead
  • Set internal deadlines before February 27

3
Phase 3: Implementation

  • Set up Cloud API integration (if chosen)
  • Train staff on new procedures
  • Update documentation and policies
  • Configure backup communication methods

4
Phase 4: Testing

  • Run simulated scenarios with 6-hour limits
  • Test mid-conversation session drops
  • Verify Cloud API workflows (if applicable)
  • Gather team feedback and adjust

Frequently Asked Questions

Can businesses get exceptions?

No. The government has stated there will be no relaxation of either the 6-hour requirement or the February 27 deadline.

What happens during an active call?

If you're on a WhatsApp Web call approaching the 6-hour mark, the session (including the call) will be terminated.

Will I lose unsent messages?

Possibly. Messages being typed when the session terminates may be lost. Best practice: draft longer messages in a separate document.

Does staying active extend the session?

No. The rule explicitly states this is a hard limit regardless of user activity.

Is my chat history affected?

No. Chat history remains intact. Only the current session is terminated. All messages sync when you reconnect.

Key Takeaways

The deadline is final — February 27, 2026 is the compliance date
Plan for session breaks — Adjust workflows for re-authentication
Consider Cloud API — For uninterrupted business messaging
Train your team — Everyone needs to understand the new process
Document everything — Create clear internal guidelines

Found this helpful?

Share it with your network

Whats91 Team

Written by

Whats91 Team

WhatsApp Cloud API Experts

The Whats91 team specializes in helping Indian businesses implement WhatsApp Cloud API for enterprise communication, ERP integration, and customer engagement.