Twilio Verify Alphanumeric OTP: Singapore Rules - Zian AI

Twilio Verify Alphanumeric OTP: Singapore Rules

Quick answer: Yes, with conditions. As at 2 November 2026, Twilio Verify sends OTPs to Singapore from an alphanumeric sender in one of three ways: your own SGNIC-registered sender ID, Twilio’s shared “TWVerify” ID (KYC-approved accounts, brandless templates only), or “Likely-SCAM”, which Twilio warns can be blocked without notice. Infobip needs a registered ID too, or its OTP-only “BipSMS” sender for direct clients without a Singapore UEN (360 EUR set-up plus 15 EUR a month).

This page covers one-time passcodes (OTPs) sent by SMS to +65 mobile numbers through Twilio Verify, Twilio Programmable Messaging and Infobip’s 2FA API. The rules come from the Singapore Network Information Centre (SGNIC), which runs the SMS Sender ID Registry (SSIR) for the Infocomm Media Development Authority (IMDA); the vendor facts come from Twilio’s and Infobip’s own documentation and price pages, all read on 2 November 2026. If your Singapore messages are already failing, start with our Twilio error 30007 triage for Singapore SSIR and Infobip. This page covers the earlier choice: which sender your OTP goes out under, and what it costs.

Where Zian fits when OTPs and sales follow-up share a phone number

Zian is the conversation after verification, not the OTP: it is an AI sales and reception agents platform that answers inbound calls 24/7 as an AI receptionist and follows up by voice, SMS, email, WhatsApp, Instagram DMs and Facebook Messenger. This page makes no OTP or verification claims about Zian; the Singapore rule it carries into Zian-style SMS follow-up is that a shared OTP sender cannot carry sales text.

That rule comes from the vendors’ own terms. Twilio restricts TWVerify to brandless verification templates, and Infobip allows only the OTP templates listed in your BipSMS LOA, so a team that verifies Singapore sign-ups through either shared sender still needs its own registered sender before any agent sends a booking reminder. Twilio also says alphanumeric sender IDs are “only available for one-way outbound messages,” so two-way conversations need a registered Singapore domestic long code. Zian’s SmartReach AI™ orchestrates message, channel and timing by country, industry and profile, with intelligent follow-up pacing, and its agents connect to HubSpot, Salesforce, HighLevel and Zapier. The sender registration stays with your organisation: SGNIC requires a UEN, and IMDA’s 2022 decision says the registrant “must therefore have full control over the use of the Sender IDs”. Australia’s comparable regime is covered in our guide to Australia’s mandatory SMS Sender ID Register.

Does Twilio Verify support alphanumeric OTP messages in Singapore?

It does, but you do not fully choose the sender. Twilio’s Singapore Sender ID Handling page says that when Verify (and the older Authy API) sends SMS to Singapore, it “will use one of five different Alphanumeric Sender IDs and message template combinations, depending on several customer-specific criteria and the time period.” Two are history; three describe today.

  • Combinations 1 and 2 (before 26 January 2023). Verify sent as “TWVerify” or “verify”, or as an unregistered custom name such as “ACME”, with any template. Accounts on either that never registered their own ID were moved to combination 4 on 26 January 2023 if KYC-approved, or to combination 5 on 30 January 2023 if not.
  • Combination 3, your registered sender ID with any template. Twilio “strongly recommend[s] this option” but notes it “may not be feasible for some customers as registering a Sender ID in Singapore requires obtaining a Singapore UEN first.”
  • Combination 4, “TWVerify” with brandless templates only. For customers without their own registered ID who pass Twilio’s Know Your Customer (KYC) check, Verify uses “TWVerify” as “a shared Sender ID that Twilio owns.” The message is restricted to brandless text such as “Your verification code is: XXXXXX”, in six listed locales (English, Mandarin, German, Spanish, French and Italian). Other locales default to English, and the PSD2 option is not supported.
  • Combination 5, “Likely-SCAM” with any template. Everyone who fits neither 3 nor 4 gets “Likely-SCAM” as the sender, and Twilio says these messages “also run the risk of being blocked entirely, without notice, from being sent to Singapore.”

The TWVerify KYC check has one main criterion, per the same page: the customer “has an approved Business Profile in Twilio’s Trust Hub” for the Verify account, after which you file a request form; a sub-account can rely on its parent’s profile. Twilio “reserves the right to modify its KYC process, including retroactively.”

