Mobile Phone Numbers vs ...Not...

Any updates on this, Jamie? I thought I heard someone in a community group mention a tool to run numbers through which will tell you whether they are mobile or not, but I can't remember what it was. I wanted to use something like it before enabling TNEW's mobile opt in so that I was more confident that the numbers already recorded in Tessitura in that phone type are all cell. 

Are you using an SMS integration with Prospect2? 

Any additional insights or thoughts on this are appreciated! 

I'm not sure I'm in any better place to write up strategy overview, but here are some individual facts:

• We went live on crowdEngage (cE), part of the Activity Stream offerings, as of the start of our Dec show. It's an enhanced mobile ticket platform, with the primary delivery method of SMS. Email is also part of it, but somehow SMS feels more primary. There is also an "instant send" aspect to handle quick blasts. It is a transactional product, NOT marketing.
  
  
• cE detects usability of a phone for SMS, and they worked with me to customize which order to go through contact points on records.
  
  
• I learned yesterday that I should be able to trust that *any* number imported into cE means it is a mobile. This is only of middling value though, at least in as far as I've gotten with it so far, because you can only ever see this information as a download per performance, the "Occupancy Report." (There's really no database aspect to it, but you can look up the current set of performances to see what's getting picked up.) I can't see us taking on a data review project based on having to export and merge spreadsheets of individual performances.
  
  
• We're slowly making our way towards doing a data clean up on both email and phone contact points. I'm relatively sure that the majority of this work will just be about inactivating/renaming the Types to be clear indicators of usage, with supporting staff re-training and documentation around this. (e.g. "Second Email" may be replaced by "Payment Contact" or something like that--no one knows what "second email" means but there's a business need to log an extra email onto a record to send an extra copy of an order confirmation to) Within this, on the email side, we'll also pay close attention to the idea of the Primary Checkbox, as that is at the heart of what address actually shows up.
  
  
• The one other thing we've encountered that I expect will make some people lean in is that Merges create double entries, even when it's the same value. This isn't a groundbreaking discovery, but it's a tiny item with some occasional impact. My current evaluation is that it doesn't matter a lot for us on a day to day basis, but it definitely creates a jumble if trying to inspect a record or work with an export that is set to repeat constituents across rows when there are multiple qualifying values. And, it needs more serious consideration in terms of Purposes, but that's a future topic still for me.

I'm not sure I'm in any better place to write up strategy overview, but here are some individual facts:

• We went live on crowdEngage (cE), part of the Activity Stream offerings, as of the start of our Dec show. It's an enhanced mobile ticket platform, with the primary delivery method of SMS. Email is also part of it, but somehow SMS feels more primary. There is also an "instant send" aspect to handle quick blasts. It is a transactional product, NOT marketing.
  
  
• cE detects usability of a phone for SMS, and they worked with me to customize which order to go through contact points on records.
  
  
• I learned yesterday that I should be able to trust that *any* number imported into cE means it is a mobile. This is only of middling value though, at least in as far as I've gotten with it so far, because you can only ever see this information as a download per performance, the "Occupancy Report." (There's really no database aspect to it, but you can look up the current set of performances to see what's getting picked up.) I can't see us taking on a data review project based on having to export and merge spreadsheets of individual performances.
  
  
• We're slowly making our way towards doing a data clean up on both email and phone contact points. I'm relatively sure that the majority of this work will just be about inactivating/renaming the Types to be clear indicators of usage, with supporting staff re-training and documentation around this. (e.g. "Second Email" may be replaced by "Payment Contact" or something like that--no one knows what "second email" means but there's a business need to log an extra email onto a record to send an extra copy of an order confirmation to) Within this, on the email side, we'll also pay close attention to the idea of the Primary Checkbox, as that is at the heart of what address actually shows up.
  
  
• The one other thing we've encountered that I expect will make some people lean in is that Merges create double entries, even when it's the same value. This isn't a groundbreaking discovery, but it's a tiny item with some occasional impact. My current evaluation is that it doesn't matter a lot for us on a day to day basis, but it definitely creates a jumble if trying to inspect a record or work with an export that is set to repeat constituents across rows when there are multiple qualifying values. And, it needs more serious consideration in terms of Purposes, but that's a future topic still for me.