3223739 - Multiple SMS Activities are created when a failed SMS attempt is followed by a successful attempt

• In the Activities Work Center, SMS messages sent which failed are not logged
• The customer is unable to tell if an SMS message has failed or not
• If an SMS message is sent and then fails, there is no activity created at that time, however, as soon as another message is successfully sent, the system will capture two activities 

• SAP Cloud for Customer
• SAP Cloud for Sales
• SAP Cloud for Service 

1. Open a C4C ticket
2. Go to the Timeline tab
3. Click SMS, screen opens to type SMS
4. Select the SMS channel
5. Enter To Mobile number (without country code to make it fail)
6. Compose a SMS and click send
7. Check the timeline and the "Messaging Activities" (notice that no activity was created)
8. Repeat above steps (from step 5) again, using the correct "To" number with country code.
9. Check the timeline and the Messaging Activities" - notice that 2 Messaging Activity are created, one for SMS sent to number without country code, another SMS sent to number with country code.

• Technical limitation
• By default, messaging activities are not created for failed messages
• Per standard, the messaging activity is created when the SMS is successfully sent
• If both attempts happened in same session, without closing the feeder, multiple activity creation occurs
• Since the previous failed data still remains in buffer, it will also be saved along with the correct data, therefore creating two successful activities

To prevent such scenarios (multiple activity creation), the user must close the feeder (exit the ticket), and try again using the correct data.

• 3221714 - The Messaging Activity does not display the "To" or "Mobile" number
• 2356282 - Outbound SMS Error "The gateway returned an error while sending the message HTTP Code 400."

Messaging, SMS, tickets, duplicates, multiple, SMS Channel , KBA , LOD-CRM-SRP , Service Request Processing , LOD-CRM-SRP-INT , Ticket Interactions , Problem