Twilio’s own pages disagree on whether your brand matters. The Singapore page says: “we have observed that not including the brand (friendly_name) in the message and using TWVerify as the Sender ID does not result in a lower OTP conversion rate,” because “End-users are requesting the OTP message, so they are expecting it.” Twilio’s Verify Countries and Regions Deliverability page says, in general terms: “Twilio Verify provides generic senders on behalf of our customers. To increase the conversion rate of your messages, register your own Alphanumeric Sender ID” in countries that require pre-registration, and Twilio’s alphanumeric sender ID country table lists Singapore as registration required. Only your own A/B data can settle which holds for your traffic.

In Singapore, Twilio Verify picks your OTP’s sender from your registration and KYC status, not from the “From” you want.

What happens to an OTP sent to a +65 number, by sender type

Built from the vendors’ and SGNIC’s own pages. Find your setup; “Arrives as” is what the recipient’s phone shows as the sender.

Your setup Arrives as Template limits What it takes Source
Twilio Verify, your sender ID registered with SGNIC and Twilio Your sender ID Any Verify template Singapore UEN (yours, or a Singapore affiliate’s that authorises you by LOA); SGNIC registration (about 19 calendar days); Twilio Console application (5 business days provisioning) Twilio Verify Singapore page (combination 3); SGNIC FAQ; Twilio SG guidelines
Twilio Verify, no registered ID, Trust Hub Business Profile approved and request form filed TWVerify Brandless templates only, six locales; PSD2 option not supported No UEN needed; approved Business Profile plus Twilio’s request form Twilio Verify Singapore page (combination 4)
Twilio Verify, no registered ID, no KYC approval Likely-SCAM Any template Nothing; Twilio warns of blocking “without notice” Twilio Verify Singapore page (combination 5)
Twilio Verify, custom “From” name you never registered Not your name: falls back to TWVerify or Likely-SCAM As for combination 4 or 5 Register it, or accept the fallback Twilio Verify Singapore page (combination 2)
Twilio Programmable Messaging (your own OTP code), registered alphanumeric ID Your sender ID; one-way only, no replies or STOP Your own text, within Twilio’s Singapore content rules UEN, SGNIC, Twilio Console application Twilio SG guidelines; Twilio Alphanumeric Sender ID article
Twilio Programmable Messaging, unregistered alphanumeric ID Likely-SCAM (Twilio’s table marks the sender ID as not preserved) Your own text Nothing; not recommended Twilio SG guidelines
Any Twilio send from an international long code (+1, +44 and so on) Likely-SCAM Not applicable Cannot be fixed: international long codes “can’t be registered with SGNIC and Twilio” Twilio SG guidelines
Twilio, registered Singapore domestic long code (8 or 9 series) The long code; two-way A2P only: person-to-person traffic over it “is not allowed” SGNIC registration in 10-digit form, then Twilio registration Twilio SG guidelines; SGNIC Rules of Registration
Short code to Singapore through Twilio or Infobip Not available Not applicable Twilio lists short codes as “Not Supported”; Infobip’s coverage table lists Singapore short code senders as “No” Twilio SG guidelines; Infobip SMS coverage
Infobip 2FA API, sender ID registered with SGNIC and safelisted by Infobip Your sender ID Your 2FA message templates UEN; SGNIC registration naming Infobip; “live” screenshot to your account manager; 14-day sender registration duration Infobip SG LOA guide; Infobip SMS coverage
Infobip, direct client with no Singapore UEN BipSMS (shared) Only the OTP templates listed in your LOA LOA; 360 EUR one-time set-up plus 15 EUR a month; wholesalers and resellers not eligible Infobip SG LOA guide
Infobip, unregistered sender ID Infobip’s pages differ: “Only registered Sender IDs are permitted” (coverage table) versus labelled “Likely-SCAM” (LOA guide); status 11 REJECTED_SOURCE if your account accepts only registered IDs Not applicable Register the ID Infobip SMS coverage; Infobip SG LOA guide; Infobip status codes
Registered sender ID sent through an aggregator that is not in the SSIR Blocked Not applicable Use only Participating Aggregators (Twilio and Infobip are both listed) SGNIC FAQ; SGNIC Participating Aggregators list
A sender ID that is literally “OTP” or “SMS” Cannot be registered Not applicable Choose a non-generic 3 to 11 character ID SGNIC Rules of Registration

