Link SMS reply to respective delivery

[SachinDhir]

Is there any way to link SMS reply to respective delivery if we are sending multiple deliveries to same customer within short period of time like transaction message?

[LaurentLam]

You can check here:
Send, monitor and track SMS | Adobe Campaign

-> linkedSmsId

But carefull, there is no "easy" way to be 100% sure for a response to be linked to the outgoing SMS as this depends from the SMS provider arbitrary rules. That's not coming from Adobe Campaign it self but about the amount of phone number to reply to a SMS in order to identify the answer.

=> usually it is based on a time frame + the phone number used for the delivery by the SMS provider

[Darren_Bowers]

Hey @LaurentLam - I have never seen linkedSmsId populated, even when using 2-way SMS with responses from Campaigns.

Is there any documentation on how to get this working? Is there a workflow that does the broadLogId matching?

Genuinely curious.

Cheers Darren

[SachinDhir]

Totally agree with @darren below.

[LaurentLam]

That depends of the SMS provider. This field was populated through the netSize connector if I'm correct. In your case, I'm afraid that you do not have the choice to discuss with your sms provider in order to be able to create arbitrary rules on your side. At the beginning this table was created to keep a trace from the optout through the keyword "STOP". It was not designed to retrieve different behavior of message regarding a delivery context

[Darren_Bowers]

Thanks @LaurentLam - I thought it might be a custom connector attribute. I don't believe normal SMPP connectors carry any IDs to link the MT and MO messages that I am aware of. We are building a custom broadLog matching workflow to attempt to do this using mobile number. Thanks Darren

[kapilKochar · Accepted solution]

Hi Sachin, 

There is a field in inSMS schema call linkedSmsId.  you can use this field to set broadlogId. Since it's not auto populated so for this you can create one tech Workflow which links incoming SMS with originating broadlogs. 

This workflow runs as delta and picks all data from inSMS as first query and then you can add enrichment with rcpbroadlogs join conditions based on extAccountid and messagetype. This will be 1:N, to restrict the output to 1 use data collected as Limit the count in properties and filter based on address=(origin) and sort by eventDate desc. 

After enrichment you will have latets records for that origin from rcpbroadlog and pass broadlogsID to next activity which will update inSMS table and column linkedSmsId. 

Thanks,

Kapil

[SachinDhir]

Hi @kapil, I totally understood the approach but the point it what if customer recieve multiple SMS? The approach relies on assumption customer should not get another SMS until he replies or previous question is expires/no more validate.