Documentation ↓
SMSFLARE / Documentation
Back to SMSFLARE
Documentation/Billing & operations
Guide · SMSFLARE 7.0.0

Single-message & CSV tests

Use the seven-section test editor, client imports, saved numbers and batch controls.

Verified 2026-10-28 · 2 min read

Prerequisites#

Actual test sending requires an active client named testUser and a connected SMS route. The backend supports SMPP_TEST_CLIENT_LOGIN, but the current frontend follows the testUser convention. A missing test client leaves preview/configuration available while Send remains disabled.

Editor sections#

SectionConfiguration
MessageTemplate client, source, saved destination and message
Bulk CSVFile, concurrent batch size, delay and stop-on-error
RoutingDirect gateway or routing group
URLsRemoval ratio/window, landing page, generated link, Unicode and text position
ContentsBengali prefix, template replacement and no-URL-only mode
DLRAutomatic receipt, word/character/bracket transformations and success override
BillingBilling mode and tariff
Test URL controls

Client import#

Importing copies the client's settings into the test draft; it does not update that account. Routing groups, SMS options and templates are loaded for the editor. Verify the source address and destination before sending.

Saved destinations#

Search an existing number, or enter a number and choose Add. Saved destinations are shared by administrators and persisted in MySQL. Saving a number is not sending a message. Removing it from the address book is separate from clearing the current message draft.

CSV format and batches#

Required columns are destination,message. The parser also accepts dest,message, msisdn,text or two headerless columns. Inspect the row preview and validation before sending. Concurrency is 1–200 messages per batch. Delay is between batches. Pause/resume/stop and stop-on-error manage the current run; already submitted messages are not undone.

Verify#

Record the returned submit IDs and inspect the Tests logs and traces. All new message options are included in single and CSV payloads. A successful local preview does not prove carrier delivery.

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