Getting Spam Messages on my Inbound Long Code/Sender ID

Unfortunately, scam messages are a growing concern for many people, and stopping them can be quite challenging. Scammers are constantly evolving their tactics, using techniques like purchasing phone number lists or cycling through blocks of numbers, which makes it hard to block their messages effectively. 

Even if you have an unlisted phone number, there's no guarantee that you won't receive random scams and spam messages.

This guide provides you with suggestions on how one can detect and filter out the inevitable spam messages you may receive on their Inbound Enabled Sender ID/Long Codes

Filtering out Incoming Spam Messages

Adding a reference tag

While using the endpoint Tall Bob API V2, provide a value for the ‘reference’ tag. This would help us in tracking the incoming messages as that tag gets returned using the Webhook Webhook Formats.

Using a Campaign ID

Currently, the ‘Campaign ID’ tag gets returned with an empty value as it is not being used while sending the campaign.

While using the endpoint Tall Bob API V2, you could additionally add a ‘campaign ID' tag and provide a value for the tag. This would help us in tracking the incoming messages as that tag gets returned using the Webhook Webhook Formats.

Exceptions

Keep in mind that this sort of filtering will only work for situations where your inbound number is not being used as an initial point of contact or call to action, for example, if you had a print advertisement with the message ‘info' to 0400 abc xyz then its likely neither a reference tag or campaign ID will be present,