SMS Sender ID Registration for Singapore SMEs: Why Your Texts Say Likely-SCAM

If your company sends texts that show a name such as DPERP or ACMEPTE instead of a mobile number, that name must be registered in Singapore's SMS Sender ID Registry. If it is not, your customer sees the message stamped Likely-SCAM, or depending on the operator and your SMS provider, never sees it at all. Registration is done through the Singapore Network Information Centre using your UEN and Corppass, and it has to be done by your business, not quietly on your behalf by a vendor. Budget a few hundred dollars and two to three weeks, and treat it as the price of keeping a channel your customers already trust.

What actually happens to an unregistered SMS in Singapore?

Nothing dramatic appears in your dashboard. Your SMS provider reports the message as sent, and your staff assume it landed. On the customer's handset, one of three things happens. The message arrives with a Likely-SCAM prefix, which means a delivery notice now reads like a phishing attempt. Or the message is dropped at the operator before it reaches the phone, with no bounce you will notice. Or the customer's own handset filter quietly files it under junk.

The business cost is hidden in all three cases. Missed delivery windows, customers calling the office to ask whether a payment reminder was real, and appointment no-shows that look like indifference rather than a blocked channel. Unlike email, SMS gives you almost no feedback loop, so a broken sender name can cost you months before anyone connects it to a drop in response rate.

Who has to register, and who can skip it?

The rule follows the sender name, not the content. If the sender is an alphanumeric Sender ID, a name in letters, it needs to be registered. This covers one-time passwords, delivery updates, appointment reminders, payment links, service notices and marketing blasts alike. It applies whether you push the messages yourself through an API or your booking system does it for you.

If you text from an ordinary Singapore mobile number, the registry does not apply. Many micro businesses do exactly that, and it works, but you give up the brand name in the sender line and you cannot send at volume. The same exemption does not buy you much goodwill either, because a customer receiving a payment instruction from an unknown mobile number is right to be suspicious.

One trap catches small companies repeatedly. Your SMS provider also has to be a registered participant in the scheme. A cheap overseas gateway that is not a participant cannot deliver your registered Sender ID into Singapore reliably, no matter how correct your own paperwork is.

What does SMS Sender ID registration cost and how long does it take?

There is a one-time registration charge and a recurring annual charge for each Sender ID you hold, and your SMS provider usually adds its own handling fee on top. For a company with one or two sender names, plan on roughly a few hundred dollars to set up and a similar order of magnitude each year to keep. Confirm the current figures with your provider before you commit, because the fee schedule has been revised since the scheme started.

The time cost is more significant than the money. You need your UEN, a Corppass user with authority to transact, evidence that the name belongs to your business, and your provider's participant details. Expect two to three weeks from first form to a working sender name once you include the back and forth. If nobody in your office can log in to Corppass with the right role, that alone can add a week. This is the same single point of failure that bites companies at tax filing time, and it is worth fixing once rather than discovering it at every deadline.

Why do registered messages still land in the junk folder?

Registration stops your Sender ID being flagged as unknown. It does not exempt your content from scam filtering. Operators and handsets both screen message bodies, and the patterns they distrust are exactly the patterns a well-meaning SME uses: a shortened link, urgent language, a request to log in, an unfamiliar domain.

Three changes fix most of it. Send links on your own domain rather than a public URL shortener, so the link text matches the brand in the sender line. Drop the artificial urgency, because act within 2 hours reads as pressure to a filter and to a person. Keep transactional messages and marketing messages on separate Sender IDs, so a promotional campaign that attracts complaints cannot damage the delivery of your one-time passwords.

Does consent still matter once you are registered?

Yes, and it is a separate body of rules. Under the Personal Data Protection Act, marketing messages to Singapore numbers require either clear consent or a check against the Do Not Call Registry, and every marketing message must identify who sent it and offer a way to stop. A registered Sender ID is not consent, and it is no defence if you texted a number on the register.

Transactional messages are treated differently. A delivery notice, an invoice or a one-time password is not marketing, so the Do Not Call rules do not bite. The distinction gets blurred the moment someone adds a promotion to the bottom of a delivery notice, and that single habit converts an exempt message into a marketing one. Keep the two apart in your templates, not just in your intentions.

What should an SME commit to in October 2026?

Work backwards from Chinese New Year. If you intend to send festive promotions, closure notices or pre-holiday order reminders in January 2027, the sender name has to be live before the year-end slowdown, not during it. Registration started in late October comfortably clears that. Started in late December, it does not.

The practical October list is short. Confirm whether your current sender name is registered, and ask your provider in writing rather than assuming. Check that your provider is a scheme participant. Make sure at least two people can act in Corppass. Split transactional and marketing sender names if they are currently the same. Then send a test message to three staff on three different telcos and look at the actual handset, because that is the only place the truth shows up.

Done properly, this is a half-day of admin and a modest annual fee that protects a channel with near universal reach. Left undone, it quietly converts every text you send into something your customers have been trained to ignore.

Frequently asked questions

Can my SMS provider register the Sender ID for me?

Your provider submits and manages the application, but the Sender ID is registered to your business using your UEN, and your authorised person has to approve it. Make sure the registration sits in your company's name. If it is held by an agency or a vendor, you can lose the sender name when you change supplier, along with the recognition you built with it.

We only send one-time passwords, not marketing. Do we still need to register?

Yes. The registry looks at the sender name, not the purpose of the message. One-time passwords are in fact the worst category to leave unregistered, because a login code labelled Likely-SCAM stops customers from completing the exact action you want them to take, and it will generate support calls you never trace back to the cause.

What happens if we ignore this and keep sending?

You do not get a fine in the post. You get a slow and invisible decline: lower response rates, more customers phoning to verify messages, and a brand name sitting next to a scam warning on thousands of handsets. The reputational damage is the penalty, and it accumulates while your reports continue to show messages as delivered.

Digital Perpetual helps Singapore SMEs get their customer communication channels trusted and delivered, from SMS Sender ID and email authentication through to the systems that send the messages. If your texts have started going quiet, that is usually a configuration problem rather than a customer problem.