Messente avatar logo

Delivering every SMS while protecting from spam issues

Margus Sütt

26 Jul 2017 -

5 min read

Margus Sütt

26 Jul 2017

-

2 min read

Our SMS API connects with various software which send requests to deliver messages to millions of devices. Yet as no software is perfect, there have been cases where we have received requests to send an unusual number of messages from one account. Typically, this is a clear signal that a client’s system has a glitch and is sending messages that they did not plan on sending. While our goal is to deliver every SMS, we have a system in place to prevent looped messages from occurring.

Before we get to that, story time. Company X (true story, but the company name is confidential) updated some code in their CRM system, which threw the software into a loop, repeating tasks. Within minutes, the CRM automated the SMS API to send hundreds of thousands of messages to their customers. So, what happens when about 5,000 people suddenly receive 50 messages from the same company in an hour, with the same content? Well, customer complaint calls skyrocket

How does the system delineate between wanted and unwanted SMS requests?

Customer feedback is the most common indicator of something like a CRM system looping. But this means it’s too late –the damage has been done. Although these glitches are rare, a prevention system is valuable. As human error is inevitable and software isn’t perfect, the first logical approach is to come up with a type of filter.

We looked at SMS request patterns, and there is a way to identify a glitch.


Based on these factors, we’ve developed some rules for potential spam or glitch indicators.

The hour countdown starts from the first sent message.

Thus, while we’re always working towards delivering every SMS, we’d like to help as a gatekeeper to keep customers out of trouble. Simple, yet valuable, the spam filter has already helped customers avoid unnecessary costs and customer complaints, while notifying system engineers of potential bugs. And everyone gets this service by default.

The second Payment Services Directive (PSD2) impact: Read the full report.


Margus Sütt

Key account manager

Margus works as a business analyst at Messente. Identifying new opportunities and going deep into industries Margus consults Messente's key customers to help their businesses to advance.




We're here to help you connect with your customers. Let's start talking.

Email again:

Further reading

Startup Conferences: What’s the point? (Slush 2017)

20 Oct 2017

With Slush coming up in about a month, it’s a good time ponder the purpose of...

Yuriy Mikitchenko

2 min read

The economics behind undelivered, failed SMS messages    

17 Oct 2017

The cost and full impact of undelivered or failed messages isn’t immediately clear. The financial impact is not...

Uku Tomikas

2 min read

Fraud and Security: 2FA Considerations for PSD2

10 Oct 2017

The second Payment Services Directive (PSD2) is less than three months away from...

Raili Liiva

2 min read

Tools to avoid breaking the budget with SMS - Part 2

03 Oct 2017

In a previous blog post we discussed a few tools to help avoid breaking the budget...

Uku Tomikas

2 min read