ClickSend is the gateway to look at when you want SMS working this afternoon and you would rather not read a protocol specification to get there. Flat, published pricing, a simple credential pair, and strong coverage in Australia, New Zealand and the UK make it a practical default for sites serving those markets.
Why teams pick ClickSend
- Published, per-country pricing with no negotiation and no minimum commitment.
- Particularly strong routes into Australia, New Zealand and the United Kingdom.
- Prepaid credit, so spend is capped by definition and cannot run away from you.
- A dashboard that a non-developer can actually operate.
What you need before connecting
- A ClickSend account with credit loaded.
- Your ClickSend username and API key, generated in the API credentials area of the dashboard. Use the API key, not your account password.
- A sender ID: a purchased number, or your brand name where alphanumeric senders are permitted.
- For US destinations, a registered 10DLC brand and campaign. See 10DLC registration for WordPress SMS.
Connecting ClickSend to WordPress
- Open the WP SMS gateway settings and choose ClickSend.
- Enter your username and API key.
- Set the sender ID. Australian and UK traffic generally accepts an alphanumeric brand name; US traffic requires a registered number.
- Save and send a test message to a real handset before wiring live triggers to it.
The usual first failure is using the account password instead of the generated API key. The second is an alphanumeric sender on a route that does not allow one. If neither applies, work through the gateway troubleshooting guide.
What you can automate once it is connected
- WooCommerce order and delivery notifications.
- Shipment tracking messages after dispatch.
- Contact Form 7 autoresponders that reply to every enquiry by text.
- OTP login for customer accounts.
- Bulk marketing campaigns to a segmented list.
Where ClickSend fits best
It suits small and mid-sized sites that value predictable pricing and a short setup over squeezing the last fraction of a cent out of each message. At very high volume, providers that negotiate rates will usually beat published pricing, so revisit the decision as your send volume grows.
Prepaid credit is genuinely useful for automated sending: a runaway loop or a misconfigured trigger can only ever burn the balance you have loaded, never an open-ended monthly invoice.
Quick facts
| Credentials needed | Username and API key |
|---|---|
| Billing model | Prepaid credit |
| Alphanumeric sender | Supported in AU, NZ, UK and similar markets |
| Strongest markets | Australia, New Zealand, United Kingdom |
| Best for | Fast setup and predictable pricing |
| Watch out for | Published rates lose to negotiated ones at high volume |
Common questions
Why is my ClickSend connection rejected?
The usual cause is using your account password instead of the API key generated in the dashboard. They are not interchangeable.
Does prepaid credit actually help?
For automated sending, yes. A misconfigured trigger can only ever spend the balance you loaded, rather than running up an open-ended invoice.
Can I send to the US from ClickSend?
Yes, but US traffic still needs a registered number and 10DLC campaign. Alphanumeric sender IDs will not deliver there.
Is it suitable for high volume?
Up to a point. Published flat pricing is convenient, but providers that negotiate rates usually win once you are sending at real scale.
Comparing your options
Browse every supported SMS gateway, or read the Twilio alternatives roundup if you are moving off a pricier provider. If ClickSend is not on your shortlist at all, the custom HTTP gateway connects any provider with an HTTP API.
See WP SMS pricing to get started.