inSMS Schema - Attribute 'origin' needs to have + removed at beginning for linking/joining

[hetfidd]

We are on Classic 7 (ACC).

We are implementing SMS for our marketing org.

ACC Recipients table won't save a mobile phone number with a + sign.   It originally was saving it with a 0 and we were able to get past that.   However, that means all phone numbers are submitted through the SMS connector without a + sign (e.g.  +15554443333).  If we manually add a + sign the SMS connector won't take it or process it.  SO mobile phone is stored without a +.   This has been working this way for 4 years and no issue.   All our SMS has been transactional through message center.

For the MARKETING instance though, we need to be able to relate the responses in the inSMS table to a recipient.   The way to do this is through a link to recipient on a field.   The best field to use is ORIGIN in the inSMS table.  Origin stores the mobile phone number.

HOWEVER, the mobile phone is being stored with a + in the Origin field (e.g. +15554443333) and that is the data that comes back from the gateway vendor.

How in the heck can I get that field to remove the + ??.    That is the dilemma.  Been trying compute-string expr to no avail.   Thoughts?  Help?

[Denis_Bozonnet]

Hi @hetfidd 

It is a classic one from SMS providers that they do not accept the + on one end but do send it in the in SMS or the other way round... The only workaround is in the inSMS workflow, you have to remove the + prior saving the record in the inSMS entity or you do it during the reconciliation workflow with recipient.

Ideally you can try to get it remove on the SMS provider side but be ready to do the abvoe workaround..

Thanks

Denis

[akshaaga]

Hi @hetfidd -

You can try using the "replace" function to remove the + sign from the origin field.

Here's an example of how you can use it:

var originWithoutPlusSign = origin.replace(/\+/g, "");

In this example, origin is the string containing the origin field, and the replace function is used to replace all occurrences of the + sign in the string with an empty string (i.e., remove the + sign).

The "g" flag in the regular expression pattern specifies that the replace should happen globally, i.e., replace all occurrences of the + sign in the string.

Once you have the origin field without the + sign, you can use it to link to the recipient record.

[hetfidd]

Hi,

Could you use a compute-string in the element section of a data schema?

[Sukrity_Wadhwa]

Hi @hetfidd,

Were you able to resolve this query with the help of the given solutions or do you still need more help here? Do let us know. In case the given solutions were helpful, then kindly choose the one that helped you the most as the 'Correct Reply'.
Thanks!

[hetfidd · Accepted solution]

No,   We do not have access to server level or factory level changes.  So none of those work.  We have our DBA looking at var originWithoutPlusSign = origin.replace(/\+/g, ""); but he hasn't been able to make it work yet.  So, we have a field service request in to change the inSMS intake on mobile #'s to remove the +.   We are still waiting to hear if they are going to do it or not.  Adobe should extend the inSMS table and put the mobile # in with the + - leave that one alone and add a new field to store the mobile # without the + sign and create a join between the recipient table and inSMS table.  This would probably help everyone doing SMS through adobe campaign.  And if they aren't, maybe that's one of the reasons the tool isn't used.   Did you also know the mobile phone type that is factory set by Adobe puts a 0 in the front of the numbers.  We were able to override that.  But this tool is making it very difficult to implement simple SMS and link everything back to a recipient.

[Sukrity_Wadhwa]

Thanks for the feedback @hetfidd. I will have this conveyed to the Campaign product team for future consideration. 
In the meantime, if you'd like then you can post this as a feature request here.