The useful answer is a rate for your actual message, destination and volume—not simply the lowest number on a comparison page. An SMS budget depends on how many billable units your messages use, which customers you contact and the commercial terms agreed with your provider.
For a starting reference, Globe’s published calculator displays an indicative Malaysian list rate of MYR 0.0750 per message and MYR 750 for 10,000 SMS, excluding tax. Globe states that final Malaysian rates are confirmed on quotation. Treat that as a planning example, not a universal market price or a promise that every campaign qualifies. [1]
Start with a transparent calculation
A basic estimate is billable SMS units multiplied by the agreed unit rate, plus applicable taxes and any agreed additional charges. The important word is “billable”: ask what the provider counts and when charging occurs. A number of recipients is not always the same as a number of SMS units.
At the illustrative MYR 0.0750 rate, 1,000 units cost MYR 75, 10,000 units cost MYR 750, and 100,000 units cost MYR 7,500 before tax. These are arithmetic examples using one unchanged rate. They are not volume-tier quotations and should not be read as Globe’s confirmed price at each volume.
Document the assumptions beside your spreadsheet. Write down whether the message is one segment, whether all recipients are in Malaysia, and whether the rate is provisional. This prevents a rough estimate from being reused later as if it were an approved commercial offer.
Why destination changes the estimate
A Malaysian-only audience and a cross-border audience should be priced separately. Do not apply a domestic example to every number in your database. Country coverage, route arrangements and sender requirements need confirmation for each intended destination.
Split your forecast by country before requesting a quote. If you cannot identify destinations confidently, clean the contact data first. A useful brief states the expected volume for each market, rather than supplying one global total and expecting the provider to infer the distribution.
Also distinguish the customer’s current country from the number’s numbering plan. For routing and quotation, the destination number matters. Discuss unusual cases with the provider instead of changing number formats manually and hoping the platform will correct them.
Volume and message purpose matter
Give Globe your likely monthly range and your busiest sending period. A business sending steadily through the month has a different operational pattern from one sending a large campaign immediately before an event. Both the total and the timing help explain what you need.
Separate OTP, transactional and marketing traffic in the brief. A login code, delivery notice and promotional offer have different purposes and urgency. Ask which rate and route apply to each category; do not assume a price advertised for one category includes all others.
Avoid promising an ambitious volume only to obtain a lower quoted rate. Build your forecast from real workflows: expected transactions, reminders per appointment, or campaigns per audience group. Include a conservative scenario so procurement can see the likely spend if activity is below forecast.
Message length can change the unit count
Standard SMS segmentation commonly allows 160 GSM-7 characters in one segment or 70 UCS-2 characters. Concatenated messages typically carry 153 or 67 characters per segment. Emoji, non-Latin text and some punctuation can affect encoding and capacity. [2]
For budgeting, consider a message requiring two billable segments instead of one. At an assumed MYR 0.0750 per segment, 10,000 two-segment messages would represent 20,000 units and MYR 1,500 before tax. Confirm Globe’s actual billing treatment before using this example in a purchase order.
Preview the finished copy, not a shortened draft. Personalisation, a sender prefix or a longer customer name can change the result. Ask for a character and segment check on representative examples, including the longest likely version, so an apparently minor copy change does not surprise finance.
Ask what happens to failed or blocked messages
Globe’s published pricing information says charging is based on operator-confirmed delivery rather than submitted attempts. [1] Still, get the exact definitions in your quotation: what status triggers billing, how delayed reports are reconciled, and how retries or duplicate requests are handled.
Keep the commercial rule separate from your application’s behaviour. A developer retrying an uncertain request may create another message if duplicate protection is absent. Ask how your integration should handle timeouts and status checks. Confirm the implementation with Globe rather than assuming a retry is always harmless.
A delivery report also does not prove a customer read the message. Do not present “cost per read” based only on delivered SMS. If your objective is a completed appointment or account action, measure that outcome separately and explain the attribution assumptions.
Check setup, sender and currency terms
Globe publishes no setup fee and describes Malaysian sender ID registration as free; other markets can have registration charges. [1] Ask what your specific onboarding includes and whether any additional service, integration work or international requirement is outside the standard scope.
Request the quote in the currency your business will pay. If your finance team works in another currency, keep its internal conversion assumption separate from the supplier’s rate. Do not label an exchange-rate calculation as a guaranteed USD or EUR tariff.
Clarify tax, quote validity, payment timing and any minimum commitment. A lower unit price may not be a better fit if the commercial arrangement requires a volume or commitment you cannot support. Compare total expected spend and operational suitability together.
Build a useful quote request
Send a short brief containing destination countries, monthly volume by category, likely peak periods, final sample messages and the preferred sending method. State whether you need a dashboard, API integration or both, and identify the person who will review delivery reports.
Ask for the rate basis, segment treatment, sender setup, billing trigger and applicable tax in writing. Request a worked example using your sample message. This gives procurement and operations the same calculation, rather than two interpretations of a headline price.
Before scaling, run a controlled pilot and compare the forecast with the billable result. Investigate differences in audience size, segment count, failed deliveries and retries. Correct the assumptions while the project is small enough to review carefully.
Reduce waste before chasing a lower rate
Remove duplicate records, suppress contacts that should not receive the campaign, and review outdated numbers. Write concise, useful copy and choose the right audience. These changes improve the communication process even when the quoted rate stays the same.
The aim is a predictable cost for a useful customer interaction. Start with Globe’s pricing calculator for orientation, then request a quotation based on your own sending requirements. A clear rate card and a tested workflow make the monthly bill easier to explain.
Sources
[1] Globe — Published calculator and commercial pricing information ↗
[2] Twilio documentation — SMS character limits and segmentation ↗