When you select the option to notify the last sender using email notifications, the SMS magic application refers to the outgoing SMS(SMS history) to check who the last sender was.


Now, SF takes some time to index the data and update the owner from the SMS History which is done according to the SF resource allocations. 
When you receive any incoming SMS, if, the SMS history is not updated, SMS magic will also not be able to update the last sender. Since the OAuth configurations were set by you, you received the incoming SMS notifications for this message(whose data was not indexed) by default.


If you notice for the contact record - Ms. Person's name

.

  • There was SMS sent to Person's name on Date, Time and a reply was received on Date, Time(gap of few minute). Here the last sender was not updated and hence you were selected as the default owner of incoming SMS and hence you received the email notification too.

For other records, the intended last sender of the outgoing message is selected as the owner of the incoming SMS and he/she received the email notification too.


Looking at this, we can say that the SMS Magic features are working fine and the issue is within the SF resource allocations. SF as platform, has certain limitations. All applications, including SMS Magic are bound by those limitations since they are integrated with SF.


If in the near future, you receive an email notification about incoming sms for messages you have not sent, I would request you to run the Find Query(shared below) on the Developer Console in SF immediately.


This will verify whether the data on SMS History is indexed or not.


Find Query - FIND {<enter mobile number of contact record here>} IN ALL FIELDS RETURNING smagicinteract__smsMagic__c(smagicinteract__SMSText__c, smagicinteract__PhoneNumber__c, smagicinteract__Contact__c, id, smagicinteract__CreatedOn__c).