WordPress Plugin

1. What it does

The CloudWave SMS plugin connects your WordPress site to your CloudWave Bulk SMS account. It lets you:

• See your SMS wallet balance and available Sender IDs in wp-admin.
• Send a one-off SMS to pasted numbers, a user role, all users, or all WooCommerce customers.
• Run bulk campaigns, throttled by WP-Cron.
• Automate event SMS: new user, password reset (with the reset link), comment alerts, order receipts and per-status WooCommerce updates, plus staff alerts.
• Keep a delivery log with cost and status.

2. Requirements

• WordPress 5.6+ on PHP 7.4 or newer.
• WooCommerce (optional) for order/status automations. The WordPress automations work without it.
• A CloudWave Bulk SMS account — the portal at https://sms.cloudwavebd.com.
• Funds in your portal SMS wallet (top up under Add Funds).
• Outbound HTTPS from your web host to the portal (most hosts allow this by default).

3. Download

Download the plugin ZIP and install it from your WordPress admin.

cloudwave-WP-plugin.zip

Contains the cloudwave-sms/ plugin folder (WordPress + WooCommerce integrations).

Download ZIP

4. Install & activate

1. UploadIn WordPress go to Plugins → Add New → Upload Plugin, choose cloudwave-WP-plugin.zip and click Install Now.
2. ActivateClick Activate Plugin. Activation creates the {prefix}cw_sms_log and {prefix}cw_sms_queue tables and schedules the two WP-Cron events.
3. Open the pluginA new CloudWave SMS menu appears in the left sidebar. Start on Dashboard.

5. Get your API credentials

1. Open the portalGo to https://sms.cloudwavebd.com and sign in (this uses your WHMCS client login).
2. Create a dedicated keyOpen API & Plugins in the sidebar and click Generate API credentials. Use a separate key for this site so you can revoke it independently.
3. Copy both valuesCopy the API Key (starts with cw_) and the API Secret.
4. Top up if neededUnder Add Funds, add wallet credit (bKash or a WHMCS invoice).

6. Configure the plugin

Go to CloudWave SMS → Settings and fill in the fields below, then click Save.

7. Plugin screens

8. Automations

Enable and reword each event on the Templates screen.

WordPress

The password-reset listener reuses the reset key WordPress just generated, so the SMS link stays valid. Comments are only sent for approved comments, and never to a user about their own comment.

WooCommerce

One customer template exists per order status your store has (pending, processing, on hold, completed, cancelled, refunded, failed — plus any custom statuses). The listener skips the initial empty → pending transition so the receipt is not sent twice.

Merge tags

All templates support {site_name}, {site_url}, {date}, {time}, plus:

Unknown tags are stripped before sending.

9. Sending behaviour

• Up to 500 recipients per API call. Bigger audiences go through the queue.
• Bodies containing merge tags are personalised per recipient and queued one call each. Identical bodies are packed into single multi-recipient calls.
• Failed recipients are retried three times before being parked as failed.
• The opt-out list is checked on every path — automations, manual sends and bulk campaigns alike. Nothing overrides it.
• Messages containing Bangla are sent as Unicode automatically; the send screen shows the encoding and the number of billed parts.

Where phone numbers come from

For each WordPress user, in order:

1. cw_sms_phone user metaWritten automatically the first time a send resolves a number.
2. billing_phone user metaSet by WooCommerce.
3. phone / mobile user metaAs used by many themes.

Only valid Bangladeshi mobile numbers (017…, 8801…, +8801…) are accepted — the value is normalised to 8801XXXXXXXXX before it leaves the site.

10. Cron

WP-Cron drives two jobs:

*/5 * * * * wget -q -O - "https://example.com/wp-cron.php?doing_wp_cron" >/dev/null 2>&1

…or define DISABLE_WP_CRON and call wp-cron.php directly from your system scheduler.

11. Custom events (for developers)

Add your own automation with the cw_sms_events_catalogue filter, then fire it from your code.

add_filter( 'cw_sms_events_catalogue', function ( $events ) {
    $events['my_custom_event'] = array(
        'label'       => 'My Custom Event',
        'group'       => 'staff',
        'target'      => 'staff',
        'description' => 'Fired by my own code.',
        'tags'        => array( '{user_name}' ),
        'default'     => 'Custom alert about {user_name}',
        'enabled'     => 0,
    );

    return $events;
} );

Then trigger it:

CW_SMS_Sender::trigger(
    'my_custom_event',
    array( 'user_name' => 'Rahim' ),
    array( 'user_id'   => $user_id )
);

12. Testing checklist

1. Test API connectionDashboard → shows your live wallet balance and Sender IDs.
2. Send a test SMSDashboard → send to your own mobile, then check the Delivery Log.
3. One-off sendSend SMS → a role or pasted numbers.
4. AutomationTemplates → enable one event (e.g. New User) and trigger it.
5. Bulk campaignSend SMS → bulk form → create a small campaign and confirm it drains on the next cron run.
6. WooCommercePlace a test order and check the receipt / status automation.

13. Troubleshooting

14. Uninstall

• Deactivate (Plugins → Deactivate) stops all sending but preserves settings and data.
• Delete the plugin (Plugins → Delete) runs uninstall.php, which removes the plugin options and both tables.