Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Need to understand the internal code used in Automatic Reply to Mobile Originated responses using Extended SMPP Connector

Avatar

Level 4

Hi Team,

 

We are looking to understand the internal code used in Automatic Reply to Mobile Originated responses using Extended SMPP Connector. We need this to customize it.

We would like to setup API call to external system to flip do not sms flag as soon as response with specifc message/Code comes from customer. Along with send and remove quarantine we would like to add one more piece of code to do the API calls.

 

Thanks & Regards,

Greeshma

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Greeshma_Sampath1 - last time I looked the External SMPP connector code was baked into the Campaign server code, so its not possible to alter the behaviour of the auto-responder directly. Its also difficult to tell when an auto-response has happened as there are no records to indicate a message was sent, other than the server SMPP logs.

You could try querying the MO responses in the inSMS schema yourself say every 15 or 30 minutes and finding matches that would have generated an auto-response and calling your API from there. Its not real-time, but depending on your legal jurisdiction, marketing opt-outs usually have a grace period before they are expected to be adhered to, so 15-30 minutes should be enough time to set the do not sms flag. You can also indicate that period in your auto-response SMS.

Cheers

Darren

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Hi @Greeshma_Sampath1 - last time I looked the External SMPP connector code was baked into the Campaign server code, so its not possible to alter the behaviour of the auto-responder directly. Its also difficult to tell when an auto-response has happened as there are no records to indicate a message was sent, other than the server SMPP logs.

You could try querying the MO responses in the inSMS schema yourself say every 15 or 30 minutes and finding matches that would have generated an auto-response and calling your API from there. Its not real-time, but depending on your legal jurisdiction, marketing opt-outs usually have a grace period before they are expected to be adhered to, so 15-30 minutes should be enough time to set the do not sms flag. You can also indicate that period in your auto-response SMS.

Cheers

Darren