Kudosity (Burst SMS)

Australia's home-grown SMS provider. Best cost, best latency, and native carrier connections for AU and NZ.

Best regions

🇦🇺 Australia · 🇳🇿 New Zealand

Alphanumeric senders

Yes (pre-register)

Inbound / STOP

Provider yes · EziLinks not yet

Cost per AU part

≈ $0.04–$0.06

Why Kudosity

Kudosity (formerly Burst SMS) is an Australian-owned SMS gateway with direct connections into every major AU and NZ mobile carrier. If your recipients are in Australia or New Zealand, Kudosity is almost always the right first choice:

Cheapest AU/NZ rates we've seen from any provider EziLinks supports
Fastest delivery because of on-net Australian carrier peering
Sender IDs are easy — register an alphanumeric brand ID in the Kudosity dashboard, done
Inbound replies land in your Kudosity dashboard so you can monitor STOP requests (EziLinks doesn't consume inbound yet, so opt-outs are a manual step — see below)
Number Insight lookup is bundled — EziLinks uses it to catch invalid numbers before you send

Where it's not the right choice: sending to US, Canada, or lots of European destinations. Kudosity can send there but pricing is less competitive than Twilio (US) or MessageBird / Bird (Europe).

Step 1 — Sign up for a Kudosity account

1 Create an account

Go to kudosity.com and click Sign up. You'll need business ABN details if you're in Australia (required for sender ID compliance).

2 Verify your business

Kudosity performs a light KYC check before enabling sends. This is usually same-day for AU businesses. You may be asked for a driver's licence or ABN certificate.

3 Add credit

Kudosity is pre-paid. Load some credit (minimum ≈ $20 AUD) via credit card or bank transfer. Test sends are cheap so you don't need much to start.

Step 2 — Get your API credentials

1 Log into the Kudosity dashboard

Go to dashboard.kudosity.com and sign in.

2 Navigate to API access

Click your profile icon (top right) → Settings → API. Or use the Developers menu if it's visible in your sidebar.

3 Create an API user

Click + New API user. Give it a name like EziLinks. Kudosity will generate two values: an API Key (public identifier) and an API Secret (secret — only shown once).

4 Copy both values

Copy the API Key and API Secret to a password manager immediately. If you lose the secret you'll need to rotate the key.

Step 3 — Connect Kudosity to EziLinks

1 Open SMS > Providers

In EziLinks, go to SMS in the sidebar, then switch to the Providers tab.

2 Click "+ Connect provider"

Choose Kudosity (Burst SMS) from the Provider dropdown. The credential form expands with two fields (API Key + API Secret) plus the Kudosity-specific sender ID rules alongside.

3 Paste API Key and API Secret

Paste the values from Kudosity. Both fields are required. Optionally give the credential a Label like "My Kudosity account".

4 Enter your rate (optional)

Set the Cost per SMS part (roughly 0.077 AUD for Kudosity's AU rate) and pick AUD. Used only for pre-send cost estimates on the composer. Leave blank if you don't want estimates.

5 Set your default sender ID

Type the alphanumeric brand ID or virtual number you'll be sending as. See the sender ID rules below for what's allowed.

6 Tick Default (optional)

Marks this as the default provider on the composer. If you only have one connected, it's the default automatically.

7 Click Connect

EziLinks encrypts your credentials at rest. The card shows a Not verified pill until you send a test SMS — click Send test SMS on the card, enter your own mobile, and the pill flips to Verified.

Sender ID options

Alphanumeric brand ID (recommended for AU)

Example: EZILINKS. Up to 11 characters, letters and numbers only, no spaces.

Works throughout Australia, New Zealand, UK, Ireland, most of the EU, India, Singapore, and many other markets
Must be pre-registered in Kudosity under Numbers → Alpha Tags. Unregistered senders may get silently rewritten to a shared number by AU carriers, or the send may fail with BAD_CALLER_ID
Recipients see your brand name instead of a phone number, but cannot reply to an alphanumeric sender — use a virtual number if inbound matters
NOT valid for US or Canada — those markets reject alphanumeric SMS entirely

Virtual number

Example: +61485123456. A dedicated mobile or shortcode number allocated to your account.

Rent a dedicated number in the Kudosity dashboard under Numbers. Costs a few dollars per month.
Enables inbound replies — STOP replies arrive in your Kudosity dashboard. EziLinks does not yet consume inbound; you'll need to check Kudosity's inbox and manually opt-out matching contacts in EziLinks (SMS → Contacts → Opt out).
Required for US and Canada, and improves deliverability in some countries.

Blank (shared number pool)

If you leave the sender ID blank, Kudosity uses their default shared number pool. Recipients see a rotating number.

Fine for testing, not recommended for real sends
No inbound reply capture — you can't automate STOP handling reliably
Recipients often flag shared-pool numbers as spam

Register alphanumeric senders BEFORE first use. If you send from EZILINKS without registering it, AU carriers may silently drop or rewrite the message. Register at dashboard.kudosity.com under Numbers → Alpha Tags. Approval for AU is typically minutes to hours.

Delivery report webhook

EziLinks automatically configures a delivery report URL when you send — nothing extra required from you. Kudosity POSTs each status update back to https://app.ezilinks.com/api/sms/webhook/dlr/kudosity with a signed tracking token, and EziLinks correlates it back to the message row in your history.

You don't need to configure anything in the Kudosity dashboard for this to work. If DLRs stop arriving, check your Kudosity dashboard → Logs to see whether Kudosity is actually generating them (it won't for undeliverable numbers, for instance).

Sending a test message

On the Providers tab, click Send test SMS on your Kudosity card
Pick the country and enter your own mobile in local format, or type it with a leading +. The line under the box shows the international number that will actually be sent.
Click Send test
The message should arrive within seconds. Check the History tab — the status will move from queued → sent → delivered as the DLR arrives

Common errors and fixes

Error	What it means	How to fix
`AUTHENTICATION_ERROR`	API Key or Secret is wrong	Double-check both values from the Kudosity dashboard. Rotate the secret if you're unsure; both values appear together in the API user page.
`BAD_CALLER_ID`	Sender ID isn't allocated to your Kudosity account	Register the alphanumeric ID under Numbers → Alpha Tags, or use a Kudosity-allocated virtual number.
`INSUFFICIENT_CREDIT`	Your Kudosity account balance is $0	Top up in the Kudosity dashboard.
`BAD_MOBILE`	Recipient number isn't valid	Kudosity rejected the number. EziLinks validates every number before sending — on import, on save and on send alike — so this usually means a well-formed number that isn't actually a reachable mobile, or one Kudosity can't route to.
`OPTED_OUT`	Recipient previously replied STOP	Their opt-out is respected. If you have valid consent to re-add them, opt them back in from the contact detail page.
Message stuck at `queued`	DLR webhook not reaching EziLinks	Rare with Kudosity because DLR is auto-configured per send. Check firewall isn't blocking outbound from Kudosity's IPs, and confirm your EziLinks base URL is publicly reachable.

Pricing notes

Kudosity publishes real-time rates in the dashboard. As a rough guide (rates change — always confirm in your Kudosity account):

Australia: ~$0.04–$0.06 AUD per part on virtual numbers, slightly cheaper on alphanumeric
New Zealand: ~$0.06–$0.08 AUD per part
UK/EU: ~$0.08–$0.15 AUD per part — MessageBird or Bird is usually cheaper here
US/Canada: ~$0.05–$0.10 AUD per part but with worse deliverability than Twilio — use Twilio for these markets

Volume discounts kick in at 10,000+ messages / month. Contact Kudosity sales for wholesale pricing.

Australian compliance essentials

Kudosity is well-versed in the Australian regulatory environment. A quick reminder of what applies:

Spam Act 2003 — requires consent, sender identification, and an unsubscribe mechanism on every commercial SMS
Consent — explicit (opt-in form, checkbox) or inferred (existing customer within a reasonable timeframe). Keep records for at least two years
Sender identification — the sender ID or the message body must make it clear who's sending. EZILINKS as an alphanumeric sender covers this
Opt-out — every marketing SMS must include a way to stop. Kudosity captures STOP replies in its inbox, but EziLinks does not yet auto-consume that inbox — you must monitor Kudosity's inbox and mark those contacts opted-out inside EziLinks yourself, or include a self-hosted opt-out link in each message
Sending window — only send marketing SMS between 9am and 9pm local time to the recipient. EziLinks' scheduled sends respect the timezone you configure

Two-way conversations: Kudosity itself supports inbound SMS when you use a virtual number as the sender. However, EziLinks does not yet ingest those inbound messages — they only appear in the Kudosity dashboard. Until EziLinks adds inbound, you'll need to check the Kudosity dashboard for replies and act on any STOP requests manually. Compliance with opt-out rules in every country you send to is your responsibility as the sender.