Fix the Notifications Triggering for Initial Inbound Flowroute SMS when Customer's SMS CID does not match any Open Tickets - Leads Creation but no Notifications

We've discovered a major issue with Notifications regarding this particular integration!

FYI: Inbound SMS through Flowroute gets stuck as a lead and does not auto convert to a ticket, despite the "Convert Leads to Tickets" option being enabled inside the Admin section. This happens even if "Enable Leads" is disabled at the account level.

What's even worse is that the Inbound SMS via the Flowroute Callback URL is treated differently inside the Repairshopr system than a regular SMS message being sent to the 425-xxx-xxxx Repairshopr standard outbound CID number.

This incoming Flowroute SMS triggers absolutely NO notifications, despite all trigger requirements being met. This is a major issue because unless you're looking at the leads icon in the dashboard and constantly refreshing the page you'll never know that your clients or prospects are sending text messages to your company phone number.

Beware; It's an awesome integration, but don't think you can enable this integration and expect to be notified when clients are texting your DID flowroute number--you won't be... not yet

If the inbound SMS Sender's CID number matches a customer AND a ticket is already open inside the system, the notifications and appends happen as they should. This post is about the first initial inbound SMS when the Sender's CID doesn't match any already open tickets.

Updates welcome...