Twilio Error 30007 in Singapore: SSIR and Infobip

Quick answer: Since 31 January 2023, an unregistered sender ID in Singapore has been relabelled “Likely-SCAM” rather than failed, as SGNIC still describes it on 6 October 2026 (Infobip permits only registered IDs; Twilio’s Verify docs warn such messages risk being blocked). So Twilio error 30007 (filtered) points at content first: Twilio bans WhatsApp and LINE chat links and nine content categories there. Then check routing and exact case.

This is a Singapore-only diagnosis for application-to-person (A2P) SMS to +65 numbers through Twilio or Infobip, including AI SMS agents. It uses primary pages only, all read on 6 October 2026: the Singapore Network Information Centre (SGNIC), which runs the SSIR; the Infocomm Media Development Authority (IMDA); Twilio’s Singapore guidelines and error documentation; and Infobip’s Singapore registration guide, SMS coverage page and status-code reference. For US numbers, see our guide to AI SMS carrier filtering and error 30007.

Why are my Twilio SMS messages to Singapore failing with error 30007?

Twilio’s error 30007 page says the message “was filtered (blocked) by Twilio or by the carrier”. Twilio filters for breaches of its Messaging Policy or Acceptable Use Policy. Carriers filter “to block abusive traffic, as well as to enforce rules or regulations about what types of messaging are allowed to that country or mobile network.” The page lists two possible causes and no others: Twilio’s filter identified the message as spam or unwanted, or a wireless carrier flagged it as objectionable.

Many teams assume the cause is the sender ID registry. That is usually the wrong first guess. The SGNIC SSIR overview says that under the Full SSIR Regime, from 31 January 2023, organisations using alpha, numeric or alphanumeric sender IDs to message Singapore mobile users “must first register the Sender IDs via the SSIR portal. All non-registered Sender IDs will be marked as ‘Likely-SCAM’.” The message is marked, not dropped. Twilio’s Singapore SMS guidelines say the same thing from the sender’s side: non-registered sender IDs are “overwritten with Alphanumeric Sender ID ‘Likely-SCAM’” (Twilio dates this from 30 January 2023; SGNIC and IMDA say 31 January).

That gives you the most useful test on this page. If the recipient sees your message under “Likely-SCAM”, you have a registration problem. If Twilio marks the message undelivered with 30007, you have a filtering problem, and Singapore’s content rules are the first place to look.

Three published facts cut against keeping those two apart too neatly. First, Twilio’s International Support for Alphanumeric Sender ID article lists Singapore as “Yes – Registration Required”. It warns that in such countries “delivery quality may be lower or delivery may be disallowed” for messages from a standard Twilio phone number, “as carriers in these countries often impose carrier filtering on non-registered message traffic.” So an unregistered sender can be filtered as well as relabelled. Second, SGNIC’s FAQ names two registry cases that end in a block rather than a label. Third, Infobip says only registered sender IDs are permitted, and Twilio’s Verify docs warn that “Likely-SCAM” messages risk being blocked (both covered below). The handset test is the fastest first split, but it does not settle every case.

What does Twilio block in Singapore that it allows elsewhere?

The compliance section of Twilio’s Singapore guidelines makes two statements that matter most for 30007. Both were read on 6 October 2026.

• Nine prohibited content categories. “Sending firearms, gambling, adult content, money/loan, political, religious, controlled substance, cannabis, and alcohol related content is strictly prohibited.” Money/loan sits on that list, so a lending follow-up is in a banned category however carefully it is worded.
• No chat-app links. “Messages containing WhatsApp/LINE chat links are not allowed.” This matters a great deal for AI agents. A common design hands an SMS lead over to WhatsApp with a wa.me link, and in Singapore that single link is enough to get the message filtered.

The same page adds that delivery to M2M numbers is “on best effort basis only”, that messages are 160 ASCII characters per segment, and that MMS is “converted to SMS with embedded URL”. Its best practices: opt-in consent, daytime sending unless urgent, HELP and STOP in the local language, and no contact with numbers on do-not-call or do-not-disturb registries.

