Insights & practical guides

How to send SMS to Taiwan through an API. Sign up, apply for an API key, check your points balance, send a first message to a +886 number and confirm delivery with callbacks — with cURL, Node.js, Python and PHP code and the error codes you are most likely to meet.

Deliverability rides on sender reputation and list hygiene—not rotating IPs. How IP and domain reputation work, when warm-up matters, when dedicated IPs help, and how monitoring plus broadcast discipline protect your brand.

Publicly documented SMS/smishing patterns in Hong Kong and Taiwan, consumer reporting channels, and how rigorous A2P SMS providers can reduce platform abuse across KYC, content, traffic and sender identity.

Give every department its own EDM account and you get three bills, three sets of SPF/DKIM settings and nobody with the full picture. How to split department lists and campaigns with teams inside one account, share the sending domain and credit pool, and switch on an approval step when you need one. Free trial for companies in Taiwan.

Compliance rarely rejects an SMS purchase over price. It rejects it because nobody can answer five kinds of question — route, identity, evidence, data, operations. A questionnaire financial institutions can send to any SMS vendor as-is, with the risk behind each question explained.

One festival window per month, each with send timing, image subject, copy skeleton (unsubscribe line included) and call-to-action type. MMS templates that retail, F&B, beauty and education businesses can copy and edit, all within the 800×800 and 230KB spec and carrying the unsubscribe and sender details the Unsolicited Electronic Messages Ordinance requires.

What size should an MMS image be? How big can the file be? Can you send a GIF? One article on the carriers' 230KB total payload, the 800×800 pixel limit, how iPhone and Android render differently, Canva and Photoshop export steps, and a pre-upload checklist.

SMS is not "non-forwardable" by default — carrier SMS-forwarding services and one-card-two-number plans will send a one-time password to a different handset. How the non-forwardable route works in Hong Kong, the pre-assigned long numbers carriers use for it, and the extra setup cost and lead time when you want your own # Sender ID on that route.

Gmail, Yahoo and Microsoft score the domain and the IP, not the department that sent the mail. How complaint and bounce rates interact under a shared domain, the usual culprits (sales buying lists, support bulk-sending from Outlook), and five governance steps — one platform, a synced suppression list, subdomain separation, Postmaster monitoring and an approval step.

Pasting 800 addresses into BCC is where most email marketing disasters begin. Sending caps, the Gmail / Yahoo / Microsoft bulk sender rules, the 0.3% complaint threshold, and why sender reputation can only be built slowly.

Why manage EDM, SMS, and WhatsApp on one platform? Unified suppression, cross-channel reporting, drip marketing, and Hong Kong compliance (UEMO, unsubscribe) in practice.

Evaluating Twilio alternatives or a Hong Kong Fintech SMS gateway? API selection for brokerages and banks: deliverability, DLR, routing, compliance, # Sender ID, and reconcilable submit volume.

Compare international messaging APIs for delivery rates in Hong Kong? Test design, DLR reconciliation, grey-route detection, and multi-country compliance — with a practical checklist.

MMS travels over a data connection and bills per message, so it fails in ways SMS never does. How MMS charging actually works, six reasons a message never arrives, and the two ways a business can send it — dashboard or API — with the real spec limits.

How do OTP bombing and SMS pumping (AIT) work? Prelude 2025: 11.83% of verification requests fraudulent. Rate limits, number-range monitoring, route separation, and six UFOSEND-ready controls.