User Experience

Naxai comes with a lot of new features and is faster, more responsive and more secure than the legacy SMS Mailer.

Send one or two SMS

Focused on sending one message at a time.

Limited to 10 custom fields

You can create up to 50 custom attributes on top of the existing standard attributes

XLS and CSV support

Naxai supports only CSV files with commas or semicolons as separators.

From Excel (Mac OS), Go to "File" -> "Save As" -> and select the file format "CSV UTF-8 (Comma-delimited) (.csv)

From Excel (Windows), go to "File" -> "Save As" -> Select CSV

From Google Sheet, "File" -> "Download" -> Select CSV

Limited to the replacement of values

Legacy SMS Mailer was limited to replacing the values of custom fields. Naxai uses Liquid Syntax, which lets you not only replace values but also manipulate and transform them.

No Preview of messages

Naxai provides a live preview of messages as you compose.

Not possible to test a mailing

Before sending your messages with SMS Broadcasts, you can send a test message to your phone number to check the layout and ensure the formatting is correct.

Limit usage of uploaded file columns

With SMS Broadcasts, you have more flexibility when using an uploaded file. You can compose your message based on multiple columns. With the previous, you can see the message content in real time.

SMS Mailer has no spread of the message

SMS Broadcasts and FTP-to-SMS can be used to deliver your messages over time. It's useful to include a phone number in your message so people don't call you back at the same time.

Security Delay

Naxai has no security delay before sending the messages.
With Naxai, you have a full preview of your messages and can send a test message to your phone; that's the reason we believe a security delay is not required.
If you still do not want to send the message directly, you can always schedule your broadcast.

Time Window

Time Window is replaced by Calendars. Calendars can be shared across all Naxai products and offer additional features: you can add exclusion dates (public holidays) and set up 2 time windows per day...
In legacy SMS Mailer, messages sent outside of the Time Window would have been rejected, in Naxai they will be sent at the next opening window.

Allow long messages

On the legacy SMS Mailer, the option "Allow long messages" is replaced by the option "Number of SMS parts" on Naxai, allowing you to control the number of SMS parts; you can limit it to 1, but also to 2, 3, or 4, depending on your use case.

Group of Contacts

Naxai is using Segments to replace groups of contacts.

On SMS Mailer, you need to define your groups by manually adding people to them.

You can continue to do that with Segments by creating a Manual Segment, but you can also create Dynamic Segments. Dynamic segments use conditions to determine whether a contact must be in the group.
Suppose you have contacts with the attributes language and country; you can create a dynamic segment based on those conditions. Each time a contact is added, updated or deleted, it will be evaluated against the segment and will enter or leave it automatically.

If you use Groups in SMS Mailer, we recommend that you visit the Segmentssection.

Not possible to pause

SMS Broadcasts can be paused if you are using a spread of messages.
In all other cases, SMS are sent as fast as possible.

Incoming replies

The legacy SMS Mailer allows you to send a manual response to incoming replies.
SMS Broadcasts can be used with SMS Automations , allowing you to handle incoming responses automatically, send them by email, SMS, or HTTP request, update your contacts, or reply to incoming SMS.
To continue manually replying to incoming messages, Quick SMS will be used.

Webhooks

You can receive in real-time the SMS delivery status report and incoming messages using the Webhooks Manager even if the messages are not sent via the API.

API Keys & Security

Naxai don't use a single API Key for security. By default the API are using OAuth2 as security schema.
If you are not able to use OAuth2On Naxai you can create up to 10 API Credentials.
Compared to the legacy paltform, the API Credentials can be used for all services.
When you had to call Message API and Vocie API on legacy platform, you were obliged to have distinct API keys. On Naxai you can use the same set of credentials for all API calls.
Check the authentication section of our API Reference

Webhook Limitations

On Legacy API, the API was limited to one Webhook configuration.
Naxai allows you to create up to 10 webhooks configurations that you can configure to select which events you want to receive.
Webhooks Subscription can be also created programmaticaly. See Webhooks for more details.

From

On legacy API, you setup a from number that you need to know, you still have the possibility to use a From number on Naxai but we have added the possibility to use a Sender Service.
A Sender Service acts as a router that will use the best From number based on the destination. It's very usefull when you need to send messages to different destination's countries.

Idempotency Key

On Naxai, we have introduced the concept of idempotency Key (optional). It will protect the system against sending duplicates messages.
If you send a message with idempotencyKey = "1111" and you try to send another message with the idempotencyKey = "1111" in the 24 next hours then your message will be rejected.
It protects your system to send duplicate messages when you don't get a response from our API endpoint.
We recommend you use a unique identifier like a UUID, ULID, KSID, NanoID, ...

Calendars

You can use a Calendar to restrict the time window when messages can be sent.
Please note that Calendar does not block messages, it will reschedule the messages to the next opening window.

Length of messages

On Naxai, you can control the length of messages by fixing a limit on the SMS parts and if you want to truncate the message or not.
If your message exceed the maxParts and truncate is set to false , your message will not be sent.
If truncate is set to true, your message will be sent but truncated to 2 SMS parts.
It allows you to control your budget and avoid sendign too long messages.

Scheduling of messages

On Naxai, we have limited the scheduling of messages to 7 days when using the API.
Let's us know your use case if you need an extended period.
Note that messages scheduled before 5 minutes from now are sent immediately.

Rate Limiter

Naxai comes with a new Rate Limiting service with different values, you will receive the following headers in the response:
X-RateLimit-Limit X-RateLimit-Remaining X-RateLimit-Reset
If limited, you will receive a 429 response from the API.

HTTP Response

On Naxai, you will receive a 202 Accepted response.
Our new API is faster than teh legacy API and can proceed much more messages simulatenously.

Response Body

The New Naxai API will return only an array of message identifier with the count of messages processed.
You will get details of the messages, with the status using the Webhooks.

Documentation

The documentation of the new API allows you to test from the documentation directly the API.