Twilio’s How Does Message Filtering Work? article explains what the code can and cannot tell you. When Twilio knows a message was filtered, the status becomes Undelivered with error 30007 and your status callback receives it. But “it is not always possible to know for certain when a message has been filtered by a carrier”, and in rare cases carriers report a filtered message as delivered. Filtered messages “are still billed”. An AI agent that retries a filtered follow-up pays for every retry.

The Singapore 30007 triage table: symptom, cause, check, fix

Work down the rows in order. Each cause is quoted from the provider’s or regulator’s own page; where we infer, the cell says so.

Symptom	Likely cause	Check that tells the causes apart	Fix on Twilio	Fix on Infobip
Twilio status Undelivered, error 30007; body contains a wa.me or LINE link	Twilio’s Singapore rule: WhatsApp/LINE chat links are not allowed	Resend the same body without the link to one consenting test handset	Remove chat-app links from Singapore templates and from the agent’s allowed outputs	Infobip’s SMS coverage page answers “Yes” to “Content With URLs Allowed” for Singapore and its prohibited topics do not name chat-app links; test before relying on that (our note, not Infobip’s)
30007 on messages about loans, alcohol, gambling or another listed topic	One of Twilio’s nine prohibited Singapore categories	Do the 30007s cluster on one topic or template?	Remove the use case from Singapore traffic; rewording does not lift a category ban	Infobip’s SMS coverage page lists its own Singapore prohibited topics (regulatory, phishing, gambling, other scams, delivery phishing) and adds that adult content and promotional loan traffic are forbidden and gambling is OTP only; operator spam rejections arrive as error 607 EC_REJECTED_SPAM_BY_OPERATOR
30007 spread across ordinary, on-topic messages	Twilio’s or a carrier’s spam filtering (content, volume, complaints)	Collect 3 or more Message SIDs that are undelivered with 30007	If you believe the traffic is compliant, send those SIDs to Twilio Support, as both 30007 articles instruct	Status 4 UNDELIVERABLE_REJECTED_OPERATOR: Infobip’s resolution step is to contact Support
Recipient sees “Likely-SCAM”; message delivered	Sender ID not registered with SSIR, or not yet whitelisted	Log in to the SSIR portal: status must show “Live” with an “Effective By” date that has passed	Register at SGNIC, then file the Twilio Console application with proof	Register at SGNIC naming Infobip as aggregator, then send the “live” screenshot to your account manager
“Likely-SCAM” although you registered	Case mismatch: SGNIC treats “PineApple” and “PineAPPLE” as different IDs	Compare the From value your code sends against the registry entry character by character	Send the exact registered string, or set a registered Default Sender ID so Twilio overwrites a non-matching From	Send the exact registered string
“Likely-SCAM” on traffic from a +1 or other non-Singapore number	Twilio: international long codes are always overwritten and “can’t be registered with SGNIC and Twilio”	Check which sender the agent actually used in the message log	Move Singapore traffic to a registered alphanumeric ID or a registered Singapore long code	Use a sender registered with SSIR
Some customers do not receive messages from a registered ID	Registered ID routed through an aggregator that is not in the SSIR. SGNIC: such messages “will be blocked”	Is every route in your stack (including fallbacks) on SGNIC’s list of Participating Aggregators?	Twilio Singapore Pte Ltd is on the list (number 48 of 51)	Infobip Mobile Services Pte Ltd is on the list (number 19 of 51)
Registered with SGNIC; messages refused or still labelled	Aggregator-side registration incomplete. SGNIC says this has led aggregators to disallow sending or convert to “Likely-SCAM”	Is your Twilio application “Completed”, or has Infobip confirmed the safelisting?	Twilio application with ACRA BizFile (no more than 3 months old), SSIR proof and Letter of Authorisation	Account-manager confirmation; wholesale partners also send the LOA
Infobip status 11 REJECTED_SOURCE	Infobip: “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”	Is the sender in the request one registered on that Infobip account?	Not applicable	Register the ID on the account, or send from one that is
Infobip REJECTED_FLOODING_FILTER	Infobip’s default anti-flooding limit: one number receives at most 20 varied and 6 identical messages per hour	Count messages per destination per hour in the agent’s send log	Not applicable (this is an Infobip limit)	Pace follow-ups and deduplicate retries; Infobip says the limit can be extended per account on request to your account manager or Support