The table reduces to one rule, which we call the UEN fork. If you hold a Singapore UEN, register your own sender ID; it works on both vendors with any template. If you do not, and no Singapore subsidiary or branch of your group will register the ID and authorise you by Letter of Authorisation (LOA) to send under it, the only SMS routes on these two vendors that avoid “Likely-SCAM” or a block are TWVerify on Twilio and BipSMS on Infobip, and both are limited to verification text.

A Unique Entity Number (UEN) is issued by the relevant Singapore government agency: Singapore’s Accounting and Corporate Regulatory Authority (ACRA) for companies, while charities, societies and religious bodies get theirs from the agencies that register them. SGNIC says a foreign business can get one by registering a local subsidiary or a foreign branch office with ACRA, and that the Singapore entity can then issue an LOA authorising the group’s other overseas offices to send under its registered sender IDs; Infobip’s LOA guide likewise accepts an affiliate of the brand owner. SGNIC’s FAQ adds a check that matters for shared senders in particular: “If users are relying on service providers to send SMS and the SMS is sent using the Sender ID of the service providers, users should also check if their service providers have registered the Sender ID with the SSIR.”

How does Infobip compare for Singapore OTPs?

Infobip’s developer product is the 2FA API, which “enables you to generate PINs, or passcodes, that can be delivered by SMS, Voice, or Email.” You create an application (PIN attempts, PIN time to live, per-number send limits), then a message template holding the PIN placeholder and a senderId; each send request can also carry a from value. In Infobip’s documentation the sender is a field you set, and Singapore’s registry decides whether it is carried.

Infobip’s SMS coverage table entry for Singapore, as at 2 November 2026: alphanumeric senders supported; short code senders not supported; registration required, with “Register Sender IDs with SGNIC and provide Infobip a confirmation screenshot as proof. Only registered Sender IDs are permitted since 31 January 2023”; sender registration duration 14 days; 2-way SMS supported; and “All customers must complete and pay for SGNIC registration (Infobip can’t do this on Customer behalf).” Gambling traffic is “only OTP allowed”. (We read this table through Infobip’s published Markdown export, because the HTML page renders client-side.)

Infobip’s Singapore LOA guidelines say registration with SGNIC is required “before you can send traffic to the Infobip platform,” and “Failure to do so will result in the Sender IDs being labeled as ‘Likely-SCAM.’” So one Infobip page says unregistered IDs are not permitted and another says they are labelled; we print both because Infobip publishes both. On accounts set to registered-only senders, Infobip’s status-code reference gives a clear signal: status 11, REJECTED_SOURCE, “Your account is set to accept only registered sender IDs, and the sender ID defined in the request has not been registered on your account.”

For senders without a UEN, the LOA guide describes the BipSMS generic sender, which Infobip shares “with our international direct clients that do not have UEN”. Conditions: direct clients only (“Wholesales/resellers are not allowed to register”), an LOA before any traffic, 360 EUR one-time plus 15 EUR a month, and “only templates listed in the LOA will be allowed.”

Above the 2FA API sits Infobip Authenticate, an omnichannel OTP product “with multistep failover” whose page lists SMS, voice, Viber, RCS, silent mobile verification, WhatsApp and email. Its calls to action are “Contact an expert” and “Contact us”; it shows no price, though it says its optimised routing lets you “only pay for what gets delivered.”

Question Twilio Verify Infobip 2FA API
Who picks the Singapore sender? Verify, from your registration and KYC status (five combinations) You, in the template’s senderId or the request’s from; Singapore rules decide if it is carried
Route with no Singapore UEN TWVerify: approved Trust Hub Business Profile plus request form; brandless templates BipSMS: direct clients only, LOA, OTP templates listed in the LOA, 360 EUR plus 15 EUR a month
Provider step after SGNIC Console application; 5 business days provisioning Screenshot of “live” SSIR status to your account manager; 14-day sender registration duration
Channels in the base API SMS, voice, email, WhatsApp (own sender), RCS, push, TOTP, Silent Network Auth SMS, voice, email (Authenticate adds WhatsApp, RCS, Viber and silent verification)
Published price model $0.05 per successful verification plus channel fees Per-message SMS price; we could not find a published per-verification fee
Both on SGNIC’s Participating Aggregator list? Yes: Twilio Singapore Pte Ltd Yes: Infobip Mobile Services Pte Ltd

