Plivo review

Getting Australian SMS access

Plivo does not sell Australian SMS self-serve. Access comes through sales for direct brands. Resellers, multi-brand software vendors and aggregators of unrelated senders are excluded. General Professional credits do not establish Australian SMS evaluation access, so ask sales to confirm any evaluation conditions.

What the commitment covers

The US$1,000 a month amount is a minimum monthly spend across all Plivo products, not a setup or connection fee. A month below the committed amount still bills at the minimum, and pass-through fees such as carrier surcharges sit outside it.

Reading the Australian rate pages

Plivo's public Australian pricing page lists outbound prices by carrier network and a separately charged inbound amount. It lists an SMS-enabled mobile number rental without a currency label. USD column labels in the reporting export establish the SMS usage currency, but not the rental currency. Ask sales for accepted USD charges and the rental currency in writing, then budget in AUD using your own payment and currency costs. The page shows no volume ladder or GST treatment. Card payments attract a gateway fee, the documented bank transfer route is described as avoiding it, and your bank may add separate transfer or currency costs.

Choosing senders and inbound routing

Australia lists two-way SMS and separate numeric and alphanumeric sender IDs. The reply path is an SMS-capable Australian mobile number, with incoming messages sent to its configured Message URL. An alphanumeric header brands the message but works one way, and ACMA guidance says such headers generally cannot receive return messages, so a commercial unsubscribe method must actually work. Your application, not the API, connects replies and delivery callbacks to the right customer record. Registration requirements point to Plivo support, source numbers can be replaced for certain operators, and the SMS Sender ID Register guide covers current Australian branded-sender registration rules.

Checking delivery logs carefully

The console has inbound and outbound SMS logs, status and error filters, and CSV exports, so export required records before log retention expires. Telstra Australia receipts are network-only, so a delivered status there can stop short of the handset, while other networks can be expected to give handset receipts. A delivered status is not a read receipt, and the multichannel API lists a read status that is not an SMS read receipt either.

Running a controlled test

Once sales confirms evaluation conditions, run a small batch across the carrier networks you expect to reach. To count the final SMS template accurately, use a counter on the substituted message and its billed parts, because long or Unicode messages can add billed segments. Compare each route's reported statuses with those caveats.

Support and source limitations

The public service level agreement states that customer issue notification runs through online tickets, and the order form or console identifies the covered support plan. Its separate target-times link redirects to sales, so ask for Australian SMS incident response targets and remedies in writing. The dedicated Slack channel mentioned for Enterprise onboarding is not proof of ongoing Australian incident support. The older Sydney announcement covers voice infrastructure, not SMS latency, local SMS support, or the presence or absence of a current office or entity.

Proceed if sales confirms evaluation access, your expected usage justifies the minimum, and the controlled test passes on key routes. When comparing SMS API requirements across providers, weight the written answers on currency, sender treatment and support targets alongside the rate table. Where those conditions are not met, a self-serve Australian option can suit you better.