SMS - segment criteria, scheduling to segments, narrow-by-tag options

[BrianJ557]

We signed up for SMS.

Was disappointed to learn that applying selection criteria to the SMS list is not yet functional (the option is there, but grayed-out.) This means that the only organic option is to send SMS messages to the entire SMS list.

There is a jump-through-the-hoop workaround. This requires tagging all your SMS records with an SMS tag. Then use that tag to build your segment. Then export the segment, and re-upload it as a List. You can then use that List for an SMS send. That's a lot of hoops to jump through for functionality that should already be there.

Please let us know when we can apply selection criteria to our SMS lists. Thanks!

[Caitlin_M]

Hi @BrianJ557. We'll need a bit of clarification here to accurately track your feedback.

I pulled up your segments and when viewing your SMS list, I can see all the available criteria. Can you share a screenshot of where you're seeing a greyed-out option? 

[BrianJ557]

No, the problem is, I cannot sub-segment and target my SMS campaigns. I can only send to the broader list of SMS subscribers. I generally do not want to do that, I generally want to send to a portion of that list.

[William_A]

To confirm, you're wanting the ability to send SMS messages directly to segments, rather than having to convert/add the generated segment into a list and send to that?

[BrianJ557]

Segments, or a tag, or combination of tags, just as I can do with email.

The workaround is:

• Build a Segment (or use a Tag)
• Export the Segment or Tag
• Import the Segment or Tag as a List

Even if the option to just select a Segment were there for SMS campaigns that would be a big improvement.

[William_A]

We're updating the status of this idea to more accurately reflect its current status with our engineering team, and also made slight changes to the subject line in order for it to be more easily found. We can't guarantee a commitment to deliver on this feature request, but it should indicate some awareness that we have heard your feedback and could be taken under consideration for a future release.

For future visitors:

If you're interested in development of these ideas, please remember to vote by clicking the thumbs up icon on the original comment (always at the top of the thread), alongside commenting your use case if you have one. Thank you!