Guides

Choosing an SMS Provider for Your Queue System (Australia)

ClickSend, Twilio, MessageMedia, or your queue vendor's bundled SMS — what actually matters for a walk-in queue in Australia, and where the hidden costs sit.

By ServQueue Team

SMS is the part of a virtual queue customers actually feel. The QR scan is one moment. The "you're up" text is the moment that gets them back to the counter. So picking the wrong SMS provider — too slow, too pricey, or rejecting sender IDs at random — quietly degrades the whole system.

Here's what we look at when an Australian SMB asks which SMS path to use.

The four real options

In practice you'll choose between:

  1. Use your queue vendor's bundled SMS. Most modern systems (ServQueue included) ship with SMS included up to a fair-use limit.
  2. ClickSend — Australian provider, AUD billing, low per-message cost, dashboard built for non-developers.
  3. Twilio — global, USD billing, deepest API, but you pay for that depth in setup time and FX exposure.
  4. MessageMedia / Sinch — enterprise-focused, AU presence, contract sales motion. Strong for high-volume senders, overkill for a salon.

For a single venue under ~2,000 messages a month, bundled SMS is almost always the right answer. The numbers below matter once you outgrow that.

What actually matters (in order)

1. Delivery latency to AU mobiles

A queue SMS is useless if it arrives four minutes after the customer's turn. You want median delivery under ~5 seconds to Telstra / Optus / Vodafone numbers. ClickSend and MessageMedia both have direct AU carrier routes. Twilio routes via international aggregators by default — fine most of the time, occasionally laggy at peak.

2. Sender ID behaviour

Australia allows alphanumeric sender IDs (e.g. "ServQueue") for one-way notifications. Customers trust a named sender far more than a random shortcode. If you need two-way replies (e.g. "reply Y to confirm you're on the way"), you need a long code or shortcode — alphanumeric IDs can't receive replies.

For a queue callback, one-way alphanumeric is fine and is what we recommend.

3. Pricing — AUD, not USD

A standard SMS to AU runs roughly A$0.04–A$0.08 with an AU provider. Twilio quotes USD and adds carrier surcharges, so the effective cost floats with FX. Over a year, an AU-billed provider is both cheaper and more predictable for budgeting.

4. Compliance — the Spam Act 2003

For transactional messages — queue position, "you're next", appointment reminder — you don't need explicit opt-in beyond the customer joining your queue. You still must:

  • Identify the sender clearly (the alphanumeric ID handles this).
  • Not send marketing without separate consent.

A "we're having a 20% off weekend" broadcast to your queue list is a marketing message and needs separate opt-in. Don't mix the two.

5. Per-message segmentation

A standard SMS is 160 GSM-7 characters. Use an emoji or a special character and the encoding flips to UCS-2, which caps at 70 characters. You can send a two-segment SMS, but you pay twice. Keep queue messages short and ASCII-only:

ServQueue: You're next at Joe's Cafe. Please make your way back.

That's one segment. Add an emoji and it becomes two.

When to leave bundled SMS

The bundled-SMS-is-fine rule breaks when:

  • You're sending over ~3,000 messages a month per venue. At that point per-message economics start mattering enough to negotiate directly.
  • You need custom routing rules (different sender IDs per location, for example).
  • You're a chain with central billing and want the SMS line item on its own invoice.

In those cases, plug a ClickSend or MessageMedia account into your queue vendor (ServQueue supports both via API key) and let them bill SMS separately.

What we run on

For Australian customers, ServQueue defaults to ClickSend. AUD billing, direct AU carrier delivery, alphanumeric sender ID out of the box, and the support team answers in your timezone. We've had one outage in the last two years and it was resolved in under thirty minutes.

For Pakistan customers we run on Eocean for the same reasons — local carrier routes, PKR billing, no FX layer.

The short version

  • Under 2,000 SMS / month: use whatever your queue vendor bundles.
  • Above that: pick an AU-billed provider with direct carrier routes.
  • Always: alphanumeric sender ID, one-segment messages, transactional content only on your queue list.

If you'd like to see how the SMS step feels in practice, start a free 7-day trial — your queue will be sending real ClickSend SMS within five minutes of setup. The features and pricing pages have the rest of the detail.

Related reading

Related reading