We found no Singapore OTP delivery or conversion rates from either vendor to compare, so this page does not rank them. What decides a build is who controls the sender, what you can do without a UEN, and how you pay.

What 10,000 Singapore OTP verifications cost on each route

All prices below are list prices in US dollars, read on 2 November 2026. Twilio’s Verify pricing page charges “$0.05 per successful verification plus standard channel fees.” Failed, expired or uncompleted verifications do not attract the $0.05, but for SMS “Message attempts are always charged and not subject to delivery.” The Verify page quotes only the US SMS fee and points to international pricing, so we used Twilio’s Singapore SMS price of $0.0591 per outbound segment from an alphanumeric sender ID as the channel fee. That page warns that “Prices may change from time to time without notice and additional carrier fees may apply.”

Infobip’s SMS pricing page shows Singapore at $0.0472 per message (€0.04082). Infobip calls this “the average price across all supported networks for each country,” and says per-network pricing is in its Portal and the exact price “may vary based on the destination country, network and applicable discounts.” The figure renders in the browser; we read it from the data the page ships, through the page’s own formatting script (stored value divided by 100). We could not find a published per-verification fee for Infobip’s 2FA API or Authenticate on its pricing, SMS 2FA, SMS OTP, Authenticate or 2FA documentation pages, as at 2 November 2026.

Two scenarios. In A, every successful verification takes exactly one single-segment SMS (10,000 messages). In B, we assume 1.25 sends per success to cover resends and abandoned attempts (12,500 messages). The 1.25 is our assumption, not a vendor figure; replace it with your own ratio.

Route Per-verification fee SMS cost, A (10,000 SMS) Total, A SMS cost, B (12,500 SMS) Total, B
Twilio Verify over SMS 10,000 × $0.05 = $500.00 10,000 × $0.0591 = $591.00 $1,091.00 12,500 × $0.0591 = $738.75 $1,238.75
Twilio Programmable Messaging, your own codes None $591.00 $591.00 $738.75 $738.75
Same, plus Twilio’s SMS pumping protection at $0.025 per message None $591.00 + $250.00 $841.00 $738.75 + $312.50 $1,051.25
Infobip 2FA API over SMS None published that we could find 10,000 × $0.0472 = $472.00 $472.00 12,500 × $0.0472 = $590.00 $590.00

Per successful verification in scenario A, that is about $0.109 on Twilio Verify, $0.059 on Programmable Messaging and $0.047 on Infobip’s average SMS price. The rows do not buy the same thing: Twilio says the Verify fee includes “passcode generation, localized template translation across 42 languages, configurable TTL expiration, rate limiting, and automated SMS pumping protection via Verify Fraud Guard.” With Programmable Messaging you build the code logic yourself; Infobip’s 2FA API also generates and checks PINs.

Fixed costs sit on top, and they depend on your branch of the UEN fork:

  • Your own sender ID (either vendor): SGNIC charges S$545 once for the account and S$218 a year per sender ID, both including GST, so S$763 in the first year for one ID.
  • BipSMS (Infobip, no UEN): 360 EUR plus 12 × 15 EUR = 540 EUR in the first year.
  • TWVerify (Twilio, no UEN): we could not find a separate fee on Twilio’s Singapore Sender ID Handling page or its Verify pricing page.
  • Failed messages on Twilio: a $0.001 processing fee per message that ends in a “Failed” status.

At volume, Twilio says custom Verify pricing “is typically evaluated when monthly usage reaches 100,000+ verifications or combined messaging spends trigger enterprise thresholds,” and Infobip says it offers “discounts for enterprises who want to send large volumes.”

Sending AI follow-up into Singapore once a lead has verified? Zian AI is in partnership-application beta. Its agents answer inbound calls 24/7 and follow up by SMS, WhatsApp, email and voice in 30+ languages. Apply For Partnership

Is “Likely-SCAM” still a label in Singapore, or a block?

The record points two ways. As at 2 November 2026, SGNIC’s SSIR overview still says “All non-registered Sender IDs will be marked as ‘Likely-SCAM’.” IMDA’s decision of 14 October 2022 said the thread “will stay open for around 6 months from the start of the Full SSIR Regime” and that after that, unregistered sender IDs “will be blocked.” That decision requires senders to “Register Sender IDs with the SSIR” and “Only use Aggregators that participate in the SSIR”; it does not cover person-to-person SMS. Twilio’s Verify page warns of blocking “without notice”, so plan as if combination 5 delivers nothing. Our 30007 guide sets out the full record.

