Is this not being considered? Really obvious feature to implement

Spintax is becoming an expected feature in most email and text platforms. Don't fall behind High Level - continue to dominate!

In the meantime until/if this makes it to dev, you can create a workaround to accomplish the same thing using a triggered workflow SPLIT block and distribute Random Split paths, each with 20% random distribution and use the SMS variations as the next action on each of the 5 splits. If you need more than 5, just add another split of 5 from each of the first 5, giving you 25 options (each option == 4%). [see workflow screenshot attached].

Create 25 new Custom Values, like: {{ custom_values.sms1 }}, {{ custom_values.sms2 }} ....

populate the 25 variations of the SMS as the value and then just reference the custom value in the SMS message payload. Once the structure is setup, all you have to do is to modify the custom values if your campaign changes.

Hope that helps!

YES!!! this is a great solution .... for sms campaigns.

Why is this not implemented yet? GHL is such a mature platform and this doesn't look like much of a coding work. It's built in all sorts of 1-developer-in-a-garage types of products. Must have. Pretty please.

Absolutely!!!!

Why is this not a thing here yet? It seems like, with deliverability being a huge issue, that this is an easy way to help the overall deliverability of the system. By being able to create unique versions of each email that goes out, you would see a lot less emails being blocked and this is even more effective than simply "dripping" emails out.

YES!!!!

Absoulutely...

Spintax capability should be applied widely to all "communicating" functionality. Like, emails, sms, auto-responses in comments, workflow functions in sending out dm's. If the devs can just do a command like this:

{{RANDOM Value1 | Value2 | Value3}}

so we can use it everywhere!