WhatsApp WiFi Login: The Definitive Technical & Business Guide

WhatsApp-based WiFi authentication is rare in the white-label WiFi marketing space. That's not a competitive jab — it's a statement of market fact as of March 2026. WhatsApp OTP login for captive portals is a white-label capability, and the conversion data from early deployments explains why it matters.

In markets where WhatsApp penetration exceeds 60% of the smartphone population, WhatsApp OTP consistently outperforms email capture by 15–25 percentage points on capture rate. A hotel chain operating across Spain, Portugal, and Mexico reported a 52% average capture rate with WhatsApp OTP across 34 properties — compared to 29% when those same properties ran email-only portals in the prior quarter. The delta isn't subtle.

This guide covers every dimension: how WhatsApp OTP technically works, how to set it up, which markets it dominates, how it affects GDPR compliance, what campaign strategies it enables, and what the ROI looks like for resellers deploying it.

---

How WhatsApp WiFi Login Works: The Technical Flow

The WhatsApp OTP flow is a five-step process that happens in under 30 seconds for the guest.

Step 1: Guest Connects to WiFi

The guest selects the venue's WiFi network on their device. The access point intercepts the connection and redirects the browser to the captive portal.

Step 2: Portal Displays WhatsApp OTP Option

The captive portal renders with WhatsApp OTP as the primary (or one of several) authentication methods. The guest sees a "Connect with WhatsApp" button or a phone number input field with a "Send WhatsApp OTP" action.

Step 3: Guest Enters Phone Number

The guest types their phone number (with country code auto-detected based on device locale). The platform validates the number format.

Step 4: OTP Delivered via WhatsApp