Fallback channels when SMS to Singapore is not an option

If you are on the “Likely-SCAM” branch, waiting for registration, or want a second channel:

  • Twilio Verify WhatsApp. Twilio says that, effective 1 March 2024, “you must bring your own brand and phone number (Sender) to send WhatsApp OTP messages.” Its Verify Channel Selection page says a WhatsApp verification “Will fallback to SMS (if SMS channel is enabled)” by default. In our reading, that fallback SMS is still subject to the Singapore sender rules above. Twilio’s Verify pricing page gives two US WhatsApp fees: $0.0034 per authentication template in its channel table and $0.0147 in its FAQ.
  • Twilio Verify voice, email and TOTP. Twilio’s channel table lists voice and email at “$0.05 per successful verification,” with links to its Voice and Email pricing, and says the TOTP (authenticator app) channel fee “is included in the verification fee.” Voice attempts are “always charged and not subject to delivery.” None of these uses an SMS sender ID, which is what the SSIR registers.
  • Twilio RCS. Verify’s RCS Upgrade is enabled by default and moves an SMS OTP to RCS where the handset supports it; RCS falls back to SMS.
  • Infobip. The 2FA API offers SMS, voice and email. Authenticate adds WhatsApp, RCS, Viber and silent mobile verification with failover, with no price on its product page.

For AI phone agents that need to verify a caller rather than a sign-up, our five-rung caller verification ladder for AI phone agents compares an SMS one-time code with the other checks a voice agent can run.

Which route should you choose for Singapore OTPs?

  1. You have a Singapore UEN, or a Singapore subsidiary or branch that will register the ID and authorise you by LOA. Register your own non-generic sender ID with SGNIC (S$763 in year one), then with your provider: about 19 calendar days at SGNIC, then 5 business days at Twilio or Infobip’s stated 14-day duration. Any template works.
  2. You have no UEN and already use Twilio. Get a Trust Hub Business Profile approved and file Twilio’s TWVerify request form. Accept brandless text in six locales, and test Twilio’s two conversion claims on your own traffic.
  3. You have no UEN and are an Infobip direct client. BipSMS, with an LOA listing your OTP templates (360 EUR plus 15 EUR a month).
  4. You have no UEN and no KYC approval. Do not send SMS OTPs to +65 numbers. Use WhatsApp with your own sender, voice, email or TOTP until one of the routes above is in place.
  5. Whichever route you choose: keep sales and service SMS on a separate, registered sender, and send only through Participating Aggregators, including any failover provider.

For calls to +65 numbers, our comparison of voice API reliability across India, Singapore and Australia covers caller ID rules.

Running sales conversations in registered-sender markets? Zian AI is in partnership-application beta. Apply For Partnership

Frequently asked questions

Does Twilio Verify support alphanumeric sender IDs for OTPs in Singapore?

Yes. As at 2 November 2026, Twilio’s Singapore Sender ID Handling page says Verify sends Singapore SMS from your own SGNIC-registered sender ID, from Twilio’s shared “TWVerify” ID if you pass its KYC check, or from “Likely-SCAM”, which Twilio says risks being blocked without notice. An unregistered custom name is no longer honoured.

What is TWVerify and how do I get it?

TWVerify is a shared Singapore sender ID that Twilio owns. Twilio uses it for Verify customers who have not registered their own sender ID and pass its KYC check, whose main criterion is an approved Trust Hub Business Profile, followed by a request form. Messages are limited to brandless templates such as “Your verification code is: XXXXXX”.

Why do my Twilio Verify OTPs arrive from “Likely-SCAM”?

Your account has neither a registered Singapore sender ID nor TWVerify approval, so Verify falls back to “Likely-SCAM”. SGNIC marks all non-registered sender IDs that way. Register your own ID through SGNIC and Twilio, or get a Trust Hub Business Profile approved and request TWVerify.

How do Infobip and Twilio Verify compare on cost for Singapore OTPs?

On list prices read on 2 November 2026, 10,000 successful SMS verifications at one message each cost $1,091 on Twilio Verify ($0.05 per verification plus $0.0591 per SMS) and $472 at Infobip’s average Singapore SMS price of $0.0472. We found no published Infobip per-verification fee. Verify’s fee includes code generation and Fraud Guard.

Can I send OTPs to Singapore without a Singapore UEN?