The table supports one rule. A 30007 in Singapore is a content and policy question until the handset shows “Likely-SCAM”. Once it does, it is a registration question.

What the SSIR actually requires, and the six registry checks SGNIC publishes

IMDA’s decision of 14 October 2022 sets two duties on organisations that send SMS with sender IDs to Singapore mobile users: register the sender IDs with the SSIR, and “only use Aggregators that participate in the SSIR.” The regime covers A2P SMS from local and overseas senders and the telecommunication operators’ own sender IDs. It does not apply to person-to-person traffic. Registration needs a Singapore Unique Entity Number (UEN). A foreign business can get one by registering a local subsidiary or a foreign branch office with ACRA. Merchant aggregators, law firms and secretarial firms cannot register sender IDs for use by third-party organisations.

SGNIC’s Rules of Registration set the format. An alphanumeric sender ID should have 3 to 11 characters, contain no non-Latin characters and no leading or trailing spaces, and use only the special characters listed in the Annex. Any mix of upper and lower case is allowed. The ID should not be generic (the rules give “OTP” and “SMS” as examples), not be sensitive, and not suggest a link to the Singapore Government, statutory bodies, regulatory authorities or agencies, national controlling bodies or national movements. Short codes can be registered only if they are 5 digits starting with 7, unique to the organisation, and shown by supporting documents to have been issued by a Singapore mobile network operator to your aggregator. Long virtual numbers must be assigned by a Singapore mobile network operator and sent by a Participating Aggregator, come from the 8 or 9 series, be unique to the organisation and backed by supporting documents, and be registered in 10-digit form (65 followed by 8 digits). SIM card numbers are not accepted. One more line on the Participating Aggregators page matters if your sender ID uses symbols: not all aggregators “may support Sender IDs that contain special characters (e.g., ?, @, *, #).”

When registered senders still fail, SGNIC’s FAQ lists six things to check. All six appear in the triage table above, and here they are in SGNIC’s order:

1. Whitelisting must be in effect. Sending while the status is pending converts the message to “Likely-SCAM”.
2. Sender IDs are case sensitive. Sending a different case from the registered one results in the SMS being “blocked or converted to ‘Likely-SCAM’”.
3. Every sender ID you use must be whitelisted. This includes IDs your service providers send under.
4. Use only Participating Aggregators. Whitelisted sender IDs sent through non-participating aggregators “will be blocked”.
5. Complete the aggregator’s own checks. Users who did not finish them have been prevented from sending or converted to “Likely-SCAM”.
6. Send a test SMS first.

Check 4 matters most for AI SMS stacks: a platform that fails over between SMS providers is safe in Singapore only if every provider in the chain is a Participating Aggregator. The list read on 6 October 2026 has 51 names.

Is “Likely-SCAM” still a label, or are unregistered IDs now blocked?

The published record points two ways, so here are both. IMDA’s 2022 decision described “Likely-SCAM” as a transition measure. It said the thread “will stay open for around 6 months from the start of the Full SSIR Regime”, and that “thereafter it will be closed and all SMS with Sender IDs that are still not registered by then will be blocked.” As at 6 October 2026, though, SGNIC’s overview and FAQ pages still say non-registered sender IDs “will be marked as ‘Likely-SCAM’”. IMDA’s Anti-Scam Measures page (last updated 15 May 2026) describes its SMS measures as “blocking malicious content and labelling unfamiliar sender IDs”. Twilio’s Singapore guidelines and Infobip’s Singapore registration guide also describe a label, not a block, although Infobip’s SMS coverage page says “Only registered Sender IDs are permitted since 31 January 2023.”

We could not find an IMDA document announcing that the six-month transition was extended. Some aggregators’ help pages say it was, but those are secondary sources and we have not relied on them. What can be said safely is this: as at 6 October 2026, the regulator’s registry operator describes the treatment of an unregistered ID as a label. Twilio’s Singapore Sender ID Handling page for its Verify product goes further: messages sent as “Likely-SCAM” “also run the risk of being blocked entirely, without notice, from being sent to Singapore.” On Infobip, plan as if an unregistered ID will not be carried at all; on Twilio, plan as if it may not be. Treat the label as a delivery failure anyway. A message that reaches a phone in a thread named “Likely-SCAM” has, for sales purposes, not been delivered.

Twilio’s Likely-SCAM article explains why teams miss the label: before July 2025, logs recorded your original From value, and the article says logs will show “Likely-SCAM” for Singapore “at a later date”. We could not confirm whether that change has shipped as at 6 October 2026, so a clean From column is not proof the label is absent. Ask a test recipient what they see.

Twilio vs Infobip for Singapore SMS: what differs when something fails

Both companies are SSIR Participating Aggregators, and the regulatory requirement is the same on both: register with SGNIC first, then with the provider. What differs is the provider’s own registration step and its stated registration time, the routes it offers to a sender without a UEN, and the codes it uses to report failures.

Question	Twilio (Singapore pages, read 6 October 2026)	Infobip (Singapore pages, read 6 October 2026)
On SGNIC’s Participating Aggregator list?	Yes: Twilio Singapore Pte Ltd	Yes: Infobip Mobile Services Pte Ltd
Provider step after SGNIC	Console application: ACRA BizFile no more than 3 months old, SSIR proof screenshot, Letter of Authorisation	Direct customers send the SSIR “live” screenshot to their account manager; wholesale partners also send the LOA
Provider’s stated provisioning time, alphanumeric	5 business days	Sender registration duration of 14 days (Infobip’s SMS coverage page, Singapore entry)
Dynamic (unregistered) alphanumeric IDs	Not supported; pre-registration required	Registration required “before you can send traffic to the Infobip platform”; the coverage page adds “Only registered Sender IDs are permitted since 31 January 2023”
Sender without a Singapore UEN	Programmable Messaging: register under your own UEN, or use an LOA from the UEN holder. Twilio Verify (OTP only): shared “TWVerify” sender with brandless templates for customers who have not registered their own sender ID and pass Twilio’s KYC check (main criterion: an approved Trust Hub Business Profile, followed by a request form to Twilio), per Twilio’s Singapore Sender ID Handling page	“BipSMS” generic sender: direct clients with no UEN, OTP traffic only, LOA with listed templates, 360 EUR set-up plus 15 EUR a month
Two-way conversations	Alphanumeric IDs are “one-way outbound” only; Singapore domestic long codes are supported but must be registered with SGNIC and Twilio, and person-to-person messages over them are “not allowed”	Supported: Infobip’s SMS coverage page lists 2-way SMS for Singapore as “Yes”
How a filtered message is reported	Status Undelivered, error 30007	Error 607 EC_REJECTED_SPAM_BY_OPERATOR; status 4 UNDELIVERABLE_REJECTED_OPERATOR
How an unregistered sender is reported	Delivered under “Likely-SCAM”; Twilio’s Verify page warns such messages “run the risk of being blocked entirely, without notice”	Status 11 REJECTED_SOURCE when the account accepts only registered sender IDs
Short codes	Not supported by Twilio in Singapore	Not supported: Infobip’s SMS coverage page lists Singapore short code senders as “No”

The practical difference for diagnosis is this. Infobip reports an unregistered sender as a rejection, status 11, where the account is set to accept only registered IDs, so the failure shows up in Infobip’s own status data. On Twilio, an unregistered sender is relabelled downstream, so the evidence sits on the recipient’s handset. This page has no Singapore delivery-rate data for either provider and does not claim one is better. Both list two-way SMS as supported in Singapore, so choose on whether you hold a UEN, how quickly you need a sender live, and how your engineers prefer failures to surface.

How long registration takes, and what it costs: a worked example

SGNIC’s FAQ says that, from account registration to the start of protection, the process “typically takes approximately 19 calendar days” if the documents are right and payments are prompt. Approved sender IDs are passed to Participating Aggregators “on a weekly basis”. After that, Twilio lists 5 business days of provisioning for a Singapore alphanumeric ID. One sender ID added from scratch, worst case run back to back:

Step	Who	Time	Cost (SGD, incl. GST)
Create SSIR account (UEN, Corppass, admin user, name your aggregator)	SGNIC	About 19 calendar days in total, per SGNIC	S$545 one-time set-up
Register the sender ID; pay within 30 calendar days of acceptance	SGNIC		S$218 per sender ID per year
Provider registration (Twilio Console application)	Twilio	5 business days (up to 7 calendar days)	Not stated on Twilio’s Singapore guidelines page
Provider registration (Infobip, instead of Twilio)	Infobip	14 days, the sender registration duration on Infobip’s SMS coverage page	Not stated on that page
Total, one sender ID, first year		About 26 calendar days on Twilio (19 + 7); about 33 on Infobip (19 + 14)	S$763 (545 + 218)

Each extra sender ID adds S$218 a year, so two IDs cost S$981 in the first year (545 + 218 + 218). SGNIC’s fees include GST. IMDA’s 2022 decision and Infobip’s page quote $500 and $200, which are the same fees before 9% GST (500 × 1.09 = 545; 200 × 1.09 = 218). SGNIC says payments are non-refundable and a registration cannot be edited once paid. Get the exact case and spelling right before you pay. Renewal is not automatic: if you do not pay by the last day of the validity period, the ID “will be automatically removed”, and anyone can then register it first-come-first-served.

For a launch on Twilio, start about four weeks before the first send. On Infobip, plan on about five weeks: SGNIC’s 19 days plus Infobip’s stated sender registration duration of 14 days, which follows the SGNIC step (Infobip asks for the SSIR status as a registration document). If you are already sending and the handset shows “Likely-SCAM”, every message until registration is live goes into that thread.

What changes when an AI agent is the one writing the SMS

An agent that writes each message, picks the channel and paces follow-ups runs into these rules in four predictable ways. This is our reading of the rules, not something Twilio or Infobip say about AI.

• Channel hand-offs. An agent told to “move the lead to WhatsApp” produces a wa.me link, which Twilio’s Singapore rules forbid. On a two-way sender, use a reply prompt instead and keep links out of the body.
• Replies on a one-way sender. On Twilio, an alphanumeric ID cannot receive replies or STOP, so you must give another way to opt out. For two-way conversations, use a registered Singapore long code and keep it to A2P traffic.
• Sender drift. An agent that picks its own From value, or falls back to a pooled +1 number, sends some traffic as “Likely-SCAM” unnoticed. Fix the sender per country in code; on Twilio, a registered Default Sender ID overwrites a non-matching From.
• Follow-up pressure. Infobip’s default flooding filter (20 varied or 6 identical messages per destination per hour) is easy to hit with a retry loop. Twilio bills filtered messages. Both reward an agent that waits before it sends again.

Zian’s SMS agents work on the last point by design: SmartReach AI™ orchestrates message, channel and timing by country, industry and profile, with intelligent follow-up pacing. The registration itself is still yours: SGNIC requires a UEN to register, and IMDA’s decision says the registrant must have full control over the ID, so a merchant aggregator, law firm or secretarial firm cannot register it for your use. Our breakdown of Australia’s SMS Sender ID Register covers the closest equivalent regime, and what to do in the first 24 hours of a Twilio account suspension covers the account-level failure that a run of filtered messages can lead to.

Running AI outreach into Singapore and other registered-sender markets? Zian AI is in partnership-application beta. Its phone, SMS, email and WhatsApp agents work in 30+ languages and connect to HubSpot, Salesforce, HighLevel and Zapier.

Apply For Partnership

Frequently asked questions

Where every figure on this page comes from

Figure	Who published it	Link	Date read
Full SSIR Regime from 31 January 2023; non-registered IDs marked “Likely-SCAM”; S$545 set-up and S$218 per ID per year, incl. GST	SGNIC	SSIR overview	6 October 2026
About 19 calendar days to protection; weekly conveyance to aggregators; six delivery checks; 30-day payment window; non-refundable	SGNIC	SSIR FAQ	6 October 2026
51 Participating Aggregators; Twilio number 48, Infobip number 19	SGNIC	List of Participating Aggregators	6 October 2026
Sender ID 3 to 11 characters; short codes 5 digits starting with 7; 10-digit LVN format	SGNIC	Rules of Registration	6 October 2026
Decision dated 14 October 2022; “Likely-SCAM” thread for around 6 months, then blocking; $500 and $200 before GST	IMDA	Decision on Full SSIR Regime (PDF)	6 October 2026
IMDA Anti-Scam Measures page last updated 15 May 2026; “labelling unfamiliar sender IDs”	IMDA	Anti-Scam Measures	6 October 2026
Nine prohibited categories; WhatsApp/LINE links banned; 30 January 2023 overwrite date; 5 business days provisioning; 160 ASCII characters per segment	Twilio	Singapore SMS guidelines	6 October 2026
30007 definition; 3 or more Message SIDs to Support	Twilio	Error 30007	6 October 2026
Filtered messages billed; status Undelivered with 30007	Twilio	How Does Message Filtering Work?	6 October 2026
Logs show original From before July 2025; Singapore change “at a later date”	Twilio	Why are my messages being sent from Likely-SCAM?	6 October 2026
BizFile report no more than 3 months old; 10-digit LVN format for Twilio	Twilio	Register your Alphanumeric Sender ID in Singapore	6 October 2026
Shared “TWVerify” sender and brandless templates for Verify OTP where the customer has no registered sender ID and passes Twilio’s KYC check (main criterion: an approved Trust Hub Business Profile) and submits Twilio’s request form; “Likely-SCAM” messages risk being blocked without notice	Twilio	Singapore Sender ID Handling (Verify)	6 October 2026
Alphanumeric IDs one-way only; Default Sender ID overwrite	Twilio	Alphanumeric Sender ID for Programmable SMS	6 October 2026
Singapore “Yes – Registration Required”; carriers often filter non-registered traffic	Twilio	International Support for Alphanumeric Sender ID	6 October 2026
BipSMS: OTP only, 360 EUR set-up, 15 EUR a month; Infobip UEN 201413192R; $500 and $200 fees	Infobip	Singapore LOA guidelines	6 October 2026
Singapore entry: sender registration duration 14 days; 2-way SMS supported; short code senders not supported; “Only registered Sender IDs are permitted since 31 January 2023”; prohibited topics regulatory, phishing, gambling, other scams and delivery phishing; adult content and promotional loan traffic forbidden, gambling OTP only	Infobip	SMS coverage and connectivity	6 October 2026
Status 11 REJECTED_SOURCE; status 4; error 607; flooding filter 20 varied and 6 identical per hour	Infobip	Response status and error codes	6 October 2026
About 26 days (Twilio) or about 33 days (Infobip), and S$763 (one ID) or S$981 (two IDs) in year one	Zian AI calculation from the SGNIC and Twilio rows above	This page, worked example	6 October 2026

Sending AI-led outreach across countries with different sender rules? Zian AI’s agents run phone, SMS, email and WhatsApp outreach with SmartReach AI™ pacing and PrecisionPitch AI™ split-testing. They are available now through the partnership-application beta.

Apply For Partnership