Best practices using Spintax and Delays

Spintax and Delays are very powerful tools, but their effectiveness depends on how they are used.
Used correctly, they improve stability and deliverability.
Used incorrectly, they can generate incoherent messages or unnatural behavior.

This document compiles real-life best practices to help you get the most out of them.


Key principle: appear human, not “automatic” #

The purpose of Spintax and Delays is not to deceive, but rather:

  • Avoid repetitive patterns.
  • Simulate natural variations.
  • Maintain credible conversations.

If a message would not be sent by a real person, do not automate it.


Best practices with Spintax #

Use Spintax for variable parts, not for everything #

It is ideal for:

  • Best regards.
  • Introductory phrases.
  • Message closings.

Correct example:

Hola ${SPINTAX_SALUDO}, ¿te escribo para confirmar tu cita?
!/SPINTAX_SALUDO/Hola/Buenas/Hey/SPINTAX_SALUDO/!

Avoid using Spintax in critical or technical phrases.


Maintain semantic consistency #

All options must:

  • To have the same meaning.
  • Fit grammatically into the sentence.
  • Keep the same tone.

❌ Common mistake:
Mixing formal and informal options indiscriminately.


Don’t overuse the number of options. #

  • 3–5 options are usually sufficient.
  • More options does not mean more security.
  • Too many variations can sound forced.

Best practices with Delays #

Use realistic delays #

General recommendations:

  • 3–10 seconds for simple answers.
  • 5–15 seconds for longer messages.
  • Avoid extreme delays.

A delay should feel like writing time, not an artificial timer.


Do not always use identical delays. #

If you always use the same range:

  • The pattern reappears.

It varies depending on the type of message.


Do not put a delay on every message. #

Not all messages need delay:

  • Quick informational messages can be sent without delay.
  • Automatic confirmations are not always required.

Use delay when it adds naturalness.


Correct combined use #

The best strategy is:

  • Spintax for content.
  • Delay for timing.

Balanced example:

!/DELAY/4000/9000/!
Hola ${SPINTAX_SALUDO}, ¿tienes un momento?
!/SPINTAX_SALUDO/¿qué tal?/hola/buenas/SPINTAX_SALUDO/!

Result:

  • Different message.
  • Different time.
  • Credible behavior.

What Spintax and Delays do NOT do #

It is important to make it clear that:

  • ❌ They do not guarantee "zero risk."
  • ❌ They do not convert spam into valid messages.
  • ❌ They do not compensate for bad practices.
  • ❌ They do not replace human judgment.

They are support tools, not magic shields.


Relationship with WhatsApp blocks #

Spintax and Delays:

  • They reduce automatic signals.
  • They help break patterns.
  • Improved medium-term stability.

But WhatsApp also evaluates:

  • Volume.
  • Content quality.
  • User responses.
  • Number history.

Everything counts.


Final recommendations #

  • Prioritize quality over quantity.
  • Always think about the recipient.
  • Only automate what you would repeat manually.
  • Review messages before escalating.
  • Combine these features with general best practices.

Summary #

Using Spintax and Delays effectively allows you to:

  • Scale shipments with greater security.
  • Keep messages natural.
  • Reduce repetitive patterns.
  • Protect the stability of the number.

Misusing them has the opposite effect.

What are your feelings

Updated on 26 de January de 2026