Yes, through a shared sender, or under the registered sender ID of your group’s Singapore subsidiary or branch, with its Letter of Authorisation. Twilio Verify customers can use TWVerify after Trust Hub approval and a request form. Infobip direct clients with no UEN can use BipSMS, with an LOA listing their OTP templates, for 360 EUR set-up plus 15 EUR a month. Resellers and wholesalers cannot use BipSMS.

Can I register “OTP” as my sender ID in Singapore?

No. SGNIC’s SSIR Rules of Registration say alphanumeric sender IDs should not be generic in nature, and give “OTP” and “SMS” as examples. An alphanumeric ID should have 3 to 11 characters, no non-Latin characters, no leading or trailing spaces and only the special characters SGNIC lists, and must not be sensitive in nature or suggest a link to the Singapore Government, statutory bodies or regulatory authorities.

Can an AI sales agent reuse the TWVerify or BipSMS sender for follow-up texts?

No. Twilio restricts TWVerify to brandless verification templates, and Infobip allows only the OTP templates listed in your BipSMS LOA. Follow-up needs your own registered sender. Twilio says alphanumeric IDs are one-way, so two-way conversations need a registered Singapore domestic long code.

Where every figure on this page comes from

Figure Who published it Link Date read
Five Singapore sender/template combinations; TWVerify brandless templates in six locales; 26 and 30 January 2023 cut-overs; Trust Hub KYC criterion; “Likely-SCAM” blocking risk; conversion statement Twilio Singapore Sender ID Handling 2 November 2026
“Register your own Alphanumeric Sender ID” to increase conversion Twilio Verify Countries and Regions Deliverability 2 November 2026
$0.05 per successful verification; channel fee rules; US WhatsApp $0.0034 and $0.0147; 42 languages; custom pricing at 100,000+ verifications a month Twilio Verify pricing 2 November 2026
$0.0591 per outbound SMS segment (alphanumeric); SMS pumping protection $0.025; $0.001 failed-message fee Twilio SMS pricing, Singapore 2 November 2026
5 business days provisioning; Likely-SCAM overwrite from 30 January 2023; international long codes cannot be registered; short codes not supported; P2P over registered long codes not allowed Twilio Singapore SMS guidelines 2 November 2026
Singapore “Yes – Registration Required” Twilio International Support for Alphanumeric Sender ID 2 November 2026
Alphanumeric sender IDs one-way only Twilio Alphanumeric Sender ID for Programmable SMS 2 November 2026
WhatsApp OTP own sender from 1 March 2024 Twilio Verify WhatsApp 2 November 2026
WhatsApp falls back to SMS by default; RCS Upgrade on by default Twilio Verify Channel Selection 2 November 2026
Singapore: sender registration required; 14-day registration duration; short codes “No”; 2-way “Yes”; “Only registered Sender IDs are permitted since 31 January 2023” Infobip SMS coverage and connectivity 2 November 2026
BipSMS: 360 EUR one-time, 15 EUR monthly, direct clients only, OTP templates in the LOA; unregistered IDs labelled “Likely-SCAM” Infobip Singapore LOA guidelines 2 November 2026
Singapore SMS $0.0472 (€0.04082) per message, average across networks Infobip SMS pricing 2 November 2026
2FA API channels: SMS, voice, email Infobip 2FA API 2 November 2026
Status 11 REJECTED_SOURCE Infobip Response status and error codes 2 November 2026
S$545 account set-up and S$218 per sender ID per year, incl. GST; non-registered IDs marked “Likely-SCAM” from 31 January 2023 SGNIC SSIR overview 2 November 2026
About 19 calendar days to protection; non-participating aggregators blocked; check service providers’ sender IDs SGNIC SSIR FAQ 2 November 2026
3 to 11 characters; “OTP” and “SMS” too generic; 10-digit long virtual numbers from the 8 and 9 series SGNIC Rules of Registration 2 November 2026
Twilio Singapore Pte Ltd and Infobip Mobile Services Pte Ltd listed as Participating Aggregators SGNIC List of Participating Aggregators 2 November 2026
Decision of 14 October 2022; “Likely-SCAM” thread for around 6 months, then blocking; two duties for senders IMDA Decision on Full SSIR Regime (PDF) 2 November 2026
Scenario B’s 1.25 sends per successful verification; all totals in the cost table Zian (our assumption and arithmetic) This page 2 November 2026

Related Blogs

Related from Zian AI