PV Phone Identity — User Guide

Turn your customers’ phone numbers into a faster, friendlier way to sign in, check out, and stay in the loop — with SMS and WhatsApp built into WordPress and WooCommerce.

Welcome

Passwords get forgotten. Emails end up in spam. Phones are almost always close at hand — and that is exactly what PV Phone Identity puts to work for your store.

Customers can enter their phone number and a one-time code sent by SMS or WhatsApp instead of remembering another username and password. The same verified number can then receive order confirmations, shipping updates, and delivery notices.

Contents

Select any section to jump directly to it.

Install PV Phone Identity like any other WordPress plugin: upload it from Plugins → Add New → Upload Plugin, or place it in your plugins folder, then activate it from the Plugins screen.

After activation, a Phone Identity menu appears in the WordPress dashboard. This becomes the home base for every setting described in this guide.

Your license confirms the purchase and enables automatic updates. Find the key in the purchase confirmation email or under My Licenses in your Plugins Vault account.

If a renewal is missed, your configured sign-in experience continues working. Only automatic updates pause until the license is active again.

General Settings controls where phone authentication appears and how it behaves. Start with the surfaces your customers actually use, then enable only the options your store needs.

PV Phone Identity formats phone numbers for every country your store sells to, including the appropriate flag and calling code. The country list follows your WooCommerce selling settings.

Choose a default country for most customers and pin favorite markets above the rest of the searchable list. Single-country stores can present a fixed calling code instead.

Messaging providers deliver verification codes and order updates. Use Log only while testing so messages are recorded privately without contacting a real phone.

Twilio can handle SMS and WhatsApp from one account. Meta WhatsApp Cloud API connects directly to WhatsApp Business Platform. Country-specific routing can override the default provider for selected markets.

Turn on custom styling to make the phone and OTP interface feel native to your store. The live preview updates as you change colors, fonts, spacing, borders, buttons, links, and feedback messages.

Use the preview to test contrast, readable field labels, clear focus states, and error messages before saving. Reset restores the defaults if you want to start again.

After enabling Order notifications in General Settings, choose which order stages send a message and the channel order used for each stage.

Enable the moments that matter most — order received, payment confirmed, shipped, completed, or another store-specific status. Stages left disabled continue using the normal email behavior.

Rewrite verification, password-reset, and order messages in your own voice. Placeholders insert values such as the customer name or order number when the message is sent.

SMS and WhatsApp can use different wording, and translations can fall back to your default language. For WhatsApp messages sent outside an active conversation, create and approve a matching template in Meta WhatsApp Manager.

The Notification Log shows recent verification codes, password resets, and order updates across every channel, newest first, together with their handoff status.

Log only testing can display the exact demo wording for review. Once a real provider is active, use delivery status while keeping customer message content private.

Phone Identity → WhatsApp provides a dedicated place to test a provider connection and configure delivery receipts for Meta Cloud API.

For delivery receipts, copy the callback URL into Meta, use the same private verify token on both sides, subscribe to the messages webhook field, and store the App Secret only in the protected settings screen.

Phone sign-in appears on the existing login screen. Customers enter a number, request a code, and sign in without learning a new interface or visiting a separate page.

Customers who prefer a saved password can switch to it when password access remains enabled.

Registration, verification, and the first login happen in one sequence. A customer supplies a phone number and password, requests a code, and confirms ownership of the number.

The flow avoids a separate email-confirmation step while preserving the option to collect a backup email later.

From My Account, customers can change their phone number and verify the replacement with a fresh code. If email is optional, they can also add a backup address for codes and one-click login links.

At checkout, the phone number becomes the primary contact value. Email can remain optional or hidden, and customers can opt in to WhatsApp order updates with a single checkbox.