Documentation ↓
SMSFLARE / Documentation
Back to SMSFLARE
Documentation/SMS operations
Guide · SMSFLARE 7.0.0

Client message options

All additional client transformations and their interaction rules.

Verified 2026-10-28 · 2 min read

Where to configure#

Open a client and choose Settings → SMS message options. These switches apply to SMPP delivery. Voice uses its existing path before SMS transformations, and its editor disables this group.

Available transformations#

OptionBehavior / range
Bengali prefixAdd অ, when no Bengali characters are present; enabled by default for compatibility
Random word replaceReplace one eligible word with four random characters
Random 1-character replaceChange the first character in 1–4 eligible words; URLs remain protected
Bracket first wordWrap the first word; a leading URL is not changed
Replace bracketed wordUse a static token, or four random uppercase letters when empty
Static replacementUp to 32 Unicode characters; one token without whitespace, controls or parentheses
Remove URLsSelect 0–100% of the client's traffic in a 1–1440 minute window

Random word replacement, random character replacement and bracket-word replacement are mutually exclusive. Bracketing without word replacement can remain enabled alongside a permitted transformation.

URL-removal interaction#

Selected messages do not generate tracking links and have URLs removed from final content. URL removal takes priority over URL-only delivery. The ratio is distributed over each client's traffic window, not randomly guaranteed for each individual small batch.

Counters are in memory and reset when the SMPP service restarts. Separate SMPP processes maintain separate counters.

Content selection#

Contents → No-URL messages only applies templates only to traffic selected by URL removal. With removal at zero, this mode does not select template traffic.

Verify#

Use Tests to import the client settings and inspect a draft. Reopen the client after saving to verify persistence. Compare final outgoing content, encoding and parts in the actual message trace.

Screenshots show fictional data from the public demo. Your instance may have different records and permissions.