Use spintax to vary your messages per recipient
Write {Hi|Hello|Hey} once; each recipient gets a different version. Reduces deduper fingerprint without rewriting the message N times.
What spintax is
Spintax is a tiny syntax for randomised text alternatives. You wrap pipe-separated options in curly braces, and Walytic picks one at random every time the message is sent.
Input: {Hi|Hello|Hey} {{firstName}}, are you {still interested|wanted to check}?
Result for recipient A: Hi Sarah, are you still interested?
Result for recipient B: Hello Mark, are you wanted to check?
Result for recipient C: Hey Priya, are you still interested?Each recipient sees a slightly different surface phrasing of the same message. WhatsApp's spam classifier tracks message similarity across your sends; identical strings to many people is a fingerprint of bot behaviour, varied phrasings are not.
Where spintax works
The same syntax works in three places:
| Where | Path | Notes |
|---|---|---|
| Flow builder | Send Message + Send Voice Note nodes | Expanded per execution |
| Campaign builder | Each campaign message textarea | Expanded per recipient |
| Bulk send | Bulk message text | Expanded per recipient |
You don't have to enable anything. Type {a|b|c} in the message field and it works.
Syntax rules
Basic:
{a|b|c} → picks one of a, b, cCombine with variables:
{Hi|Hello} {{firstName}} → picks greeting, then fills variableNested groups:
{Hi|Hello {there|friend}} → picks "Hi" or "Hello there" or "Hello friend"Escape literal braces:
\{not a group\} → emits the literal text {not a group}
\|literal pipe\| → emits a literal pipeWhitespace inside groups is preserved verbatim. Watch for trailing spaces.
How many alternatives?
There's no enforced cap on alternatives per group or groups per message. Practical guidance:
- 3-5 alternates per group is the sweet spot. Past 10 you're maintenance-burdened without measurable deduper benefit.
- 5-10 groups per message is plenty. Past that the message becomes hard to read in the editor.
- A typical safe template has 3 to 4 groups with 2 to 4 alternates each, giving you 8 to 256 unique variants. More than enough for a 1,000-recipient campaign.
The expanded message must fit WhatsApp's ~65,536-character text limit. Hard to hit unless you have a multi-paragraph essay.
Test it before you send
In any message field with spintax, click Test Spin (the purple button below the textarea). Walytic shows three random expansions of your current text. Use it to:
- Catch grammar mistakes ("are you still wanted to check" vs "are you still interested")
- Verify whitespace is correct
- Confirm variables aren't accidentally inside spintax groups
The Test Spin button reads only your text, no AI calls, no message sends. Safe to click as many times as you want.
Generate spintax with AI
If you struggle to think of alternates, click AI Variations instead. Walytic asks GPT to rewrite your message in spintax form, preserving variables. The result lands as a paste-ready string with 2 to 4 alternates per phrased segment.
You can also see N alternative full rewrites in the same panel and pick the one you like, then add your own {a|b} groups around the parts you want randomised.
AI Variations needs an OpenAI key configured under Settings → AI Settings. Test Spin does not.
Common mistakes
1. Single-brace variables vs spintax
Walytic uses double braces for variables: {{firstName}}. Single braces are for spintax: {Hi|Hello}. Don't mix them up. {firstName} (single brace) won't be replaced by the contact's name.
2. Spaces inside groups
{ Hi | Hello } produces " Hi" or " Hello" (with leading space). Strip whitespace inside the braces or you get awkward output.
3. Empty alternates
{Hi|} is valid syntax: it picks "Hi" or empty string. If that's intentional, fine. If not, remove the empty alternate.
4. Forgetting to close a brace
{Hi|Hello {{name}} is malformed (no closing brace). The parser passes the unmatched brace through verbatim. Always count your { and }.
What spintax doesn't help with
- Message timing. Use the Jitter node for randomised delays.
- Recipient targeting. Spintax only varies content, not who gets the message.
- Opt-out compliance. Always include "Reply STOP to unsubscribe". Spintax doesn't replace good practice. See the WhatsApp Compliance Guide.
- Cold-contact templates on Walytic Cloud. Outside the 24-hour window, Cloud API requires Meta-approved templates; you can't substitute spintax for a template.
Summary
{Hi|Hello|Hey} {{firstName}}, {quick question|wanted to check}: are you still {looking for|interested in} {a deal on|help with} your order?Four groups × 2 to 3 alternates each = 24 to 36 unique variants. Pasted into any send-message field in Walytic. Each recipient sees a different combination. No tooling needed beyond the message editor.
That's it. Use it everywhere you send to more than ten people.
Need more help?
Browse the rest of the help center or contact support directly.