The platform sends a one-time password (typically 6 digits) to the guest's WhatsApp number via the WhatsApp Business API. The message arrives as a WhatsApp message from the venue's branded WhatsApp Business account (or the reseller's account, depending on configuration).

The message contains the OTP code and typically a brief welcome message: "Your WiFi access code is 847291. Welcome to [Venue Name]!"

Step 5: Guest Enters OTP or Taps Link

The guest can either:

• •Switch back to the browser and type the 6-digit code (manual entry)
• •Tap a deep link in the WhatsApp message that auto-completes the authentication (one-tap)

Upon successful OTP validation, the platform tells the access point to grant internet access. The guest is redirected to the configured post-login destination (venue website, offer page, review prompt, etc.).

What Happens Under the Hood

[Guest Device] ──WiFi connect──→ [Access Point]
                                      ↓
                              [HTTP 302 redirect]
                                      ↓
                          [Captive Portal (CDN)]
                           Guest enters phone #
                                      ↓
                    [WiFi Marketing Platform (API)]
                           Generates OTP token
                                      ↓
                    [WhatsApp Business API (Meta)]
                           Delivers OTP message
                                      ↓
                         [Guest's WhatsApp App]
                           Guest taps link / enters code
                                      ↓
                    [Platform validates OTP]
                           Sends RADIUS accept → AP
                                      ↓
                         [Internet access granted]

The entire flow runs on cloud infrastructure. No WhatsApp code runs on the access point. The AP's only job is the initial redirect and the final access grant — the same role it plays with any captive portal authentication method.

Latency Breakdown

Compare this to email login (15–45 seconds — typing is slower than tapping) or SMS OTP (15–40 seconds — SMS delivery can be slower than WhatsApp). The WhatsApp flow feels fast because the input is a phone number (short) and the response is in an app the guest already has open.

---

Why WhatsApp OTP Outperforms Email Capture

The conversion advantage isn't theoretical. It comes from three structural factors.

Factor 1: Reduced Input Friction

Entering an email address on a mobile device requires typing an average of 22 characters (including the @ symbol, domain, and TLD). Phone numbers require 10–11 digits. Typing speed on mobile keyboards averages 38 words per minute — but email addresses contain special characters (@, dots) that require keyboard switching. Phone numbers are pure numeric keypad input.

The result: entering a phone number takes 40–60% less time and effort than entering an email address on a smartphone.

Factor 2: WhatsApp Is Already Open

In WhatsApp-dominant markets, the app is literally the most-used application on the phone. The average WhatsApp user opens the app 23–25 times per day (Meta's published usage data). When the OTP message arrives, it appears as a notification — often while WhatsApp is already the active app. The guest doesn't need to open a separate app, navigate to an inbox, or search for a code.

Compare this to email OTP: the guest must open their email app (which might not even be logged in on mobile), find the OTP message (which might be in spam), read the code, switch back to the browser, and type it. Every step is a drop-off opportunity.

Factor 3: Trust in the Channel

WhatsApp messages feel personal. Email from unknown senders feels like spam. A WhatsApp message from a verified business account (with the green checkmark badge) carries implicit trust that a cold email never achieves. Guests are more willing to provide their phone number for WhatsApp OTP than they are to provide their "real" email address, because they trust WhatsApp's privacy model and they know they can block the sender.

The Conversion Data

Aggregated across early deployments in WhatsApp-dominant markets (2024–2026):

The 17-point gap between email and WhatsApp OTP represents hundreds of additional captured guests per month at a typical venue. For a restaurant with 2,000 monthly WiFi connections, that's the difference between 700 captured guests and 1,040 — a 49% increase in the size of the marketing database from the same traffic.

---

Market-by-Market WhatsApp Adoption

WhatsApp OTP login is not effective everywhere. It's highly effective in markets where WhatsApp is the dominant messaging platform and less relevant where it's not.

Tier 1: WhatsApp Dominant (>80% Penetration)

These markets are where WhatsApp OTP delivers the strongest results.

Tier 2: WhatsApp Strong (50–80% Penetration)

WhatsApp OTP is effective but should be offered alongside other methods.

Tier 3: WhatsApp Weak (<50% Penetration)

WhatsApp OTP is not recommended as primary in these markets.

The US Exception: While US-wide WhatsApp penetration is only 33%, it's significantly higher among Hispanic/Latino populations (estimated 60–70%), in cities with large immigrant communities, and among international business travelers. A hotel in Miami or a restaurant in Los Angeles may see WhatsApp OTP outperform email even in the US — the national average masks significant local variation.

---

WhatsApp Business API: The Technical Foundation

WhatsApp OTP login requires a WhatsApp Business API connection. The WiFi marketing platform handles this integration, but understanding the components helps you explain the setup to clients and troubleshoot issues.

Components

WhatsApp Business Account (WABA) A business account registered with Meta's WhatsApp Business Platform. The WABA holds the business profile (name, logo, description, category) and the phone number(s) associated with the account.

Business Solution Provider (BSP) The entity that provides API access to the WhatsApp Business Platform. The WiFi marketing platform acts as a BSP (or connects through one), handling the API calls, message templates, and delivery infrastructure.

Message Templates WhatsApp requires pre-approved message templates for business-initiated messages. The OTP template is typically a simple format: "Your WiFi access code is {{OTP}}. Welcome to {{venue_name}}!" Templates must be submitted to Meta for approval before use.

Phone Number The WhatsApp Business account uses a dedicated phone number. This can be the venue's existing business number (if not already used for WhatsApp Business), a new number provisioned for this purpose, or a shared number managed by the platform.

Setup Process (Platform-Managed)

For resellers using the MyWiFi platform, the WhatsApp Business API setup is handled within the platform:

1. •Enable WhatsApp OTP add-on ($99/month on Agency, MSP, or Enterprise plans)
2. •Register the WhatsApp Business Account (or connect an existing WABA)
3. •Submit and approve OTP message template (typically approved within 24 hours)
4. •Configure the captive portal to display WhatsApp OTP as an authentication option
5. •Test the flow end-to-end with a real device

Total setup time: 1–2 hours (plus up to 24 hours for template approval).

Costs

WhatsApp Business API messages have per-message costs set by Meta. These vary by country and message type:

These costs are in addition to the $99/month platform add-on fee. At 1,000 OTP messages per month in a European market, the per-message cost adds approximately $35/month. At 5,000 messages, approximately $175/month. Factor these into your pricing model.

---

The GDPR Advantage: Why WhatsApp OTP Is Compliance-Friendly

This is counterintuitive. Most resellers assume WhatsApp OTP is more complex from a privacy perspective than email. The opposite is true.

The Consent Problem with Email

When a guest provides an email address on a captive portal, the consent is often ambiguous. Did they consent to receive marketing emails? Or did they just want WiFi access? GDPR requires that consent be "freely given, specific, informed, and unambiguous." If the only way to get WiFi is to provide an email, and the consent checkbox says "I agree to receive marketing emails," regulators have questioned whether that consent is truly "freely given" — because the alternative (no WiFi) creates coercion.

Why WhatsApp Consent Is Stronger

WhatsApp's platform model provides an additional consent layer that email doesn't have.

1. •

   Double consent. The guest consents on the captive portal (first consent — to receive a WhatsApp message). Then, when they interact with the WhatsApp message, they implicitly opt into the WhatsApp Business conversation (second consent — WhatsApp's own opt-in model). This layered consent is stronger than a single email checkbox.

2. •

   Easy opt-out. WhatsApp provides a native "Block" and "Report" mechanism built into the app. Guests can block the business number with one tap — no unsubscribe links to find, no CAN-SPAM compliance to manage. The ease of opt-out actually strengthens the consent argument: the guest can withdraw at any time, trivially.

3. •

   Verified identity. WhatsApp numbers are tied to phone numbers, which are tied to SIM cards. There are no "disposable WhatsApp numbers" equivalent to disposable email addresses. The data quality is inherently higher, and the identity verification is inherently stronger.

4. •

   Transparent channel. WhatsApp Business messages are labeled as business messages. The guest knows they're receiving a business communication. There's no ambiguity about the sender or the nature of the message.

Practical Compliance Configuration

For GDPR-compliant WhatsApp OTP deployment:

• •Captive portal consent checkbox: "I agree to receive a WhatsApp message containing my WiFi access code. [Venue name] may send me promotional messages via WhatsApp. I can opt out at any time by blocking this number." [Privacy Policy link]
• •The consent checkbox must not be pre-checked
• •Store the consent record: timestamp, consent text version, guest phone number, device identifier, IP address
• •Configure data retention (12–24 months is common)
• •Ensure the platform's Data Processing Agreement (DPA) covers WhatsApp data processing

---

The WhatsApp-First Markets: Deep Dive

Understanding the market dynamics in WhatsApp-dominant regions helps resellers position the feature correctly and set accurate expectations.

Latin America: The 95%+ Market

WhatsApp is not just a messaging app in Latin America — it's the internet. In Brazil, WhatsApp is the primary communication channel for 99% of smartphone users. People pay bills through WhatsApp. They book medical appointments through WhatsApp. They order food through WhatsApp.

For WiFi marketing in LATAM, WhatsApp OTP isn't an option — it's the only option that makes sense. Email-only portals in Brazil capture 20–25% (well below the global email average) because email is less culturally embedded. WhatsApp OTP captures 55–65% in the same venues.

Key LATAM considerations:

• •Portuguese (Brazil) and Spanish (rest of LATAM) portal language detection is critical
• •WhatsApp message templates must be submitted in the local language
• •Per-message costs are slightly higher in LATAM than in Asia, but still lower than SMS
• •Internet speeds at venues can be slower than in North America/Europe — optimize portal load time aggressively

Europe: The Consent-Friendly Market

WhatsApp OTP has a unique advantage in GDPR-regulated Europe: the double-consent model (portal consent + WhatsApp implicit consent) actually strengthens the legal basis for marketing communications. European DPAs have been scrutinous of email consent on WiFi portals — the "freely given" requirement is harder to satisfy when WiFi access is conditional on providing an email.

WhatsApp OTP reframes the exchange: the guest provides their phone number to receive an access code (a utility purpose, not a marketing purpose). The marketing consent is separate and optional. This clean separation between service consent and marketing consent aligns better with GDPR principles.

European deployment patterns:

• •Spain and Italy: WhatsApp-first, email fallback (90%+ WhatsApp penetration)
• •Germany and Netherlands: WhatsApp-first, email equal (85%+ penetration)
• •France: Dual option (58% penetration — significant but not dominant)
• •UK: Dual option (80% penetration, but strong email culture)
• •Nordics: Email-first (lower WhatsApp adoption, strong email infrastructure)

Middle East and Africa: The Mobile-First Market

In the UAE, Saudi Arabia, and much of sub-Saharan Africa, WhatsApp is the default communication platform. Mobile-first internet usage means many users don't even have a personal email address — but they all have WhatsApp.

For resellers serving hospitality clients in Dubai, Riyadh, or Cape Town, WhatsApp OTP may be the only authentication method that reaches the full guest population. Email-only portals miss a significant segment of guests who either don't have email or don't check it regularly.

---

Campaign Strategies: What WhatsApp Enables Beyond OTP

WhatsApp OTP captures the phone number. But the real value is the messaging channel it opens.

The WhatsApp Campaign Stack

Once a guest has authenticated via WhatsApp OTP, the reseller (or venue) has a WhatsApp messaging relationship with that guest. This enables several campaign types that email and SMS cannot replicate.

1. Rich Media Messages WhatsApp supports images, videos, PDFs, and interactive buttons in business messages. A restaurant can send a visually rich message featuring the weekly specials with a "Book a Table" button. An email with the same content has a 20% open rate. A WhatsApp message has a 90%+ open rate.

2. Interactive Reply Buttons WhatsApp Business messages can include up to 3 reply buttons. "Rate your visit: Great / OK / Poor." The guest taps a button instead of typing a response. Completion rates for button-based feedback are 3–5x higher than email survey completion rates.

3. Post-Visit Follow-Up Automated WhatsApp message sent 2 hours after disconnect: "Thanks for visiting [Venue Name]! Here's 10% off your next visit: [link]. Reply STOP to opt out."

WhatsApp follow-up messages consistently outperform email follow-up on open rate (90%+ vs. 20–25%), click rate (15–25% vs. 2–5%), and time-to-open (median: 3 minutes vs. 4+ hours for email).

4. Birthday and Loyalty Messages If birthday data was captured (or if the platform calculates approximate birthday from social login data), WhatsApp birthday messages have near-100% open rates and 30–40% redemption rates on attached offers.

5. Re-Engagement Campaigns "We haven't seen you in a while! Here's a welcome-back offer." Delivered via WhatsApp to guests who haven't visited in 14+ days. Re-engagement via WhatsApp achieves 3–4x the response rate of email re-engagement.

Campaign Compliance

WhatsApp Business messaging has stricter rules than email marketing:

• •24-hour session window. After the last guest-initiated interaction, you have 24 hours to send free-form messages. Outside this window, you must use pre-approved message templates.
• •Template approval. All business-initiated messages must use templates approved by Meta. Templates are categorized as Marketing, Utility, or Authentication. Marketing templates have higher per-message costs than Utility or Authentication templates.
• •Quality rating. Meta monitors message quality based on blocks, reports, and response rates. Low quality ratings can result in messaging limits or account suspension. Send valuable messages, not spam.
• •Opt-out respect. If a guest blocks your number or sends "STOP," immediately cease messaging. WhatsApp's platform enforces this, but your automation system should also flag the opt-out.

---

ROI Analysis: WhatsApp OTP vs. Email

The ROI of WhatsApp OTP over email login has two components: the capture rate improvement (more guests in the database) and the campaign performance improvement (higher engagement per guest).

Capture Rate Impact

For a venue with 3,000 monthly WiFi connections in a Tier 1 WhatsApp market:

The usable contact gap is even larger than the capture rate gap because WhatsApp numbers are verified (virtually zero fake entries) while email lists always contain disposable and invalid addresses.

Campaign Performance Impact

For the same venue running a monthly promotion to their captured guests:

These figures are illustrative and represent optimistic projections. Real results depend on offer quality, venue type, messaging frequency, and guest demographics. But the structural advantage is clear: higher capture rates compound with higher engagement rates to produce dramatically different outcomes.

Cost Comparison

The additional cost of WhatsApp OTP is $165–$325/month. If the campaign-attributed revenue difference is even 10% of the illustrative figures above, the ROI is overwhelmingly positive.

---

Deployment Scenarios

Scenario 1: Single-Market, High-WhatsApp Penetration

A reseller serving 15 restaurant locations in Madrid, Spain (WhatsApp penetration: 97%).

Configuration: WhatsApp OTP as the only authentication method. No email fallback. The portal shows a phone number field and a "Connect via WhatsApp" button. Clean, fast, optimized for one path.

Result: Average 55% capture rate across all 15 locations. Zero fake entries. WhatsApp campaign engagement 4x higher than their previous email campaigns.

Scenario 2: Multi-Market, Mixed Penetration

A reseller serving 40 hotel properties across Europe: 12 in Spain/Portugal, 8 in Germany, 10 in France, 5 in UK, 5 in Scandinavia.

Configuration: WhatsApp OTP as primary in Spain/Portugal and Germany. Dual option (WhatsApp OTP + email) in France and UK. Email primary in Scandinavia (lower WhatsApp penetration, higher email culture).

Result: Capture rates varied by market: Spain 54%, Germany 48%, France 42%, UK 40%, Scandinavia 38%. The weighted average across all 40 properties was 46% — up from 31% when all properties ran email-only.

Scenario 3: US Market with Target Demographics

A reseller serving 8 restaurant locations in South Florida, targeting neighborhoods with high Hispanic/Latino populations.

Configuration: Dual option — WhatsApp OTP and email, with WhatsApp positioned as the primary button. Portal language auto-detection renders Spanish for Spanish-language devices.

Result: 48% of guests chose WhatsApp OTP. 33% chose email. 19% abandoned. Combined capture rate: 81% — significantly above the US restaurant average of 35–40%. WhatsApp adoption tracked closely with Spanish-language device detection.

---

WhatsApp vs. SMS OTP: The Detailed Comparison

Resellers often ask: "Why WhatsApp OTP instead of regular SMS OTP? They both use phone numbers."

The answer is in six dimensions.

Delivery Reliability

SMS delivery is subject to carrier filtering, international routing delays, and message prioritization. In some markets (India, Brazil, parts of Africa), SMS delivery rates for OTP messages can drop below 80% due to carrier-level spam filtering and DND (Do Not Disturb) registries.

WhatsApp messages route over the internet, bypassing carrier infrastructure entirely. Delivery rates for WhatsApp Business API messages consistently exceed 98% globally. The message arrives over the guest's existing data connection (which they have, because they're at a venue trying to get WiFi — they have mobile data).

Delivery Speed

SMS OTP messages typically arrive within 5–30 seconds, but outliers of 1–2 minutes are common, especially for international numbers. Guests don't wait 2 minutes for a WiFi code — they abandon.

WhatsApp messages typically arrive within 1–3 seconds. The near-instant delivery keeps the guest's attention and maintains the authentication flow momentum.

Cost Per Message

SMS costs vary wildly by country and direction. Sending an SMS from a US-based Twilio account to a phone in Brazil costs approximately $0.0725/message. Sending to India costs approximately $0.035/message. These costs add up quickly at scale.

WhatsApp Business API authentication messages cost approximately $0.004–$0.035/message depending on the recipient's country. In many markets, WhatsApp is cheaper than SMS. In a few (primarily US domestic), the costs are comparable.

In the US, SMS is cheaper per message. Everywhere else, WhatsApp wins on cost.

Post-OTP Marketing Channel

This is the critical differentiator. SMS OTP captures a phone number. WhatsApp OTP captures a phone number AND opens a WhatsApp messaging channel.

After SMS OTP authentication, you can send marketing messages via SMS — but SMS marketing is expensive ($0.01–$0.07 per message), has no rich media support (no images, no buttons, no interactive elements), and is increasingly filtered by carriers.

After WhatsApp OTP authentication, you can send marketing messages via WhatsApp — with rich media (images, video, PDFs), interactive buttons, catalogue links, and location sharing. The cost per message is lower in most markets. The engagement rates are 3–5x higher than SMS.

Guest Perception

Guests perceive SMS messages from unknown numbers as potential spam. "You have an SMS from +1-888-555-0123" doesn't inspire trust. Many guests don't even open SMS messages from unknown numbers.

WhatsApp Business messages arrive with the business name, logo, and verified badge (green checkmark for verified businesses). "You have a WhatsApp message from Cafe Milano" is a different experience. The branding and verification build trust from the first interaction.

The Verdict

Use WhatsApp OTP in markets where WhatsApp penetration exceeds 50%. Use SMS OTP in the US and Canada (where WhatsApp penetration is low and SMS costs are favorable). For international deployments spanning both regions, offer both options on the portal and let the guest choose.

---

Troubleshooting WhatsApp OTP Deployments

"Guests aren't receiving the WhatsApp message"

Check 1: Is the guest's phone number in the correct international format? The platform should auto-detect the country code from the guest's device locale, but manual entry errors (missing country code, extra digits) are the most common cause of delivery failure.

Check 2: Does the guest have WhatsApp installed? WhatsApp OTP requires the WhatsApp app on the guest's device. If the guest doesn't use WhatsApp (common in the US and Japan), the message will fail to deliver. This is why dual-option portals (WhatsApp + email) are recommended in Tier 2 and 3 markets.

Check 3: Is the WhatsApp Business API account in good standing? Meta monitors message quality. If your account's quality rating drops (due to blocks, reports, or low engagement), Meta may impose messaging limits or temporarily restrict the account. Check the quality rating in the WhatsApp Business Manager dashboard.

Check 4: Is the OTP message template still approved? Meta can disapprove previously approved templates if they receive negative feedback. Verify the template status in the Business Manager.

"Capture rate is lower than expected with WhatsApp OTP"

Check 1: Is WhatsApp the primary option on the portal? If WhatsApp OTP is a secondary button below email login, most guests will default to email. Position WhatsApp OTP as the primary (larger button, more prominent placement).

Check 2: Is the market actually WhatsApp-dominant? A portal offering WhatsApp OTP in Tokyo won't perform well regardless of design. Validate the market's WhatsApp penetration before deploying.

Check 3: Is the portal communicating what WhatsApp OTP means? Some guests don't understand "Connect with WhatsApp." Add clarifying text: "We'll send a code to your WhatsApp. It takes 5 seconds."

"Meta rejected my message template"

Common rejection reasons:

• •Template contains promotional language in an authentication template (authentication templates must be utility-only — just the OTP code and a brief, neutral message)
• •Template uses placeholder parameters incorrectly
• •Template doesn't match the declared category (submitted as "utility" but contains marketing language)

Fix: review Meta's template guidelines for the authentication category, revise the template, and resubmit. Approval typically takes 24 hours.

---

Implementation Checklist

For resellers deploying WhatsApp WiFi Login:

Pre-Deployment:

• • Confirm the target market's WhatsApp penetration justifies the investment
• • Enable the WhatsApp OTP add-on on the platform ($99/month)
• • Register or connect a WhatsApp Business Account
• • Submit OTP message template for Meta approval
• • Submit campaign message templates for Meta approval (welcome, follow-up, re-engagement)
• • Configure consent text for the captive portal (GDPR-compliant if applicable)

Portal Configuration:

• • Add WhatsApp OTP as primary authentication method
• • Decide: WhatsApp-only or dual option (WhatsApp + email)?
• • Configure phone number input with auto-detected country code
• • Set up post-login redirect
• • Test the full flow on iOS and Android devices

Campaign Setup:

• • Configure welcome WhatsApp message (sent immediately after first authentication)
• • Configure post-visit follow-up (sent 2 hours after disconnect)
• • Configure re-engagement message (sent after 14 days inactive)
• • Configure birthday message (if birthday data captured)
• • Set up opt-out handling (automatic via WhatsApp block, plus manual STOP keyword)

Monitoring:

• • Track capture rate daily for the first 2 weeks
• • Monitor WhatsApp quality rating in the Business API dashboard
• • Review per-message costs monthly
• • Compare WhatsApp campaign metrics against prior email performance

---

Further Reading

• •WiFi Marketing: The Definitive Guide — Complete WiFi marketing overview
• •Captive Portal Guide — Portal design and authentication methods
• •WhatsApp OTP Captive Portal Setup — Step-by-step technical setup guide
• •WhatsApp Business API for WiFi Resellers — API integration details
• •WhatsApp vs. Email WiFi Capture — Head-to-head comparison
• •WhatsApp Replacing Email Capture — Industry trend analysis
• •WhatsApp WiFi Login: native — white-label story
• •WhatsApp WiFi Marketing Campaigns — Campaign strategy guide
• •WhatsApp WiFi GDPR Consent — GDPR compliance for WhatsApp
• •WhatsApp WiFi Login: Brazil — Brazil market guide
• •WhatsApp WiFi Login: Europe — European deployment guide
• •WhatsApp WiFi Login: Mexico & LATAM — Latin America market guide
• •WhatsApp WiFi Login: Middle East — Middle East deployment guide
• •WhatsApp WiFi Login: Southeast Asia — SEA market guide
• •WiFi Marketing ROI Guide — Calculate WhatsApp OTP ROI
• •White-Label WiFi Guide — Platform evaluation (WhatsApp support as differentiator)
• •GDPR WiFi Data Compliance — Comprehensive GDPR guide