Messavo for WooCommerce

Messavo for WooCommerce connects one or more Android phones directly to a WordPress store. WordPress owns the message queue, immutable recipient and message snapshots, send results and settings. The plugin cannot read or copy the phone’s SMS inbox.

The plugin includes:

• Independent SMS switches and short templates for supported WooCommerce notifications.
• Customer consent controls for classic checkout, Checkout Blocks and account settings.
• International phone-number validation and normalization.
• Preferred phones, ordered fallbacks and per-phone SIM selection.
• An administrator activity log and safe, explicit resend controls.
• Manual SMS sending without inbox or message-history access.
• A documented adapter interface for extension notification types.

SMS automation is off after installation. Account and security notification types remain separate opt-ins. WooCommerce email settings continue to work independently.

Pricing is currently switched off for the temporary free offer, so API and plugin sends have no commercial daily allowance and no subscription is needed. Future pricing is planned but is not active. When pricing is enabled, API and plugin sends will share 100 free messages per phone per day, resetting at 00:00 UTC. Messavo Pro will cost £6.99 per phone/month or £69.99/year and remove this allowance. App and synced-browser sending will remain free. Carrier charges and sending safeguards still apply.

Requirements

• WordPress 6.9 or newer.
• WooCommerce 10.8 or newer.
• PHP 8.3 or newer.
• HTTPS and working WordPress REST API routes.
• A compatible Messavo Android app set as the phone’s default SMS application.

External software and services

The compatible Messavo Android app is required to send SMS through an Android phone. The app connects to this plugin’s authenticated REST API on the store’s own WordPress server. When sending, the phone downloads the queued recipient and message snapshot and returns the send result. This plugin has no inbox-upload capability. A Messavo Cloud account is not required, and the direct connection does not send message content to Messavo Cloud.

Messages sent to recipients pass through the phone’s mobile carrier, which receives the destination number and message content needed to deliver the SMS. Carrier charges, limits, delivery reporting and terms may apply. The phone may delay background polling because of Android battery restrictions.

App information and installation help: https://messavo.cloud/help

Messavo privacy policy: https://messavo.cloud/privacy

Messavo terms: https://messavo.cloud/terms

Acceptable use policy: https://messavo.cloud/acceptable-use

Privacy

The plugin processes phone numbers, outgoing SMS content, notification consent records, delivery state and device activity needed for the features an administrator enables. It does not request or accept the phone’s inbox or message history. When upgrading from a version that supported optional inbox synchronization, the WordPress-stored inbox copy is deleted without changing messages on the phone.

Site owners are responsible for providing required privacy notices, recording valid consent, honoring opt-outs and deletion requests, and following carrier rules and applicable law. Do not enable automated messaging for recipients who have not consented.

Source and third-party libraries

The distributed ZIP contains the readable plugin source and its locked Composer dependencies. Dependency versions and source references are recorded in composer.lock and THIRD-PARTY-NOTICES.txt.

The readable browser QR bundle is from the MIT-licensed qrcode project. Its public source is available at https://github.com/soldair/node-qrcode and its license is included in assets/qrcode-LICENSE.txt. The bundle runs locally in the administrator’s browser; it is not loaded from a CDN.