In July we released a new feature to the Twilio SMS Application optimizing how incoming SMS messages are handled. Our application will now check incoming unknown phone numbers against your Contact database. If a match is found the corresponding CDO record for the incoming message will be mapped to the matching Eloqua Contact. Incoming messages with no matching Eloqua Contacts will continue to be written to the CDO and will remain unmapped.
We have identified and designed this feature to assist users who are expecting Contacts to text in to a Twilio short code or long code when opting in to messaging or initiating a workflow. This feature is available today and does not require any changes or updates to your current configurations
Mapping Incoming Messages to Eloqua Contacts
When incoming contacts text into a Twilio phone number linked to your Sureshot account, the application will attempt to match incoming text messages to an Eloqua contact.
- If an Eloqua contact has previously been sent a message from the app, Sureshot will match the incoming message to the same contact.
- If there is no message history for the incoming phone number, Sureshot will search Eloqua for a matching phone number in the Eloqua contact field designated in step four of the configuration wizard.
- If no matching contact is found in Eloqua, the incoming message will be recorded in the CDO with no mapped contact.
Supported phone number formats for Contact data in Eloqua include: